Sign in
On first connect your client opens a browser window. Sign in with AffixIO Studio, then choose which API key the client may use on the consent screen. The consent screen shows which app is asking and where it will send you back.
Quickstart
Add the hosted AffixIO MCP server to your AI client, prove a simple yes/no condition, verify it with a signed ML-DSA-65 attestation, then move to the affixio SDK or API when you are ready to build.
Most MCP clients that support remote servers only need the URL. Add this to your client's MCP configuration:
{"mcpServers":{"affixio":{"url":"https://www.affix-io.com/mcp/"}}}If your client only supports local (stdio) servers, use the mcp-remote bridge instead:
npx -y mcp-remote https://www.affix-io.com/mcp/
On first connect your client opens a browser window. Sign in with AffixIO Studio, then choose which API key the client may use on the consent screen. The consent screen shows which app is asking and where it will send you back.
Your client registers itself (dynamic client registration), completes OAuth 2.1 with PKCE, and receives a token scoped to the key you picked. No API key is pasted into the client. See MCP connection for more detail.
Once connected, ask your agent to call these two tools, or call them directly. First, prove the built-in yesno circuit:
affix_circuit_prove
{"circuitId":"yesno","body":{"fields":{"condition_greater1":true,"condition_greater2":true,"condition_greater3":true}}}The response includes a proof ID. Pass it to verify, and ask for an attestation:
affix_circuit_verify
{"circuitId":"yesno","body":{"proof":"<proof_id>","requestAttestation":true}}409 double_spend_detected, which is how AffixIO stops replay. Attestations are signed with ML-DSA-65, a post-quantum signature scheme, so a third party can check the result without seeing the underlying data.For application code, install the public Node.js package (Node.js 20 or later, Apache-2.0):
npm install affixio@beta
Keep API keys in a trusted server runtime, never in public browser JavaScript. The API base is https://api.affix-io.com.
| Where next | What you will find |
|---|---|
| AffixIO documentation | SDK setup, verification modes, API references and integration boundaries. |
| Node.js SDK | What the affixio package does and how to configure it. |
| SDK proof modes | HMAC and UltraHonk proof modes and their trust assumptions. |
| Developer entry points | Connecting a trusted application with an API key and the published HTTP schema. |
| Migration to 2.0 | Moving from 1.x package names to affixio 2.0. |
| affixio on npm | Current published version and README. |
150 free proofs, no card needed.
100 free proofs, no card needed.
Read the details on the free proofs page, or see pricing for paid plans.
A single-use ticket takes four calls from your server, with your API key:
POST /v1/circuits/ticket_age_entry/prove
{"credential":{"schema_id":"0x01","issuer_id":"box-office","issuer_pubkey_hash":"0x0a","credential_id":"0x0b","claim_value":30,"valid_from":0,"valid_until":4000000000},
"context":{"secret":"0x01","context_id":"0x02","min_value":18,"max_value":120}}
POST /v1/link/issue {"proof_ref":"<proof_id>","gate_id":"main-door","ttl_seconds":45}
POST /v1/link/verify {"link":"https://www.affix-io.com/v/<token>"}
POST /v1/gate/verify {"circuit_id":"ticket_age_entry","proof":"<proof_id>","gate_id":"main-door","mode":"consume"}Put the returned https_link in the QR code. The first gate consume admits; a second returns 409 double_spend_detected, and link verify then returns 409 used. For staffed doors, /v1/otp/issue gives a six-digit code bound to the same proof. /v1/wallet/pass does the same for wallet barcodes.
schema_id, issuer_pubkey_hash, credential_id, secret, context_id) as strings holding a decimal or 0x hex number. Hash any text, such as an order id, first. Carriers must be bound to a proof made with the same API key; empty, unknown or spent proofs are refused. Opening a ticket link shows only whether the pass is valid, used or expired, never personal details. Full schema: openapi.json.