# Carry

> Proof-carrying memory for AI agents — control what every agent can use, and prove it on every answer. Built on Sui · Walrus · Seal · MemWal.

## Docs

- [Architecture](https://docs.usecarry.xyz/architecture.md): How Carry enforces access before generation, proves every answer, and lets anyone verify it.
- [Answer Receipts](https://docs.usecarry.xyz/concepts/answer-receipts.md): Every memory-based answer ships a verifiable receipt: what it used, whether it was authorized, and whether the blob still resolves.
- [Memory & namespaces](https://docs.usecarry.xyz/concepts/memory-and-namespaces.md): How Carry stores facts as content-addressed Walrus blobs, organized into typed namespaces.
- [Proofs on Sui](https://docs.usecarry.xyz/concepts/proofs-on-sui.md): Anchoring an answer as a tamper-evident Receipt object that the chain itself verifies — no wallet.
- [The gate](https://docs.usecarry.xyz/concepts/the-gate.md): Access control enforced at retrieval — the model physically never sees memory it isn't allowed to use.
- [Carry](https://docs.usecarry.xyz/index.md): Proof-carrying memory for AI agents — control what every agent can use, and prove it on every answer.
- [API reference](https://docs.usecarry.xyz/integrate/api-reference.md): The Carry web app's HTTP routes — gated chat, the companion, capture, policy, and anchoring.
- [The carry CLI](https://docs.usecarry.xyz/integrate/cli.md): Proof-carrying memory from your terminal — recall with a receipt, gate access, and anchor verifiable proofs on Sui + Walrus.
- [Aria — the companion](https://docs.usecarry.xyz/integrate/companion.md): A consumer health companion built on Carry: it only remembers what you allow, and proves it on every reply.
- [MCP server](https://docs.usecarry.xyz/integrate/mcp.md): Give any MCP client — Cursor, Claude Desktop, Claude Code — gated, receipted, Walrus-backed memory.
- [Vercel AI SDK adapter](https://docs.usecarry.xyz/integrate/sdk.md): Wrap any Vercel AI SDK model with proof-carrying memory in one line — gated before generation, a receipt on every call.
- [The Move contract](https://docs.usecarry.xyz/onchain/contract.md): carry::access — the on-chain access policy, OwnerCap, and the Receipt object that anchors every proof.
- [Deployments](https://docs.usecarry.xyz/onchain/deployments.md): Live Carry package and object IDs on Sui testnet, and how to publish your own.
- [The hash chain](https://docs.usecarry.xyz/onchain/hash-chain.md): How blake2b256 binds each receipt to its content and to the receipts before it — and why TS and Move agree byte-for-byte.
- [The public verifier](https://docs.usecarry.xyz/onchain/verifier.md): A walletless page anyone can use to independently verify a Carry Proof against Sui and Walrus.
- [Quickstart](https://docs.usecarry.xyz/quickstart.md): Run Carry locally — from clone to a live, proof-carrying agent in a few minutes.
- [What's real vs mock](https://docs.usecarry.xyz/reference/honesty-table.md): An honest accounting of which parts of Carry are live and which fall back to deterministic mocks.
- [Tech stack](https://docs.usecarry.xyz/reference/tech-stack.md): The languages, frameworks, and packages that make up Carry — and how the monorepo is laid out.
- [Seal & MemWal](https://docs.usecarry.xyz/stack/seal-memwal.md): Optional server-side encryption: private memories addressed by a real Walrus blob, readable only through the relayer.
- [Walrus](https://docs.usecarry.xyz/stack/walrus.md): How Carry stores memories and receipts as real, content-addressed blobs on Walrus — and verifies them live.

## Optional

- [Live demo](https://carrysui.vercel.app/companion)
- [Verify a proof](https://carrysui.vercel.app/verify/0x435148fde001b0ed2e935b4a72e686d5d7b64f54af74bd99af4bb8e9774ae215)
- [npm](https://www.npmjs.com/package/@usecarry/cli)
- [GitHub](https://github.com/Enoch208/carry)