Who publishes a passport.
Businesses publishing a valid Agent Passport at /.well-known/agent-passport.json. Each row below was fetched, schema-validated, and Ed25519-verified against the issuer's DNS TXT record at _agent-passport.{domain} before going live.
| Domain | Agent | Issued | Status | Passport |
|---|---|---|---|---|
| cubitrek.com | Cubitrek Humans-for-Agents Router | 2026-04-28 | Live | Open JSON |
Verification is run by the maintainers before each list update. A row drops to Expired if the passport expires before re-issuance, and is removed after one rotation cycle.
One PR. One verification run.
Publish a valid passport, then send a PR appending a row to adopters.md in the spec repo. Maintainers fetch, validate, and Ed25519-verify before merging.
- 01
Publish your passport.
Serve a signed JSON document at https://{your-domain}/.well-known/agent-passport.json. The five-step issuance flow is on /agent-passport.
- 02
Confirm with the reference verifier.
Install @cubitrek/agent-passport-verifier, point it at your domain, and confirm result.ok === true. The verifier prints a structured error code if anything fails.
- 03
Send a PR to adopters.md.
One row: domain, agent display name, issued date, status pending. Maintainers run the verifier, flip status to live, and your row appears here on the next deploy.
Embed a live status badge on your site.
The badge endpoint will re-verify on each render and return red if a passport drops out of conformance. Shipping with v0.2.
<a href="https://cubitrek.com/agent-passport/adopters">
<img src="https://cubitrek.com/agent-passport/badge?domain=YOUR_DOMAIN"
alt="Verified Agent Passport adopter" />
</a>Endpoint not yet live. Subscribe to releases on the spec repo for the v0.2 announcement.