Most verification vendors quote "enterprise scale" without saying what is being scaled. Circuits? Audit events? Stored passports? We split the question into three layers: what the API exposes today, what the audit tree has recorded, and what we will (and will not) say about uptime.
What the API reports today
curl -s https://api.affix-io.com/api/health on 28 August 2026 returned:
| Field | Value |
|---|---|
circuit_count | 115 |
merkle_leaf_count | 1,547 |
policy_version | 1.7.0 |
engine | noir+barretenberg |
attestation.algorithm | ML-DSA-65 |
The circuit list spans eligibility, travel, health, government, hospitality, and ticket domains. Count them yourself: the array is in the same JSON response.
Audit tree scale
Merkle leaves are append-only audit events. The count grows with every attested proof that syncs to the API. As of 28 August 2026 the on-disk merkle-audit.json store was about 449 KB for 1,547 leaves. The current root is published at /v1/merkle/root and matches the health endpoint.
That is audit scale, not customer record scale. We do not host the underlying eligibility files.
API query log
The key-usage.json index on the API host held 20,000 logged request events on 28 August 2026 (method, path, status, timestamp per row). Total API data directory size was about 11 MB across JSON stores including carriers, proof index, and Merkle audit.
Small in cloud terms. That is intentional. The platform is built to return a signed yes or no, not to become another data warehouse.
Uptime without a percentage
We do not print "99.99% uptime" on the marketing site. We cannot defend a number that mixes planned maintenance, client-side DNS failures, and regional routing into one headline.
What we do publish:
- status.affix-io.com runs live checks from your browser against named public endpoints and shows measured latency.
- incidents.json opened on 15 August 2026. As of 28 August it lists zero closed incidents and zero scheduled maintenance entries.
- /metrics/ pulls live circuit and Merkle counts and documents SDK benchmarks with reproduction commands.
If we have an outage worth naming, it goes in the incident log with timestamps and impact. If we cannot evidence it, it does not become a claim.
Verify yourself
curl -s https://api.affix-io.com/api/health | jq '{circuits:.circuit_count, leaves:.merkle_leaf_count, policy:.policy_version}'
curl -s https://status.affix-io.com/history/incidents.json | jq '.incidents | length'For SDK throughput numbers, see SDK throughput and test results, August 2026.
Public endpoints
The verify step
Where AffixIO fits in your scale check
Procurement teams ask for circuit count, audit depth, and incident history. Every number on this page maps to a URL you can curl without a sales call.
It returns scale facts from named public endpoints. Health for circuits and Merkle leaves. Status for incidents. Hub for a trial run with 100 proofs on your own integration.