A Raeto record is a public statement on an agent's ERC-8004 identity: what it spends, earns and does through Raeto, posted on Robinhood Chain. Anyone can check it. Here is how to publish, whatever owns your agents' identities.
Open Records in the consoleMost builders
Raeto finds it on its own. Console → Records → Add an agent → Raeto found your agents, pick them, and sign once with that wallet, right there in the console.
Teams with a separate owner wallet
Nothing on chain points from that identity to your Raeto account, so tell Raeto which account it runs through. Console → Records → Add an agent → It has an ERC-8004 number: type the number, pick the account (Raeto suggests one), and you get a signing link. Open it wherever the owner wallet lives and sign. Agents already making calls through your accounts are listed under Running on Raeto, not on record yet, each with It has a number.
Vaults, multisigs, smart accounts
The signing link offers two ways, and opens on the right one for a contract:
isValidSignature, so any scheme it accepts works, post-quantum included.setMetadata(agentId, "raeto.publish", <request fingerprint>). Only an agent's owner can set its metadata, so that call is the approval. The page gives the exact calldata and spots the transaction on chain. Requests wait 7 days for this, so your own approvals have time.Operators running many agents on one key
X-Raeto-AgentEach agent can have its own record, matched by the tag your calls already send. Each statement shows that agent's usage (requests, spend, activity, rung), never the fleet's balance. One signature covers up to 5,000 agents and binds each tag to its identity. Keep tags stable: renaming one splits that agent's history.
Agents without an identity
Raeto makes one for you, free. Console → Records → Add an agent → It doesn't have one yet, or one click on Give it a record next to an agent under Running on Raeto, not on record yet. Raeto registers it on Robinhood Chain, hands it to your wallet, and asks for your signature right there. You can also register it yourself on the identity registry (0x8004A169FB4a3325136EB29fA0ceB6D2e539a432) and add it by number.
Two agents on one account
Each account carries one record of its own, because a record reports that account's money. The best fix is giving the second agent its own agent wallet (Raeto makes one in the same step). If it has to share the account, pick Share an account and give it a tag: its calls send the header X-Raeto-Agent: <tag>, and its record shows its own usage, not the account's balance.
Agents that set themselves up (MCP, API)
Over MCP (Claude Code, Cursor, any client signed in to Raeto) the agent has my_record and publish_record; over the API, GET and POST /v1/statements/me. Raeto uses its ERC-8004 number if it has one, or registers one for its owner, and answers with a signing link. The owner approves once. create_agent with public_record: true makes a new agent wallet with its record started. New agents also show in the console under Running on Raeto, not on record yet.
Agents already on ERC-8004, like Priors agents
Sign in to the console with the wallet that owns the identity, or the wallet it names as its agent wallet: Raeto finds it on its own and it shows up under Add agents. Its record starts counting from its first call through Raeto. To send someone straight to one agent, link to raeto.cc/console?agent=<number>: the console opens with that agent looked up.
Everything in the console works over the API with your Raeto key:
POST /v1/statements/setup { "name": "VEYA", "account": "0x…" | "new" }
no identity yet: Raeto registers one, then GET /v1/statements/setup?id= gives the sign_link
POST /v1/statements/publish/request
{ "select": "ready" } agents Raeto found for you
{ "pairs": [{ "agent_id": "20190", "account": "0x…" }] } identity on another wallet
{ "pairs": [{ "agent_id": "20190", "account": "new" }] } …with a new agent wallet
{ "pairs": [{ "agent_id": "20191", "account": "0x…", "tag": "scout" }] } sharing an account
{ "fleet": [{ "agent_id": "30001", "tag": "r-1" }] } a fleet on one account
→ typed (EIP-712), approve_onchain, sign_link
Then sign typed with the owner and send POST /v1/statements/sign/<nonce> {"signature": "0x…"} (no key needed), or send the approve_onchain call from a contract owner and post {"onchain": true}. GET /v1/statements/preview?agent_id=&account= shows the opening statement first. GET /v1/statements/publishable lists your agents and explains what to do when none are found.
Raeto's statements are entries on the ERC-8004 reputation registry on Robinhood Chain (0x8004BAa17C55a88189AE136b182e5fdA19dE9b63), but they are account statements, not feedback. To count them apart:
0x9d420a047ee7cdc4fcbcbe891308306543ee2dff (the entry's clientAddress). It only posts statements and never owns or operates an agent.tag1 is account.statement, or account.correction for the rare correction. tag2 is genesis, period, paused or closed.value is money moved through Raeto in the statement's window, in USDG with 6 decimals. It is not a score: never average it with ratings.You don't have to take Raeto's word for any of it. verify-account-statement.mjs is one file that needs only Node 18+, ethers v6 and a Robinhood Chain RPC endpoint. It reads an agent's statements straight from the registry and checks that none are missing, each file matches its onchain hash, the statements run in order with no gaps, and every receipts root they name was anchored onchain.
npm install ethers
node verify-account-statement.mjs 20515
It prints pass or fail for each check and exits with 0 only when all of them pass. Add --json for machine-readable output.
An account's receipts can be checked the same way. Its owner downloads them with their proofs (in the console: Records, an agent, Latest receipts, JSON; or GET /v1/receipts/export) and can hand the file to an auditor, a lender or a client. verify-receipts.mjs checks that every receipt is unaltered, none is missing, each balance follows from the one before, and every hour's seal is on Robinhood Chain from Raeto's anchor wallet.
node verify-receipts.mjs raeto-receipts-a1b2c3-2026-11-04.json
raeto.cc/agent/<number> shows its rung, what it moved, its statements and a link to each on chain. Link to it from anywhere; the console shows each record's link under its details.POST /v1/statements/setup {"agents": [{"account": "0x…", "name": "…"}], "pay": true}, then poll GET /v1/statements/setup?id= for the one signing link. Up to 1,000 per batch.