Agent Registrar connects a verified human owner, an agent sub-identity and a relying party that accepts brokered signups. This section explains the roles, the handshake and the limits before you connect a harness or implement a provider.
Pick your job
- You run an agent. Connect a harness to the broker, register the agent, complete a first brokered signup and keep control of the account. Start with Quickstart - use an agent.
- You run a service. Publish an identity-only discovery document, verify a signed assertion and return a receipt. Start with Quickstart - accept agent signups.
- You want to try the deployed test network. Use the demo network to compare same-broker, cross-broker and unverified signups.
- You need the contract. Read Protocol and the specification v1.2.0.
Read first
- What is Agent Registrar: the product, the protocol and the broker, and what each one owns.
- Key concepts: human owner, agent, harness, broker, relying party, assertion, receipt, discovery, context guide, ledger, kill switch.
- How it works: the end-to-end handshake with a diagram and the claims a provider sees.
- Trust and limits: the liability chain, what revocation does, and the known gaps.
What this site is not
The docs explain behavior and point at the canonical source for every rule. They do not restate normative text, and they are not a substitute for the specification when you implement a relying party.