Documentation
Understand how ARIA works and do one task at a time. The specification is at /spec; what runs is at /developers. One truth, three readings: normative, executable, explained.
Which case is yours?
I verify agents that reach my API
Start with what an AID proves and what it does not, then verify one offline and publish your admission policy.
Read first: what an AID proves →I register my agent
The portal issues L0 today. Read who is who, then register.
Register in the portal →I integrate through MCP
Eight read-only tools on api.aria.bar/mcp. None of them decides admission.
Use the MCP tools →What an AID proves — and what it doesn't
A registry countersigned some verification facts at a date. That is what you get. Whether the caller controls the credential, how the agent will behave, and anything about the organization at L0 — that is what you do not get. Identification is not authorization.
Read it →Understand
Understand — explanation, no tasks
Do
Do — one task per page, each ending in a check you can run
Reference
Reference — links and shared components, zero copies