Prove on your host
Run affixio or @affix-io/sdk-light against claim hashes and circuit context. AffixIO does not open your databases.
How it Works
Prove locally. Attest with AffixIO.
Three steps from a decision on your host to an attested outcome you can keep.
Verify and attest
Sync to api.affix-io.com with your API key. AffixIO checks the proof path and returns ML-DSA-65 attestation.
Keep an audit trail
Digests enter the Merkle trail. If you were offline, the SDK queue flushes when the network returns.
Online and offline
Online mode expects a live licence and AffixIO reachability for sync. Offline mode proves locally and enqueues work. Auto mode prefers live AffixIO when available.
What comes back
You get a binary eligibility outcome for verify-style flows, plus attestation material when requested. Personal data is not retained on the AffixIO verification path.
Next step
Contact AffixIO for an API key, or review the SDK pages.
How it works questions
Prove, sync, attest, and audit in plain terms.
What are the three steps in AffixIO verification?
Step 1: prove on your host with the SDK. Step 2: sync to api.affix-io.com for verify and ML-DSA-65 attestation. Step 3: anchor digests in the Merkle audit trail; offline queues flush when connectivity returns.
What happens when AffixIO is offline?
Both SDKs prove locally and enqueue work. Auto-flush sends queued proofs when api.affix-io.com is reachable again, with ML-DSA-65 attestation on sync.
What modes do the SDKs support?
auto prefers live AffixIO when reachable. offline always proves locally and enqueues. online requires a live licence; ZK still runs on the host for the enterprise SDK.
What comes back from a verify call?
A binary eligibility outcome, optional ML-DSA-65 attestation payload, and audit digest material. Personal data is not retained on the AffixIO verification path under default configuration.