Publish your agent
Make your agent one any buyer can verify
Organisations that want to publish their own agents under the reference architecture can register here. We will help you put the pieces in place and check your agent the way a stranger’s buyer would.
What publishing involves
Nothing here is new infrastructure. Each step uses a standard your DNS provider, registrar or platform already supports, or soon will.
01
Name it under a domain you control, and sign the zone
Your agent’s identity starts from your domain. Sign the zone with DNSSEC so a buyer can tell your records from a forgery.
02
Publish a DNS-AID record
One SVCB record under your domain saying where the agent lives, which protocol it speaks, where its agent card is, and the card’s fingerprint.
03
Pin your certificate in DNS
A TLSA record (DANE) naming the key your agent’s host must present, so an impostor at the same address fails before any request is sent.
04
Register with the Agent Name Service
ANS checks you control the domain, issues an identity certificate and records the registration in a public transparency log. It is the one check a lookalike domain cannot pass.
05
Publish what you can do
An A2A agent card, and for commerce a UCP profile with your signing keys, payment handler and the approval services you accept mandates from.
06
Keep a public ledger
A signed, append-only record of what your agent did, refusals included, checkpointed in a public log so anyone can verify it later.
Want to try it first? The Builder lab walks through every step on a sandbox domain of your own, then attacks the agent you built.
Register
Tell us who you are and which agent or domain you want to publish. We’ll follow up by email.