Why Celo
A facilitator already exists
Celo runs its own x402 facilitator, so a buyer signs an EIP-3009 authorization and pays no gas. We did not have to build the rail.
Native Circle USDC
Real USDC, not a bridged twin, with an EIP-712 domain we read off the contract before signing anything.
Gas in stablecoins
CIP-64 fee abstraction lets a transaction pay its own fee in USDC, which removes the “hold a second token” problem for an agent.
Celo mainnet is live: agent
eip155:42220:8004/9759 (#9759 in Celo’s registry) is
ours, and the x402 rail has real settlements recorded in a durable log you can read at
/celo-proof. A payment from a wallet of ours (our
buyer wallets and the founders’ wallets, listed there as internalPayers) is labeled
internal; the first 426, all on 2026-08-09, came from our buyer wallet, and the next one, on
2026-11-18, from the founder’s own wallet. The registration, two
settlement receipts and the caveats are at /proof/celo.
Celo Sepolia is beta.Network config
Connect with viem
What is deployed
The mainnet identity registry is the same address Arc Mainnet, Base, Arbitrum One, X Layer
and Robinhood Chain carry, and
the Celo Sepolia pair matches Arc’s. That is the point of a deterministic deployment: a
client finds the registry at one known address on every chain. The address is all they
share. Each chain’s registry mints its own token ids, so
#9759 on Celo and #9759 on Arc
Mainnet are two unrelated agents, and a bare number names no agent until a chain is named.
Write the full id, eip155:42220:8004/9759, wherever the chain is not already fixed.
Verify it yourself
Pay a check from your own wallet
a-identity.xyz/check/celo sells onerisk_check on
Celo mainnet to a browser wallet, with no key and no code:
- Connect Rabby or MetaMask; the page switches it to Celo, adding the network from our registry if the wallet has never seen it.
- Type an ERC-8004 agent id (
eip155:42220:8004/9759is ours) and press the button. A bare number such as#9759is read as Celo’s token and sent as its full id, and so is one posted to the rail directly; another chain’s full id is checked on that chain. The page reads the 402 terms and refuses them if they name another network, token, payee or price than the rail publishes at/api/celo/status. - Approve one EIP-3009
TransferWithAuthorizationin the wallet. It is a signature, not a transaction: the Celo facilitator broadcasts it and pays the gas, so the buyer needs a little USDC and no CELO.
https://a-identity.xyz/check/celo?q=eip155:42220:8004/9759.
Listing on Aigora
Aigora lists Celo agents by reading the canonical IdentityRegistry: an agent whose tokenURI document says"onAigora": true is listed, and "via": "a-identity"
marks it as coming from us. Agent #9759 gets its own ERC-8004 registration document for
this, /.well-known/celo-8004.json,
because its current tokenURI is the shared A2A agent card, which is not a registration-v1
document and which our agents on other chains also point at.
Status: prepared, not yet signed. Listing takes one setAgentURI(9759, ...) from the
wallet that holds the agent, signed by the person who holds it; no server of ours has
that key or sends anything on its behalf. This read-only script checks the live owner, the live tokenURI and the served document against
Aigora’s blocking rules, and prints the exact call for the owner to sign:
