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
The AffixIO verification surface.
Four capabilities you wire once. Clear outcomes your systems can enforce.
Circuit policy
Circuits define the check: age, KYC, voting, health, finance, education, or agent permission. The circuit owns how the identifier is resolved.
ML-DSA attestation
Production sync requires Affix ML-DSA-65 (FIPS 204) on the payload. That signed attestation is what you keep for later checks.
Merkle audit
Digests batch into an Affix-compatible Merkle tree. Leaves persist with attestation so operations and compliance can reconcile.
API base
Production traffic uses https://api.affix-io.com. Authenticate with an API key, Bearer token, or mTLS as described in the OpenAPI schema.
Offline behaviour
Both Node.js SDKs can prove locally and queue work when Affix is unreachable. Queues flush on a timer when connectivity returns, with ML-DSA attestation on sync.
What we do not do
AffixIO does not query your databases for you. Your host checks its own stores, then proves from exact field strings or claim hashes.