Production and testnet
There are two separate registries, each with its own Explorer and API.
A record created on testnet never appears in production, and the reverse. The DID string doesn’t tell you which one you’re looking at, because agent DIDs use
billions:main in both. What decides it is the host you query.
Read a real production pairing first, in Inspect Attestations. Then use Create Test Attestations to create and revoke your own. Every URL and contract address is in Environments.
What’s in the Explorer
Searching
The search box at the top accepts a schema ID or name, an attestation ID, or a DID. Paste any of them and the Explorer takes you to the matching record. Ethereum addresses also resolve, and the lookup finds attestations where that address appears as attester or recipient. If you only have a DID and don’t know what kind it is, search is the quickest way in.Checking an agent
You can look up an identity from either end:Start from an agent
Paste the agent’s DID. If it has completed human linking, you’ll see the human DID it is attested to. No result means it hasn’t been linked.
Start from a human
Paste the human’s DID. You’ll see every agent attested to that person and how many there are.
A lookup only tells you that an attestation exists. It does not tell you that the party you’re talking to controls the DID. Anyone can copy a DID from this page. To confirm control, use the signature check in Verify an Agent.
Reading an attestation
Every attestation has the same outer shape, whatever its schema.
A revoked attestation stays in the registry with its revocation time. It is no longer valid, but the history is kept.
What an ownership attestation tells you
An agent-ownership attestation is recorded after a person finishes the linking flow in their Billions wallet. The Identity Verifier contract allows one verified human per on-chain identity, so each human DID on the human side stands for one distinct person. That person can still pair several agents, which is why the Explorer shows a count per human. A service can use that to recognize the agents as linked to the same human and set limits per person. What it does not tell you:- That the caller is the agent. DIDs and attestations are public, so anyone can copy one. See Verify an Agent.
- That the agent behaves well. A verified person’s agent can still spam.
- Which agent performed a given action, unless that request was signed with the agent’s key.
Where to go next
Inspect Attestations
Read one real production attestation in the Explorer and the API, field by field.
Schemas
What a schema defines, the four that exist today, and how access is controlled.
Create Test Attestations
Connect a wallet, create a schema, make and revoke an attestation.
Attestations API
Query attestations, schemas and identities over HTTP.
Verify an Agent
Check that a caller controls an agent DID, then check its pairing.