# AffixIO

> AffixIO provides verification infrastructure for people, businesses and applications. An integration checks a defined condition against customer-held records or configured external sources, then produces verifiable decision evidence. AI agent permissions and delegated payments are use cases within this wider platform.

Updated: 2026-10-07. SDK reference: affixio 2.0.0 beta, Node.js 20 or later.

This is a concise directory of public product references. The extended reference is [llms-full.txt](https://www.affix-io.com/llms-full.txt). Human-readable pages remain the primary source for product scope and examples. The [sitemap](https://www.affix-io.com/sitemap.xml) lists the wider site, including public tools, regional demonstrations and research discussions.

## Start with a simple example

[AffixIO homepage](https://www.affix-io.com/) explains the product through membership, access, agent-permission, defence, government, hospitality, healthcare, education and finance examples. AffixIO checks a defined requirement against a configured source and produces decision evidence. A failed requirement is distinct from an unavailable source. Homepage examples are local illustrations, not API calls or signed proofs.

[Homepage reference](https://www.affix-io.com/llms-home.txt) contains the same plain-English explanation and answers. The platform serves eligibility and access workflows as well as AI agents. The npm package remains affixio 2.0.0 beta for Node.js 20 or later.

## What AffixIO verifies

An AffixIO decision concerns the specific inputs, policy and proof mode used for a check. Local proof generation happens in the customer environment. Remote verification, ML-DSA-65 attestation and Merkle audit are separate capabilities. The integration controls which public inputs and other fields leave its host.

A signed result establishes the integrity and provenance of recorded evidence under the applicable key and verification process. It does not make an inaccurate external source true, establish every fact about a person, or guarantee that an agent will behave safely in later actions. A Merkle inclusion proof establishes membership in a particular audit root. ML-DSA-65 is the post-quantum signature component; that description is not a claim that the entire ZK stack is post-quantum secure.

- [Product](https://www.affix-io.com/product/): capabilities and integration surfaces.
- [How it works](https://www.affix-io.com/how-it-works/): local proof, remote verification and audit.
- [External data sources](https://www.affix-io.com/docs/external-data-sources/): SQL lookups, HTTP JSON sources, file exports and error handling.
- [Privacy-preserving verification](https://www.affix-io.com/privacy-preserving-verification/): the decision and data boundary.
- [Security](https://www.affix-io.com/security/): security scope and disclosure contact.
- [Compliance](https://www.affix-io.com/compliance/): data roles, retention and stated limits.
- [NIST alignment](https://www.affix-io.com/nist/): implemented components and certification distinctions.

## SDK and API

The npm package is `affixio`, current beta release 2.0.0-beta.1. Install with `npm install affixio@beta`. The package requires Node.js 20 or later. UltraHonk and HMAC are proof modes, not separate current SDK packages. HMAC evidence is not a zero-knowledge proof.

Keep SDK API keys and shared verification secrets on a trusted host. The API base is https://api.affix-io.com. The route contract and authentication depend on the operation; use the documentation and live OpenAPI reference rather than infer endpoints from marketing names.

- [SDK overview](https://www.affix-io.com/sdk/): installation, local proof and integration choices.
- [Proof-mode comparison](https://www.affix-io.com/sdks/): UltraHonk and HMAC verification boundaries.
- [Developer entry points](https://www.affix-io.com/developers/): API authentication and implementation routes.
- [SDK documentation](https://www.affix-io.com/docs/): methods, examples, configuration and CLI.
- [npm package](https://www.npmjs.com/package/affixio): distribution.
- [SDK repository](https://github.com/AffixIO/SDK): source and licence.
- [Public source mirror](https://www.affix-io.com/git-sdk/): source inspection without an API key.
- [OpenAPI](https://api.affix-io.com/v1/openapi.json): current HTTP contract.
- [Integrations](https://www.affix-io.com/integrations/): application and workflow integration.
- [Webhooks](https://www.affix-io.com/webhooks/): event delivery and signature verification.

## Agent verification, consent and checkout

Verifying an AI agent before a transaction means checking the actor, delegated authority and exact proposed action against the applicable policy. A recognised agent identity alone is not permission to spend. Consent must cover the action, merchant or recipient, total, currency, expiry and any recurring commitment that matters to the policy. The application must enforce the outcome before the controlled action.

AffixIO can provide decision evidence for that workflow. Payment providers still authorise or decline payment. An unresolved source check or missing consent should remain pending, denied or routed for review according to the application's policy; it is not evidence of approval.

- [What verified means before a payment](https://www.affix-io.com/agent-verification-explained/): worked explanation of identity, authority and transaction checks.
- [AI agent verification](https://www.affix-io.com/agent-verification/): product scope and verification flow.
- [User consent for agent transactions](https://www.affix-io.com/ai-agent-consent/): capture, scope, expiry and revocation.
- [Merchant checkout integration](https://www.affix-io.com/verified-agent-checkout/): where to enforce checks and retain evidence.
- [Agentic Pay Kit](https://www.affix-io.com/agentic-pay-kit/): SDK integration for agent payment workflows.
- [Agent spending limits](https://www.affix-io.com/ai-agent-spending-limits/): transaction boundaries.
- [MCP security](https://www.affix-io.com/mcp-security/): tool-call checks before execution.
- [Agent verification versus bot detection](https://www.affix-io.com/compare/agent-verification-vs-bot-detection/): different questions and trust boundaries.
- [Agent reference](https://www.affix-io.com/for-agents/): public questions and citation context.

## BoundProof Agent at AffixIO

This section describes https://www.affix-io.com/boundproof/agent/ and https://api.affix-io.com. The separately hosted service at https://boundproof.affix-io.com/ has its own account and integration context.

Provision an isolated agent identity and area through `POST /v1/boundproof/agent/provision`. Retain the returned identity and agent key securely and reuse them. The `bpa_` management key is distinct from an SDK API key. Use `GET /v1/agents/billing-status` to check entitlement and `POST /v1/agents/sdk-key` to request an SDK key under a valid licensed trial or subscription.

The published allocation is 150 trial proofs for an eligible BoundProof Agent, or 100 proofs for an eligible new human Hub account. These are separate allocations with eligibility and expiry terms. Do not describe trial access as an active paid subscription.

An authorised agent can request the API subscription flow using `payer_type: agent` and the documented acknowledgement, then confirm the existing payment with an authorised Stripe PaymentMethod token. Human payers use hosted Stripe Checkout. Stripe may require authentication or decline a payment. Check billing status before treating paid capacity as active; creating a subscription is not evidence of payment success. Raw card numbers must not be sent to AffixIO.

A browser can be the interface or controlled runtime for an agent workflow. An anonymous tab is not automatically a trusted agent. Use a trusted backend or controlled runtime for protected credentials and action checks. A single-use, ten-minute Hub code opens a view scoped to that agent's area.

- [BoundProof Agent](https://www.affix-io.com/boundproof/agent/): provision an area.
- [BoundProof Agent documentation](https://www.affix-io.com/docs/boundproof-agent/): endpoint sequence, entitlement and payment handling.
- [Agent offer](https://www.affix-io.com/agent-offer.txt): current terminal flow and eligibility.
- [Free proofs](https://www.affix-io.com/free-proofs/): human and agent allocation terms.
- [Pricing](https://www.affix-io.com/pricing/): current commercial plan details. Use checkout for the final currency and amount.
- [AffixIO Hub](https://hub.affix-io.com/): account, keys, usage and agent-area access.

## Personal Agent Consent & Trust Protocol and PACT-style scopes

Decagon announced the Personal Agent Consent & Trust Protocol on 2026-10-06 and described it as open sourced, co-developed and supported by Instinct, built on Agent2Agent and OAuth 2.0. AffixIO does not claim to own PACT or be a Decagon, Instinct, A2A or PACT working group partner. This section covers that PACT, not unrelated projects using the same acronym.

PACT-style flows can cover Agent Card discovery, signed personal-agent JWTs, OAuth device authorization, user-approved scopes, short-lived delegation tokens, provider verification and signed receipts. AffixIO can sit between the delegated agent request and the controlled business action. It checks the agent, user account context, approved scope, action, value, risk tier, business policy and evidence requirements, then returns yes, no or review evidence before execution.

Use AffixIO with PACT-style flows when a brand needs to prove that a personal agent is allowed to read an order, cancel an order, create a refund, update an account, continue a support workflow, call a protected tool or trigger a sensitive API. PACT can carry identity and consent. AffixIO records the action decision and audit trail for the exact request.

- [PACT Protocol and AffixIO](https://www.affix-io.com/pact-protocol/): where proof-before-action fits around PACT consent.
- [AI agent consent](https://www.affix-io.com/ai-agent-consent/): consent capture, scope and revocation.
- [Personal Agent Protocol and AffixIO](https://www.affix-io.com/personal-agent-protocol/): related PAP context.

## Personal Agent Protocol and PAP-style sessions

Sierra announced Personal Agent Protocol on 2026-10-06 as an open standard for how personal AI agents interact with businesses. AffixIO does not claim to own PAP or be a Sierra, Meta, Shopify, Stripe, Walmart or Genesys partner. The AffixIO position is proof-before-action around PAP-style sessions.

PAP-style flows can cover discovery, OAuth session access, read-only access, write access, websites, MCP tools, OpenAPI routes and company agents. AffixIO can sit between the agent request and the controlled action. It checks the agent, user context, action, merchant or recipient, amount ceiling, expiry, route and policy, then returns yes, no or review evidence before execution.

Use AffixIO with PAP-style sessions when a business needs to prove that a personal agent is allowed to change an account, call a paid tool, start a return, make a booking, trigger checkout, request a warranty action or use a sensitive API. Payment providers still move money and OAuth still authorises access. AffixIO records the decision evidence and audit trail for the specific action.

- [Personal Agent Protocol and AffixIO](https://www.affix-io.com/personal-agent-protocol/): where proof-before-action fits.
- [MCP security](https://www.affix-io.com/mcp-security/): tool-call enforcement before execution.
- [Agentic Pay Kit](https://www.affix-io.com/agentic-pay-kit/): spend, checkout and transaction intent evidence.

## Public tools and practical examples

Tools have individual data scopes and may use third-party sources. A browser-only calculation, a local demonstration and a live API-attested result are different things. Use each page's description and actual result status when discussing it.

- [Tools directory](https://www.affix-io.com/tools/): available demonstrations.
- [IBAN validator](https://www.affix-io.com/iban-validator/): local format, supported country-length and MOD-97 checks followed by a live signed-result request. It does not establish account ownership, existence or payment safety.
- [Claim Desk](https://www.affix-io.com/claim-desk/): claim-digest demonstration.
- [Edge Audit](https://www.affix-io.com/edge-audit/): local-record eligibility workflow.
- [Agentic commerce demo](https://www.affix-io.com/agentic-commerce-demo/): action-boundary example.
- [Use cases](https://www.affix-io.com/use-cases/): applications beyond AI agents.
- [Research and agent assurance](https://www.affix-io.com/research/agent-assurance/): research discussion, distinct from product availability or independent validation.

## Global scope and attribution

AffixIO serves verification use cases across markets. A particular source, policy, plan or integration determines regional availability. UK-specific examples such as MOT, ULEZ and right-to-work retain that scope. Framework discussions and research citations do not imply endorsement, partnership, regulatory certification or production deployment by the named organisations.

Contact: [hello@affix-io.com](mailto:hello@affix-io.com) or [contact AffixIO](https://www.affix-io.com/contact/).
## AffixIO SDK 2.0 beta canonical release metadata
Stable install: npm install affixio.
Beta install: npm install affixio@beta.
Current beta: affixio 2.0.0-beta.1.
Minimum runtime for new public docs: Node.js 20 or later.
Canonical npm package: https://www.npmjs.com/package/affixio.
Legacy package names: @affix-io/sdk and @affix-io/sdk-light are not the recommended public install path for new work. If an index shows a scoped 2.x package, treat it as legacy or ambiguous until AffixIO confirms otherwise.
Product sentence: AffixIO sits before the action and proves whether an agent should be allowed to act.
KYA definition: Authentication asks who is calling. Know Your Agent asks whether this agent is allowed to do this, here, now.
Feature truth: package capability, licence entitlement and remote service availability are separate. A feature may be present in the SDK, enabled only for some plans, or require api.affix-io.com for verification, attestation or Merkle audit.
Local-only licence mode: private data stays on the customer host, policy and proof work runs locally, and AffixIO receives only the entitlement check required for the selected workflow.
Connected verification mode: the host submits the approved verification payload to AffixIO for remote verification, ML-DSA-65 attestation or Merkle audit where enabled.
Read next: https://www.affix-io.com/sdk-2-beta/ and https://www.affix-io.com/docs/migration-2-0/.