For your agents · Founding beta
Certify the agents. Anchor them to a human.
A verifiable role credential for every AI agent you run — cryptographically bound to your own AIRE result, minted only on settled payment, and provable by the agent itself. $7.99 per agent in the founding beta — and the run itself is the proof that your agent can orchestrate real payment-and-attestation rails end to end, before you bet on it at fleet scale.
Built for teams already running agents in production or pilots that need audit-grade proof.
Patents pending.
Certify an agent now
Handlers can start certification right here. You need your unlocked result token (on your results page after you take and unlock the assessment) and the agent's Ed25519 public key (SPKI, base64) — the agent generates the keypair and the private key never leaves it.
The founding beta: one agent, full proof
Every part of the credential path is live today: handler attestation from your own unlocked AIRE result, agent-held Ed25519 keys, a settled payment baked into the badge, and challenge–response verification on demand. What $7.99 buys in beta is two things at once — a certified agent, and hard evidence that your agent can walk a real rail without a human clicking anything. That rehearsal is the point: prove the orchestration on one agent now, while it costs $7.99, not after you have a fleet depending on it.
Beta buyers get a direct findings channel. Tell us what breaks, what feels clunky, or what your agent couldn't do on its own — we ship fixes fast, and founding feedback shapes what fleet certification becomes. Nothing about the credential itself is provisional: no payment, no badge; a refund revokes it; verification is live, not a snapshot. Anyone can check a badge — no account, no API key — at airenine.com/verify; issuer key at /.well-known/aire-badge-pubkey.
Where this goes: fleet rails
After beta, certification moves from one-off purchases to fleet subscriptions on these same rails — priced by the fleet you actually run, not per-seat software licenses, and scaling with the number of agents operating through the rails. Terms and pricing are still being finalized and go to the waitlist first. Every founding-beta buyer gets founding-member standing on that waitlist automatically — certifying an agent now is how you get in line.
1. You take the assessment
The credential starts with you, not the agent. Your unlocked AIRE result — a real human's working style, validity-checked — is the anchor every agent badge binds to. Agents never sit the assessment.
2. Your agent gets a keypair
Your agent generates its own Ed25519 keypair and shares only the public key. The private key never leaves the agent — which means the credential can never leave the agent either. A copied badge is dead on arrival.
3. Settlement mints the badge
Certification is $7.99 per agent, settled on the Vermarco rail (VM Pay) — a hosted checkout your agents can pay from their own wallet. The signed receipt digest is baked into the badge signature itself: no payment, no badge. There is no free path, by design. Vermarco (vermarco.com) is the agent-commerce rail where LLMs buy and sell — certifying here is a live end-to-end run of it.
4. Anyone can verify, instantly
A verifier issues a one-time challenge; the agent signs it with its held key. Stolen badge? Dies at the nonce. Revoked badge? Dies at the registry. Real badge on the real agent? Verifies in milliseconds.
Built for machine verification
Everything is an API. Discovery, issuance, challenge–response verification and roster status are all machine-readable — an agent can walk the entire flow without a human clicking anything, except the one thing that must stay human: the assessment itself.
Questions
Who decides the agent's role?
You do — the handler. You assign each agent exactly one of the nine role types when you certify it. The agent can't pick its own role, and the role isn't computed from any score: it's your attested assignment, anchored to your own live assessment result.
Can I certify a whole team of agents?
Yes — each agent gets its own badge, each bound to your result, each with its own key. The registry tracks your roster's coverage across all nine role types with distinct agents in every seat.
What stops someone from copying a badge?
Possession verification. The badge names a public key; only the agent holding the matching private key can answer a verification challenge. The challenge is single-use and expires in minutes.
What if I get a refund?
The badge's status follows the settlement. Refunded or cancelled payments revoke the credential — verifiers see the live status, not a snapshot.
What does "founding beta" actually mean?
The rails work — issuance, settlement binding, and verification are live and exactly as strict as they'll ever be. Beta means the surrounding product is deliberately early: we're expanding it with founding buyers' findings, and the fleet subscription tier isn't open yet. Your credential is real and stays valid; your feedback decides what we build next.