Product

Verification you can put in production.

AffixIO is built for teams that need a clear eligibility result without moving personal data onto our stack.

Outcome

Yes or no

Binary eligibility for the circuit you selected. Systems can gate on a boolean.

Proof

On your host

Prove with affixio or @affix-io/sdk-light against claim hashes you already control.

Record

Attest and audit

ML-DSA-65 attestation plus Merkle digests on api.affix-io.com.

What AffixIO is

A verification layer between your application and the decision you need to make. Your host proves. AffixIO verifies, attests with ML-DSA-65, and keeps a Merkle audit trail on api.affix-io.com.

Who it is for

Security, compliance, and engineering teams running age checks, KYC gates, policy decisions, or agent permissions where retaining PII on a third-party path is not acceptable.

How you ship it

  • Call the API with an API key, Bearer token, or mTLS.
  • Integrate with affixio for full zero-knowledge prove, or @affix-io/sdk-light for millisecond AffixIO Light proofs.
  • Keep source records in your own stores. AffixIO works from claim hashes and circuit outcomes.

Product questions

What AffixIO is and who it serves.

What problem does AffixIO solve?

Teams need a clear eligibility result for age, KYC, or policy gates without moving personal data onto a third-party verification stack. AffixIO proves locally, verifies remotely, and returns yes or no with optional ML-DSA-65 attestation.

Who uses AffixIO?

Security, compliance, and engineering teams in regulated sectors that need binary verification outcomes and Merkle audit trails without warehousing customer identity dossiers.

How do you integrate AffixIO?

Call https://api.affix-io.com with an API key, or embed affixio / @affix-io/sdk-light on the host that already holds your records. OpenAPI: https://api.affix-io.com/v1/openapi.json.

What is the default data retention posture?

The verify path is designed so data_retained stays null under default configuration. AffixIO acts as processor for verification inputs; you remain controller of source records.