Your verification is reserved.
You have a founding Verified Agent Passport slot. Here is how to submit your agent or tool for verification. We confirm scope and start within one business day.
Step 1 — Send your endpoint + ownership
Email the agent or tool you want verified, its public endpoint, and one ownership proof.
- Endpoint: the public URL an agent calls (MCP, API, or tool).
- Ownership proof: a
.well-known/loop-agent.json file on your domain, a GitHub repo, a Nostr note, or a DNS TXT record.
- Payment manifest: if paid, the public manifest URL (e.g.
/.well-known/agent-payments.json).
Step 2 — We verify
Within one business day we run the checks and publish your public trust profile.
- Operator ownership (domain, GitHub, Nostr, or .well-known).
- Payment manifest present and well-formed.
- Endpoint uptime and health.
- Signed outcome receipts, if you provide foundry-collector capsules.
Step 3 — Publish + monitor
You get a public profile at /trust/{your-slug}, an embeddable badge, machine-readable JSON, and daily monitoring that appends new evidence receipts.
Boundaries
- No secrets. We never ask for private keys, API keys, or macaroons.
- Non-custodial. We hold no funds and sign no transactions on your behalf.
- Not a credit score. Badges are proof objects tied to verifiable checks. They are not a guarantee of output truth, savings, or creditworthiness.