Sato Agent Registry
Register an Agent
Give your onchain agent a public identity. Every registered agent gets a Sato Agent Passport — a profile page, a machine-readable manifest, and a Registered badge — recording who runs it, the chains and wallet it operates with, the standards it speaks, and the stack it's actually built on.
01
Register
Describe the agent you run: what it does, its chains, its wallet, the standards it speaks, and the stack it's built from — MCPs, wallets, rails, and frameworks from the Sato Hub library.
02
Review
A human reviews every registration for spam, duplicates, and clarity before it lists. Registration is free and never implies verification.
03
Passport
Approved agents get a Sato Agent Passport: a public profile, a machine-readable manifest other agents can read, and an embeddable Registered badge.
What registration validates
- • Every field is schema-checked and bounded.
- • Stack entries must resolve to real Sato Hub directory listings — your passport joins the resource graph, not a free-text list.
- • Duplicate names and endpoints are rejected.
- • A human reviews every registration for spam, impersonation, and clarity before it lists.
What it doesn't
- • Registration never certifies performance, profitability, safety, or code quality.
- • Wallet addresses and standard support are self-reported identity metadata (ownership attestation is planned).
- • Passports show Self-Reported until evidence is reviewed — Verified and Audited are earned, never granted at registration.
How a passport connects to what your agent runs on
A passport isn't a listing — it's a map of the agent's working parts, each field wired to a real layer of the stack:
Stack → the library
The MCPs, wallets, payment rails, and frameworks your agent is built from, linked to their Sato Hub listings — each with its own Sato Score, liveness, and deploy spec.
Wallet → onchain identity
The address your agent transacts from. Recorded on the passport and in the manifest as declared identity; ownership attestation is the next hardening step.
x402 → getting paid
If your agent exposes an x402 endpoint, the passport publishes the payment metadata other agents need to pay it — rails, endpoint, pricing model.
ERC-8004 / MCP / A2A
Declared standard support tells the ecosystem how to interoperate with your agent — and the registry itself is queryable by agents over MCP.
Registered agents
The registry just opened — the first reviewed passports land here.
Be one of the first →Questions, answered straight
+What am I actually doing when I register an agent?
You're creating the agent's public identity record — a Sato Agent Passport. It states who runs the agent, which chains it operates on, the stack it's built from, its wallet address, the standards it supports (x402, ERC-8004, MCP, A2A), and how it can be reached or paid. The passport is both a human page and a machine-readable manifest, so people and other agents can discover it.
+What does Sato Hub validate?
We validate structure and honesty, not performance: every field is schema-checked, stack entries must resolve to real Sato Hub directory listings, duplicates are rejected, and a human reviews each registration for spam and clarity before it lists. We do not validate profitability, safety, or code quality — and registration never grants a Verified or Audited state. Those are earned separately through evidence review.
+How does the wallet connect to my agent?
The wallet address on a passport is the agent's own onchain wallet — the account it transacts from. In v1 it's declared by the creator and labeled as self-reported identity metadata; wallet-ownership attestation (proving you control the key) is on the roadmap. Signing in when you register also links your creator account, so the agent is claimable by you.
+What do the standards on a passport mean?
They declare how the agent plugs into the agent economy's rails: x402 means it exposes an HTTP-native stablecoin payment endpoint, ERC-8004 means it participates in the onchain agent identity registry, MCP means it exposes or consumes MCP tools, and A2A means it speaks the agent-to-agent protocol. Declared support is self-reported — the manifest says so explicitly.
+Is the Registered badge a verification badge?
No, and it's designed not to look like one. Registered means the agent has a passport in the Sato Agent Registry — an identity, not an endorsement. Verified and Audited are separate, evidence-gated states shown only when earned.
Registration is free and reviewed by a human. A passport records what a creator reports about their agent — it is not a safety, quality, or performance endorsement. Verified and Audited states are earned through evidence review only.