How do AI agents call AffixIO safely?
Route verification through a backend or MCP server with your API key. Return proof_id or eligibility boolean to the agent. Never paste end-user PII into chat clients.
Integrations
Wire AffixIO into your stack.
Middleware, agents, workers, and webhooks that return eligibility without exposing raw credentials.
API middleware
Run verify before sensitive routes. Gate on eligible true or false from api.affix-io.com. Attach proof_id to audit logs without storing raw KYC in application databases.
MCP and agent servers
Public SDK materials describe Streamable HTTP tools: zk_prove, zk_verify, zk_merkle_proof, zk_attest. Production throughput should prefer direct https://api.affix-io.com calls.
LLM orchestration gates
Require a successful verify outcome before tool execution. Return proof_id or a boolean to the model context instead of passport numbers, dates of birth, or account dossiers.
Background workers
The AffixIO SDK can queue offline prove work and flush when connectivity returns. Suitable for retail edge, field ops, and intermittent networks.
Webhooks and audit
Attach Merkle digest and attestation material to downstream reconciliation. Public governance stats at GET /api/governance-stats.
Integration questions
How teams connect AffixIO to agents and APIs.
What MCP tools are documented?
zk_prove, zk_verify, zk_merkle_proof, and zk_attest over Streamable HTTP in public SDK materials. Prefer direct https://api.affix-io.com calls for production throughput.
Can AffixIO gate LLM tool execution?
Yes. Middleware can require a successful verify outcome or proof_id before sensitive tools run, returning eligibility without exposing raw KYC fields to the model context.
Where is the OpenAPI schema?
https://api.affix-io.com/v1/openapi.json. Developer summary at https://www.affix-io.com/developers/.
Provider names do not establish authority
An integration with an AI assistant must cover the actual tool execution path. Describing a project as SI, ASI or personal superintelligence does not establish provider compatibility or a partnership. Check the selected adapter, supported transport and failure behavior before enabling protected operations.
AI, superintelligence (SI), ASI and personal superintelligence: terms and boundaries