Keep the evidence
Record a moment, seal an existing file, and verify the original independently. Preserve what happened and when without requiring someone to trust a screenshot.
Record, seal & verify →Receiz · Capability map · v129.0.0
Keep what you’ve built.
Do more with it.
Your identity, proof, ownership, and history can travel together. Each compatible experience can use what you bring instead of making you start from zero.
For builders, these are foundations you can combine: from a personal record to a store, an agent, or a world. The same original can support uses its creator never had to plan for.
1,528 capabilities. One underlying ontology.
- Primitives
- Relations
- Invariants
- Laws
- Operations
- Capabilities
- Experiences
Receiz’s capabilities emerge compositionally from a small set of shared primitives governed by invariant relations and deterministic transition laws. The same foundations combine across operations and interfaces to create new experiences.
Core primitives: Proof object · Receiz ID · Kai pulse · Verified append · Memory Crystal
Explore the ontology →704
Public SDK exports
425
SDK client methods
356
Callable MCP tools
43
AI operating skills
Callable interfaces and operating skills for the same system—not a count of separate products. Availability and permissions depend on the operation and its configured environment.
Start with what matters to you.
Carry yourself forward
Bring your Receiz ID and carried history into a compatible experience. Recover from your identity proof instead of recreating yourself in every app.
Identity & recovery →Give your work more uses
Publish a Showcase, open its Originals as documents, audio, video, or live experiences, and carry the source into another compatible reader.
Proof objects & media →Keep how things happened
Preserve the changes that led to the current state. Revisit the evidence, answer a new question, or build a new analysis without recreating the past.
History & continuity →Change hands. Keep the story.
Carry origin, ownership, and custody with the object. Transfer it through the supported ownership path while preserving the evidence of earlier chapters.
Ownership & custody →Put proof-backed value to work
Hold Settlement, use funded Reserve, and issue notes or ownership certificates. Governed actions keep their proof trail attached.
Settlement & Reserve →Let your work meet people
Give visitors a Twin they can talk to about your work. Connect it to your profile, website, or domain so discovery can lead to a concrete next step.
Twins & domains →Keep the whole customer path
Connect discovery, booking, payment, and follow-up. Carry the relationship’s context through the handoff instead of asking people to explain themselves again.
Commerce & collaboration →Build worlds that remember
Create games and communities where subjects, possessions, relationships, and permitted history can continue across compatible experiences.
Worlds & portable subjects →Work beyond a connection
Open and verify held proof locally. Create offline records, then coordinate verified additions when transport is available. A server outage does not erase the source you hold.
Offline creation & coordination →Give agents evidence and boundaries
Let agents inspect public capabilities, work from permitted proof, and use explicit tools. Identity, consent, scopes, and custody still govern every action.
MCP & AI skills →Build the experience, reuse the foundations
Use the SDK, React helpers, compiler, and testing tools for proof-native apps. Spend your effort on the experience instead of rebuilding verification and carried continuity.
SDK, compiler & conformance →One foundation. Your next idea.
A repair history can become a diagnostic tool. A creator’s archive can become an interactive exhibition. A community’s permitted history can become the starting point for a new world. Keep the evidence; build the next use around it.
Apps decide which formats and actions they support. New interpretations stay traceable to their source; they do not rewrite it. Private history travels only through the access and consent its proof permits.
Find the exact capability
SDK exports include local primitives, compiler functions, tests, and React helpers. Client methods call the configured runtime. MCP tools are the named adapters your agent can invoke. Each keeps its documented requirements.
2 of 1528 capabilities
SDK export · @receiz/sdk (2)
runReceizOfflineNoteRollbackConformanceverifyReceizOfflineNoteRollbackConformanceEvidence