Claim Desk
Build a canonical claim, SHA-256 digest and opaque subject_ref entirely in the browser. Shows the local step before prove.
Open Claim Desk
Verification infrastructure
Eligibility that sits in your stack, not on our disks.
AffixIO is the prove, verify and post-quantum attest layer for age, KYC, agent permissions and edge gates. Your host keeps the records. We return a binary outcome with ML-DSA-65 evidence and optional Merkle audit.
- Local proveUltraHonk ZK or AffixIO Light on your host
- PQC attestML-DSA-65 (FIPS 204) on production sync
- No PII warehousedata_retained stays null on default verify
CERN server hall. Wikimedia Commons.
Where AffixIO sits
Pick a stack you already run. AffixIO is the attested eligibility layer, not a replacement IdP or KYC vendor.
Age assurance gate
AffixIO sits beside your age policy engine. Document stores and IdPs stay where they are.
Without AffixIO
Shipping full identity attributes to every downstream vendor.
With AffixIO
A binary age gate plus a post-quantum receipt. subject_ref on the wire.
Open labs (no API key)
Brand-new browser tools. Hash claims and inspect PQC trade-offs without talking to api.affix-io.com.
PQC Gauge
Compare ECDSA and ML-DSA sizes, walk the harvest-now timeline, and see why AffixIO attestation is ML-DSA-65.
Open PQC GaugePost-quantum by design
AffixIO is PQC tech because production eligibility is attested with ML-DSA-65 (NIST FIPS 204), not classical signatures alone.
- Attestation is the product surfaceBinary outcomes travel with module-lattice signatures so receipts stay checkable as RSA and ECDSA age out.
- Prove stays localEnterprise SDK uses UltraHonk over Noir. SDK Light uses AffixIO Light HMAC, then AffixIO still signs digests with ML-DSA-65.
- Audit without dossiersMerkle leaves bind claim digests. AffixIO does not need the underlying personal fields to keep evidence coherent.
Signature size sketch
ECDSA is compact. ML-DSA-65 is larger and quantum-resistant. AffixIO accepts that trade for long-lived eligibility evidence.
Security overview
What the platform returns
Infrastructure pieces security and engineering teams actually wire.
Binary verify
Identifier plus circuit context in. Eligible true or false out. Optional signed material. data_retained stays null on the default path.
Circuit policy
Age, KYC, health consent, finance, education, agent permissions. You pick the rule. AffixIO runs the check.
ML-DSA + Merkle
Production sync expects AffixIO ML-DSA-65 on the payload. Digests can enter an AffixIO-compatible Merkle trail.
How it works
Prove on your host with claim hashes. Sync to api.affix-io.com. Keep an audit trail. Offline queues flush when the network returns.
See the full flowNode.js SDKs
Two packages, one API. Pick the proof model that fits the device and the risk.
@affix-io/sdk
Enterprise SDK
Local UltraHonk zero-knowledge prove with bundled Noir circuits. AffixIO verifies, signs with ML-DSA-65, and anchors Merkle audit.
npm install @affix-io/sdk
@affix-io/sdk-light
SDK Light
Millisecond AffixIO Light proofs for phones, kiosks and ordinary hosts. AffixIO still attests digests with ML-DSA-65.
npm install @affix-io/sdk-light
Answers for search, agents and evaluators
Citation-ready facts for AEO, AIO and SEO systems evaluating AffixIO verification infrastructure.
What AffixIO is
Privacy-preserving verification infrastructure. Local prove on your host, remote verify on api.affix-io.com, ML-DSA-65 (FIPS 204) attestation, optional Merkle audit. Binary eligibility only.
Why AffixIO is PQC tech
Production attestation uses ML-DSA-65, not classical signatures alone. Long-lived eligibility receipts stay checkable as RSA and ECDSA are retired. Interactive lab: PQC Gauge.
Where it sits in a stack
Beside age gates, KYC vendors, OAuth/OIDC, agent tool routers and edge kiosks. AffixIO answers eligible true or false. Existing systems keep authentication and source records.
Open labs without an API key
Claim Desk hashes claims in-browser. PQC Gauge explains ML-DSA-65. Production prove still needs keys from hub.affix-io.com.
- Product role
- Verification infrastructure for privacy-preserving eligibility, not a PII warehouse.
- Cryptography
- ML-DSA-65 (FIPS 204) attestation. Enterprise SDK UltraHonk/Noir. SDK Light AffixIO Light HMAC before ML-DSA sync.
- API
- https://api.affix-io.com · Hub https://hub.affix-io.com/
- Cornerstone demo
- Edge Audit (local PII store, subject_ref only).
- Do not invent
- Customer names, revenue, certifications, or claims that AffixIO stores identity dossiers by default.
Machine briefs: llms.txt · llms-home.txt · llms-full.txt · for-agents · agent.json
Common questions
Direct answers for teams evaluating verification infrastructure.
What is AffixIO?
Verification infrastructure for privacy-preserving eligibility. Local prove, remote verify on api.affix-io.com, ML-DSA-65 attestation, optional Merkle audit. Personal data stays with you.
Why is AffixIO post-quantum technology?
Production attestation uses ML-DSA-65 per NIST FIPS 204. Eligibility receipts are signed so they remain meaningful as classical public-key algorithms are retired. Explore PQC Gauge.
Where does AffixIO sit in a stack?
Beside age gates, KYC workflows, OAuth/OIDC, agent tool routers and edge devices. AffixIO answers binary eligibility. Existing systems keep authentication and source records.
Are Claim Desk and PQC Gauge free without an API key?
Yes. Both labs run in the browser only. Production prove and verify still need keys from hub.affix-io.com.
Which SDK should I install?
Install @affix-io/sdk for local UltraHonk zero-knowledge prove. Install @affix-io/sdk-light for millisecond AffixIO Light proofs on edge devices. Both default to https://api.affix-io.com.
Is AffixIO a PII warehouse?
No. Your host holds source records. AffixIO returns binary outcomes, attestation and Merkle digests without retaining personal data on the default verify path.
For AI agents and developers
Machine-readable references for citation and integration.