Binary verify
Send an identifier and circuit_id. Receive eligible true or false. Optional signed material when you need a portable result. data_retained stays null on the verification path.
Platform
Four capabilities you wire once. Clear outcomes your systems can enforce.
Send an identifier and circuit_id. Receive eligible true or false. Optional signed material when you need a portable result. data_retained stays null on the verification path.
Circuits define the check: age, KYC, voting, health, finance, education, or agent permission. The circuit owns how the identifier is resolved.
Production sync requires AffixIO ML-DSA-65 (FIPS 204) on the payload. That signed attestation is what you keep for later checks.
Digests batch into an AffixIO-compatible Merkle tree. Leaves persist with attestation so operations and compliance can reconcile.
Production traffic uses https://api.affix-io.com. Authenticate with an API key, Bearer token, or mTLS as described in the OpenAPI schema.
Both Node.js SDKs can prove locally and queue work when AffixIO is unreachable. Queues flush on a timer when connectivity returns, with ML-DSA attestation on sync.
AffixIO does not query your databases for you. Your host checks its own stores, then proves from exact field strings or claim hashes.
Binary verify, circuits, Merkle audit, and data boundaries.
Send an identifier and circuit_id to api.affix-io.com. Receive eligible true or false. Optional signed attestation material. data_retained stays null on the verification path.
Named policy templates that define what is checked: age, KYC, consent, health, finance, education, agent permissions, and 100+ public identifiers in the live catalogue at GET /api/health.
Verification digests batch into an AffixIO-compatible SHA-256 sorted-pair Merkle tree. Client batches can reach 50,000 leaves. Public root at GET /v1/merkle/root and GET /api/governance-stats.
No. Your host evaluates its own stores, then proves from claim hashes or exact field strings. AffixIO never opens customer databases directly.