Pre-launch: AxiomCode is not yet open — we are not yet accepting submissions or payments, and certificates are not yet being issued. These pages describe the service as it will operate when it opens.
AxiomCode Try free

Pricing

The trial proves the engine. The certificate is the product.

Pre-launch: packs are not yet on sale — this page shows the launch pricing. Our pricing covers the full cost of running the service — infrastructure, compute, operations, support, and insurance — plus a standard margin. One credit is always US$0.01. Verification consumes credits by compute time; the certificate itself is included with every paid verification.

Trial

$0
no card required
  • 10 verifications
  • Full verdict + proof transcript
  • No certificates — trial verdicts are not certifiable
  • Rate-limited, fair use

Start verifying

Starter

$10
1,000 credits, never expire
  • Roughly 30–100 typical verifications
  • Signed certificates on every pass
  • REST API + API key
  • Certificate checker + revocation list

Available at launch

Growth

$50
5,000 credits, never expire
  • Roughly 150–500 typical verifications
  • Signed certificates on every pass
  • REST API + MCP server access
  • Usage reports & audit log

Available at launch

Scale

$200
20,000 credits, never expire
  • Roughly 600–2,000 typical verifications
  • Signed certificates on every pass
  • Everything in Growth
  • Priority verification queue

Available at launch

How metering works

Each verification is metered by compute time at 0.9 credits/second (about $0.009/s). A small spec that checks in 12 seconds costs ~11 credits — eleven cents. You see the exact charge with every verdict, and your usage report itemizes all of it. Credits never expire. Unused credits are refundable within 14 days — see the Refund Policy.

Why the trial has no certificates

The trial exists so you can evaluate the engine: real verdicts, real transcripts, real evidence. But a certificate is a trust instrument — it says AxiomCode stakes its name on this verdict. We only stake our name in a commercial relationship, where the full cost of standing behind the verdict is covered. That boundary is what keeps the certificates meaningful.

What counts as a “typical verification”?

A Lean 4 spec that compiles and checks in 10–60 seconds of engine time. Very large developments cost proportionally more; the meter is compute time, so you always pay for what you used.

Do certificates really expire?

Yes — 90 days, like TLS. Software changes and toolchains move on; re-verification keeps the evidence fresh. Renewal pricing is the same credit meter.

What if a certificate was wrongly issued?

We revoke it publicly and say so. Mis-issuance handling is documented in the Certificate Policy — it’s the core of the trust model.