What does it mean for an AI agent to be verified?
It means the agent is recognised, bound to a current user or business intent, checked against policy, and linked to auditable evidence.
AI agent verification
Know which agent is acting and why.
AffixIO verifies agent identity and delegated authority before high-value actions such as payments, paid API calls, account changes, bookings, renewals and tool execution.
BoundProof Agent
Give every AI agent its own proof area before it acts.
Provision a persistent BoundProof Agent, check its proof allowance and give a reviewer a scoped AffixIO Hub code. Trial and paid access follow the current billing status of that agent area.
- bpa_ agent key first. SDK key access depends on an active trial or subscription licence.
- Authorised payment. An authorised agent can use the documented API payment flow. Human payers use hosted Stripe Checkout. Payment-provider authentication may still be required.
- Scoped Hub view. The BP code opens only that agent's own area, usage and proof status.
Starter paid access
From £19/month
Provision the agent, check its licence and allowance, then request an SDK key through the documented flow.
What this page answers
An AI agent is verified when the system can show which agent is acting, who or what authorised it, what scope applies, and whether the current action fits policy. AffixIO turns that check into a signed yes or no decision.
AffixIO is designed for privacy-preserving verification. The customer keeps source records, account context, consent evidence and policy data. AffixIO verifies the proof path and returns signed evidence that another system can use without receiving a full identity dossier.
Verification flow
- 01Identify the agentBind the tool runner, wallet agent, buying agent or orchestration process to an agent_ref.
- 02Bind authorityReference consent, mandate or delegated policy scope.
- 03Check the actionCompare the current action with the allowed scope.
- 04Attest the resultUse a signed decision and audit digest as portable evidence.
Direct answers
Concise answers for search, procurement, engineering and agent retrieval.
What identifiers matter?
Common references include agent_ref, subject_ref, consent_ref, policy_version, circuit_id, nonce, timestamp and proof_id.
Can this work without exposing PII?
Yes. Source records stay with the customer. AffixIO receives proof material and returns a signed decision.
Personal Agent Protocol context
PAP-style sessions still need proof before action.
When a personal agent reaches a website, MCP tool, OpenAPI route or checkout flow, AffixIO can check the exact action and return yes, no or review evidence before the business lets it run.
PACT consent context
Scopes still need proof before execution.
PACT can identify the personal agent and carry user-granted scopes. AffixIO can check the exact action and return yes, no or review evidence before the brand lets it run.