Verify a file. Seal a response. Record a moment. Keep a Memory Crystal. Ask in your own words, with the proof objects and identity you carry.
Manual installation is available independently of marketplace approval.
Tool execution requires a compatible MCP host.
Two real screen recordings: create a sealed proof object, then check the proof carried by an uploaded artifact.
The user asks “Receiz seal this.” Receiz returns a sealed proof object, its exact artifact hash and byte length, a verification result and the save action.
The original sealed file carries the proof. The conversation displays the result.
Open the silent Seal recording ↗The original PNG passes verification. A subsequent JPEG showing the same artifact does not carry the embedded proof structure and fails verification.
Watch the full flow: submit the original PNG, see it pass verification, then submit the JPEG and see why it fails. A visible label or screenshot cannot replace the proof carried by the original file.
Open the silent Verify recording ↗Recorded demonstrations of a configured Receiz connection. The public HTTPS discovery endpoint alone does not provide this device-held execution; available actions depend on your host, authenticated connection and setup. Videos are silent and load only when selected. The descriptions above provide the text alternative.
Choose the setup for your AI →Your assistant can create and verify selected proof objects without becoming the authority over them. The original, its identity binding and verified history remain the foundation across compatible hosts.
Each proof object is the append-only database for its identity and governed history. Verified additions extend that history. Servers and databases may transport, index and replicate the objects; they do not replace their proof authority.
Verification checks the artifact’s binding and supported proof. A changed file cannot stand in for the verified original when it breaks that proof.
With the complete artifact and canonical verifier resources, offline verification establishes its proof without asking the originating service to confirm it.
Choose the complete proof objects each authorized participant receives. A scoped workflow can reduce repeated collection and unnecessary copies without making one party custodian of everyone’s complete history.
After explicit enrollment and installation of proof resources, the local runtime seals and verifies on your device. A cloud assistant still has its own connectivity and data-handling requirements. Keep private identity material out of chat attachments.
A connected view helps people understand the work. Receiz keeps the evidence beneath that understanding independently checkable: the original carries proof, supported tools project its content, and the responsible person or organization decides what to do.
Source, interpretation and decision retain distinct roles. A model response or operational view cannot rewrite the original evidence or manufacture its proof.
End-to-end organizational workflows require qualified source connectors, permissions, decision owners and operational actions. Installing the tools does not automatically connect every system or seal every AI response. Measure evidence preparation, repeated source requests and time to reconstruct the decision basis.
Integrity: sealed proof makes the original checkable. It does not by itself establish the truth of every factual claim in the content.
Confidentiality: who can read a record depends on its actual encryption, access and sharing controls. Sealing alone does not make content private, and sharing a readable original shares its carried content.
Custody: define source selection, permissions, retention and recipient responsibilities. Independent verification does not remove records you must retain or deployment-specific data obligations.
Continuity: offline verification checks the held artifact and its carried history. Discovering later additions and using connected services retain their own network and access requirements.
Choose by what your AI can run. The same Receiz proof objects remain the source of truth across compatible experiences.
Give your AI this one instruction:
Install Receiz from https://receiz.com/developers/install
An AI with local file and MCP setup access can follow the current download manifest and complete setup guide to install the package, preserve your Identity Seal and check its tools. A hosted AI uses the supported Receiz connection below.
Connect the downloaded runtime to Codex, Claude Desktop, Cursor, or another host that supports local MCP. Create and verify files on your device.
Set up local toolsUse the full authenticated Receiz connection to verify, seal, record supplied moments and retain Memory Crystals. A configured Receiz-hosted owner runtime runs without your Mac.
Connect a hosted AIGive an assistant the Receiz skill as project instructions or a supported skill import. Add the runtime when you want it to execute tools.
Add the instructionsDownload the ZIP above and extract the receiz folder into a permanent location. Keep its runtime, scripts and skills together. Install Node.js if needed, then check your terminal:
node --version
The major version must be 22 or higher. You do not need to run npm install.
Keep your original Identity Seal in a private, permanent location on your device. The runtime verifies the seal, its Receiz ID binding and proof of control before using that identity. Your ID text alone does not supply that proof.
For hosts that accept mcpServers JSON, merge this entry into your existing configuration. Replace both absolute paths: the extracted script and your original Identity Seal file. A passphrase-free seal needs no passphrase setting.
{
"mcpServers": {
"receiz": {
"command": "node",
"args": [
"/ABSOLUTE/PATH/TO/receiz/scripts/start-mcp.mjs"
],
"env": {
"RECEIZ_SUBJECT_IDENTITY_PATH": "/ABSOLUTE/PATH/TO/your-identity-seal.png",
"RECEIZ_MCP_EXECUTION_PROFILE": "marketplace-nonfinancial"
}
}
}
}Merge this into ~/.codex/config.toml, preserving your other servers. Replace both paths, reconnect, and start a new conversation. Official Codex MCP instructions.
[mcp_servers.receiz] command = "node" args = ["/ABSOLUTE/PATH/TO/receiz/scripts/start-mcp.mjs"] startup_timeout_sec = 120 [mcp_servers.receiz.env] RECEIZ_SUBJECT_IDENTITY_PATH = "/ABSOLUTE/PATH/TO/your-identity-seal.png" RECEIZ_MCP_EXECUTION_PROFILE = "marketplace-nonfinancial"
In JSON, use a path such as C:\\Users\\you\\Applications\\receiz\\scripts\\start-mcp.mjs. Keep the whole path in one argument. For a form: name receiz, transport stdio, command node, argument the script's absolute path, and the identity-file path and execution profile shown above. If Node is not found, use the executable path reported by where.exe node on Windows or command -v node on macOS/Linux.
Only if your selected artifact was created with password encryption, set RECEIZ_SUBJECT_IDENTITY_PASSPHRASE privately in your host environment to that artifact's existing passphrase. Do not invent a new password for a passphrase-free seal. The passphrase unlocks encrypted custody; the verified Identity Seal and proof of control establish identity authority.
Choose this only when you want a separate local identity instead of continuing with your existing Identity Seal. Replace the connection above with this configuration and set the script path. It does not automatically become your existing Receiz account.
{
"mcpServers": {
"receiz": {
"command": "node",
"args": [
"/ABSOLUTE/PATH/TO/receiz/scripts/start-mcp.mjs"
],
"env": {
"RECEIZ_MCP_DEVICE_BOOTSTRAP": "1",
"RECEIZ_MCP_EXECUTION_PROFILE": "marketplace-nonfinancial"
}
}
}
}First setup enrolls the device online and creates encrypted local custody with an automatically generated secret. You do not choose a password. Subsequent starts reuse that custody. If you already used this bootstrap path, retain it and its custody directory when updating.
Save your settings, restart the MCP connection and approve startup in your host. Allow up to 120 seconds where your host has a timeout setting. In a new conversation, ask:
Use receiz_capabilities with action describe. Report the tools available on this connection. Then use receiz_offline_seal_status to report local sealing readiness. Do not create, replace or publish any proof object.
Look for actual tool calls and returned status. If local sealing is not ready, ask the assistant to explain the one-time device-signing enrollment, then explicitly approve receiz_offline_seal_enroll with confirmEnrollment: true. Enrollment needs connectivity and retains the admitted identity; it does not replace your Receiz ID. Recheck readiness before sealing. The host's discovered tools define this connection.
Place a small text file in ~/.receiz/workspace, select it in your assistant, and ask:
Receiz seal this.
This connection exposes reviewed nonfinancial operations. Each tool retains its proof, custody and consent requirements. Settlement, Reserve transaction planning, financial transfers and unrestricted executors are excluded from this profile.
Select the original sealed file in your assistant, then ask:
Receiz verify this.
The skill uses receiz_verify_uploaded_artifact for the selected attachment. The tool verifies the bytes carried by your selected file. A screenshot, converted photo or visible checkmark cannot substitute for its embedded proof. For a file already held in your configured workspace, use receiz_offline_verify_file with its path.
ChatGPT is the conversational frontend. Receiz infrastructure executes the full nonfinancial runtime with your admitted identity, original custody and verified sources. A configured hosted owner runtime does not need your Mac awake.
In ChatGPT Plugins, install the Receiz plugin made available to your account. For a custom connection, enable Developer mode in Settings → Security and login where available, then use the administrator's registered OAuth client and exact callback with this HTTPS endpoint:
https://receiz.com/api/mcp/device
Choose OAuth and connect your Receiz account. This full connection is authenticated; the local Node ZIP above is a separate installation and does not install a ChatGPT plugin when attached to a conversation. Keep private Identity Seals, passphrases and transport credentials out of chat.
Enable Receiz in the conversation's tools menu. Ask it to check its tools and sealing readiness:
Receiz, check that you are ready.
The full reviewed profile contains 195 nonfinancial tools, including proof creation, verification, private AI subjects and Memory Crystal operations. Actual discovered tools and returned readiness determine what this account can execute. Each operation keeps its proof, custody and consent requirements.
Select the original attachment and say:
Receiz verify this.
Or seal selected text or a response:
Receiz seal this: My first proof object.
Record a supplied account of a moment with “Receiz record this moment: …” and continue with “Keep that in a Memory Crystal.” Short requests and translated equivalents use the same tools; no technical prompt is required.
Tap Download sealed proof on the branded Receiz proof object. It delivers the exact original file with its filename, signed proof and history intact. The private file link uses receiz.com and also works outside ChatGPT while valid. If the small Receiz panel appears, tap Download file to save the original.
ChatGPT can also retain the object using the existing receiz.bundle.v1 carrier where required. That handoff preserves the same proof and reconstructs the exact original; it does not reseal or embed Offline Studio. File acceptance, Library persistence and a completed device download are separate results.
Open ChatGPT on iPhone with the same ChatGPT account and enable the available Receiz plugin. The configured owner runtime executes on Receiz infrastructure, without a Mac worker or an embedded studio. Physical iPhone execution and the platform's exact file handoff must be tested separately. If Photos or Files removes embedded proof, a converted upload cannot verify as the original. Retain and supply the complete original or an existing proof-bearing Receiz bundle.
The separate unauthenticated https://receiz.com/api/mcp endpoint supports discovery, supplied-field inspection and integration planning. It does not provide the full sealing or Memory Crystal runtime. Use it only when those public inspection tools are what you need.
Full execution reuses the existing owner runtime and original custody, with separate caller and worker OAuth grants. A Receiz-hosted worker needs its explicitly authorized custody and verified owner binding; installing the plugin alone does not create them. A local worker remains an optional deployment and must be awake while it executes. Follow the complete setup guide and the Receiz Connect integration. The download contains no credentials.
Import the marketplace-skills/receiz folder where your AI supports skills, or add its SKILL.md to your assistant's project instructions. Instructions guide your AI; the connected runtime supplies its tools.
Mind brings your recorded work, retained sources and sealed memory into one place to inspect and reason from. Use it alongside your AI, with the identity and source files you choose to carry.
Sharing is explicit. Installing the package does not automatically import Mind memory or private AI conversations.
Save the guide for later, download individual configuration files, or inspect the checksum of the complete package.
Executable tools, required dependencies and setup files.
Local setup, full hosted ChatGPT, original custody and troubleshooting.
For hosts accepting mcpServers. Set the runtime and Identity Seal paths.
Merge into your existing config.toml. Set both paths.
The scoped Receiz skill for supported skills or project instructions.
Compare the downloaded ZIP with this digest using shasum -a 256 on macOS, sha256sum on Linux, or Get-FileHash -Algorithm SHA256 in PowerShell. This checks package bytes; proof object verification uses the canonical Receiz verifier.
777443e898efbb735c47f92b611302fe0a48ac7ca960718182608ee54dc7e169
Continue with your existing Identity Seal and Receiz ID. Select the original seal on your device using the identity-file path in the configuration above. Receiz verifies the enclosing artifact, its identity binding and proof of control. That verified identity is the authority the tools use.
A passphrase-free Identity Seal needs no password. Only password-encrypted artifacts need their existing passphrase, configured privately on the host. Keep your private Identity Seal, recovery material and any passphrase out of AI chat attachments.
Your seal stays at the location you select. Working files default to ~/.receiz/workspace; the existing-identity runtime keeps local signing custody in ~/.receiz/offline-seal and subject continuity in ~/.receiz/subjects. The optional separate-identity setup uses ~/.receiz/mcp-device. Preserve whichever existing paths your configuration uses.
For updates, stop the connection, extract the new package into a new folder, and update only the runtime script path. Keep the same identity path, custody directories and workspace, then reconnect and check readiness. Updating the tools must not create a replacement identity.
Local execution requires a host that supports stdio MCP and can launch Node. Hosted execution requires a supported remote MCP connection. An AI that accepts only text can read the instructions but cannot execute Receiz tools from those instructions alone. Your AI provider's subscription and permission requirements still apply.
Read the returned result. verdictObtained: false means verification could not run; it does not establish invalid proof. attachment_authorization_failed means the selected file handoff was not accepted. Update your installed local tools from this page, reconnect and start a fresh conversation. Keep your original file and identity custody.
Local hosts can supply a staged attachment path; hosted ChatGPT supplies an authorized file reference to the configured owner runtime. An API-only update to a hosted connection does not update an installed local runtime. Hosted administrators must update the hosted worker, configure its attachment access and refresh the connection's tool metadata.
File extensions do not grant or prevent proof validity. The existing canonical verifier determines the result from the original bytes. The attachment transport currently accepts files up to 32 MiB; a transport failure or an unsupported-format verdict must be reported exactly.
Check Node 22+, the absolute script path, and that the whole ZIP was extracted. Reconnect the MCP server and start a fresh conversation. Use an absolute Node executable path if the desktop host cannot find it. Put the selected file in the configured workspace. For enrollment or custody errors, preserve the existing identity files and resolve the reported cause; do not delete custody to force a reset.
Receiz sealing runs locally without network after the one-time canonical enrollment. Verification runs locally from the exact held file and packaged verifier resources; it does not need enrollment or server confirmation. A local MCP host can call those operations offline.
Hosted ChatGPT needs connectivity to reach its configured owner runtime on Receiz infrastructure. A URL attachment must be downloaded first. After the original bytes are held, the SDK executes sealing and verification in that runtime, without a Mac worker. Receiz Mind's Mac application includes local inference; its remote connection and device relay require connectivity.