Identity and permissions for AI agents. Prove who controls an agent, cap what it can spend, and revoke it with one signature.
An agent's wallet can sign anything. BoundID separates who controls the agent, what its owner allows, and what actually executes.
Dated claims from named issuers. Each one states what it proves and what it doesn't.
Approved issuers check key control and the operator, then sign scoped credentials that expire.
POST /v1/evaluations { "decision": "ALLOW", "reasonCodes": ["POLICY_MATCH"], "policyVersion": 3, "validUntil": "+60s", "signature": "0x5b1d…c07a" }
ALLOW, DENY or INDETERMINATE, with reason codes and a receipt signed for 60 seconds.
A credential alone can't stop a transfer. The guard re-checks the exact call at execution, consumes its nonce and updates the budget atomically. Revocation beats every cached decision.
Four steps from an anonymous key to an agent your counterparties can check, and a kill switch that actually works.
The owner key and the agent's own key both sign a binding challenge. The agent gets a passport at binding v1.
An approved issuer checks the operator and signs a 30-day credential. The evidence stays off-chain.
The owner signs exactly what the agent may do: asset, recipients, per-payment and daily caps, expiry.
Every call is evaluated and guarded. Revoke once, and every later call fails, even with a live session key.
Ask BoundID API whether an agent may make a specific call. The answer comes with reason codes and a receipt your contracts can check.
curl https://useboundid.com/api/v1/evaluations \ -H "content-type: application/json" \ -d '{ "agentRef": "bnd:4663:1", "request": { "to": "0xCcb26681DcF04FDF9Ab1F828781d77D85ECdB7e3", "amount": "84000000" } }'
Run the request against the live API.
Try an unlisted recipient or more than 100 USDG.
Receipt lifetime. Bound to the request hash, chain block and audience.
Typed signatures for owners, agents, issuers and receipts. Replays fail.
Missing, stale or unreachable evidence returns INDETERMINATE, never ALLOW.
Assume agents get compromised, issuers make mistakes and infrastructure goes down. Each failure mode has a hard rule and a reason code.
Every owner or execution-key change bumps the binding version. Nothing signed for the old binding carries over.
Signatures bind chain, recipient, asset, amount and nonce. A reused nonce or altered call fails.
Spend counters update atomically in base units, so two concurrent calls can't both spend the last dollar.
A revoked delegation fails every later call, including ones holding a receipt issued a second earlier.
If chain or registry status can't be read, the answer is INDETERMINATE. Nothing defaults to ALLOW.
Documents, biometrics and prompts stay in encrypted, access-logged storage. Chain state holds random IDs and status.
Every receipt names the block it was evaluated against. Revocations and status are shared state that independent apps can read without trusting a BoundID server.
$KYA is the collateral behind BoundID Verify's issuer network. A false attestation costs the issuer that signed it.
Issuers lock KYA against the exposure of each verification job. Collateral releases only after its challenge window closes.
Evidence-backed challenges freeze only the affected collateral: 7-day challenge, 7-day response, 14-day appeal, three independent reviewers.
Customers pay for verification in stable assets. KYA is collateral, not a toll, and reading a passport never needs it.
| Ecosystem & providers | 35% | Milestone releases over 48+ months |
| Protocol treasury | 20% | Published budgets over 36+ months |
| Core contributors | 20% | 48 months, 12-month cliff |
| Strategic contributors | 10% | 48 months, 12-month cliff |
| Community reserve | 10% | Rules set after legal review |
| Liquidity reserve | 5% | No automatic deployment |
Token parameters are proposed and subject to legal review. No KYA has been issued, and nothing on this site is an offer to sell or a solicitation to buy any asset. Holding or staking KYA carries no right to fees, dividends or yield.
Pilot access is open for agent-wallet teams, payment apps and verification providers.
Follow @UseBoundID