Verification infrastructureMeet Agentic Pay Kit

AffixIO

Permission to act.
Proof to trust.

Give your application a clear eligibility decision before an agent spends, a tool runs or access is granted. Keep source records in your environment.

Talk to AffixIO Read the documentation

One decision. A traceable outcome.Illustrative workflow

01 / Your environment

The request

A shopping agent requests permission to check out.

02 / The trust layer

AffixIO

Check the claim.
Verify and attest the outcome.

How it works

03 / Your application

The decision

Within the spending policy

Your checkout receives a decision it can enforce, with evidence to inspect later.

Source records stay with you

Local proof workflows

ML-DSA-65 attestation

Merkle audit records

Official Node.js SDK

Built around the decision

Ask what matters.
Keep the rest private.

Most workflows need to know whether an action is allowed. AffixIO connects your proof workflow to a usable verification result, without making another home for your source records.

Set the conditions

Define the eligibility rule, permitted action or spending policy your application needs to enforce.

Agent permissions

Prove the claim

Use the SDK for local proof generation. Keep sensitive inputs in the environment you control.

Privacy by design

Act on the result

Receive a clear outcome, enforce it in your product and retain the verification evidence you need.

Explore the platform

Agentic Pay Kit

Before an agent spends,
check its permission.

Connect agentic commerce to the rules your business actually uses. Check the amount, merchant and scope before your application authorises a payment.

Spending policies for agent checkout
Helpers for x402, AP2-style mandates and MCP
Receipt and webhook evidence workflows

Explore the kit Payment workflows

Your payment provider moves the money. AffixIO helps your application decide whether the action is permitted.

Policy explorer

A purchase, checked.

Example

Purchase amount £40

£10£150

MerchantAgent has permission to make this purchase

Per-purchase limit: £75
Merchant policy: Approved only

Within policy

£40 is within the £75 limit, with an approved merchant and permission in place.

Sample policy only. No API call, payment or signed proof is created.

For the people building it

From npm to your
next integration.

The official affixio package brings local proving, API verification and Agentic Pay Kit helpers into your Node.js project.

npm install affixio

SDK reference Integration examples View on npm

JavaScript / TypeScriptNode.js 18+

checkout.mjsAgentic Pay Kit

import { AffixSDK, agenticPay,
  shoppingAgentPolicy } from "affixio";

const sdk = new AffixSDK({
  apiKey: process.env.AFFIX_API_KEY
});

const policy = shoppingAgentPolicy({
  currency: "GBP",
  maxPerAction: 75,
  categories: ["retail"]
});

const result = await agenticPay({
  sdk, policy,
  agentId: "agent://shopper/session-42",
  merchant: "example.com",
  amount: 40, currency: "GBP",
  category: "retail", rail: "checkout"
});

if (!result.allowed) {
  throw new Error(result.reason);
}

A practical trust layer

Different workflows.
The same need for proof.

All use cases

Agents & commerce

Permission before action

Give autonomous purchases, paid tools and delegated tasks a policy checkpoint.

Eligibility & access

The answer you need

Build age assurance and eligibility gates around verification outcomes.

Tools & platforms

Check the scope first

Place permission checks before MCP tool calls, API writes and restricted workflows.

A few useful answers

Know what you
are building with.

Explore the implementation details, then choose the workflow that fits your product.

Talk to AffixIO

What is AffixIO?

AffixIO is privacy-preserving verification infrastructure. It connects local proof workflows to API verification, signed outcomes and audit records, helping applications decide whether a user or agent is eligible to take an action.

Where does AffixIO sit in an agent workflow?

Place AffixIO before the action your application controls, such as a checkout, paid API request or tool call. Your application supplies the relevant context, checks the result and enforces the decision. AffixIO does not replace the agent or payment provider.

Where does the personal data stay?

Source records remain in your environment for local proof workflows. The default verification path returns an eligibility outcome with data_retained set to null. Review the chosen SDK flow and API request fields when designing your integration.

Which SDK should I use?

Use affixio for the full Node.js SDK, local UltraHonk proof workflows and Agentic Pay Kit helpers. The separate @affix-io/sdk-light package supports lightweight HMAC proof workflows. Both connect to the AffixIO API; their proof mechanisms differ.

How do I get started?

Install affixio from npm, contact AffixIO and follow an integration example. Manage your API keys in the AffixIO Hub. Check the pricing page for your expected API usage before going live.

See pricing

Your next step

Make trust part of the product.

Start with one workflow. Put a verifiable decision before the action.

Contact AffixIO Explore pricing

Built for the questions buyers are asking now

AffixIO now gives clear, citeable answers around verified AI agents, delegated checkout, agentic payment risk, transaction intent proof and privacy preserving decision evidence.

Verify the agent before money moves

Confirm the agent, the mandate and the action before checkout continues. AffixIO gives teams a clear permission result with evidence they can inspect later.

See how verification works

Accept agent-led checkout with control

Let useful AI shopping agents reach conversion while checking spend limits, consent and merchant policy at the moment it matters.

View the checkout guide

Prove the transaction matched intent

Create a decision record that shows why an agent was allowed to act, what scope applied and which proof supported the outcome.

Read the intent proof page

Proof, trust and use cases for serious buyers

Premium buyers need more than a pitch. They need trust posture, proof examples, direct answers, request shapes and clear use cases before they speak to sales.

Trust Centre

Security posture, privacy model, data minimisation, responsible disclosure and the claims AffixIO does and does not make.

Open Trust Centre

Proof Library

Sample signed decisions, agent mandates, Merkle audit records and webhook evidence for buyers and builders.

Explore proof examples

SDK request builder

A simple interactive request builder that shows how agent checkout and tool-call permission payloads are shaped.

Build a request shape