How much can you do?
| Pack | Work units | Price | Early | Mid | Late |
|---|
| Explore | 100,000 | $29.00 | 467 | 138 | 96 |
| Round | 400,000 | $99.00 | 1,869 | 553 | 387 |
| Raise | 1,200,000 | $249.00 | 5,607 | 1,659 | 1,163 |
Early / mid / late columns are approximate complete valuations of typical venture-backed archetype cap tables
(Seed–A, multi-series, mature private), measured from real runs — not estimates. Work units meter the underlying
computation; you buy analytical capacity, not abstract compute.
About auto-reload. So a calculation mid-negotiation doesn't fail on an
empty balance, auto-reload is on by default: when your balance falls below $5, the card you saved at checkout is
charged $99 for one Round pack. It fires only when your balance runs low — never on a calendar — and you can
stop it any time by removing your saved payment method in the Customer Portal, reachable from your account.
Billing guarantees
Three named guarantees govern every metered run: what happens on a failure, where your balance stops, and where
the charge for a solve tops out.
Only billed for delivered work
A failure of any kind before your result exists — an engine error, or a request the transport dropped before
the answer was handed back — means your account is simply not billed, no matter how much compute we spent.
Work we hand back is billed: stopping a run with opm_cancel returns the partial schedule and event log produced so far, and that delivered work settles. If billing itself
fails after your result exists, you keep the result and we absorb the loss. Every solve result is durably
retained — written to storage before your account is settled, and kept for 48 hours — so re-issuing the
identical request in the same session within that window returns the retained result with a single settlement.
No negative accounts
Billed work is clamped to your available balance at settlement — a balance stops at zero. Anything we cannot
charge against it is waived outright — never carried as debt, never invoiced later — and every waived amount
shows up in your usage reporting. Delivered work is never refused after the fact.
No billing beyond the estimate max
You are never charged more than the work_max in the estimate for the job you ran. If it consumes more than that, the run still finishes, you still get the
complete result, and we absorb the difference. Our estimate, our risk. Your AI previews the cost first with opm_estimate — the preview is
free, and forward estimates are exact.
A solve, and an estimate of one, each need a balance of at least 100 work units before they will run — an
interactive session is checked once, when it starts. Below the floor you are told to top up rather than billed
for a surprise.
Interactive scenario operations settle one by one, as each result is delivered — every operation sits under the
delivered-work and no-negative-accounts guarantees. See Terms.
First Round on us: the first 100 accounts created between 17 August 2026 and
30 September 2026 each receive one free Round pack (400,000 work units,
$99 value). One per account, new accounts only, verified email required, no prior purchase.
Free units are used before any you buy and expire 31 December 2026 — unused units are forfeited and have no cash value. No
card is required to claim. Full terms: Terms.
Complete solves per pack on early / mid / late venture-backed archetype cap tables, measured from real runs — mid is the cap table published at /docs/claude. Actual work depends on structure; call opm_estimate for work_expected before you run.
How billing works: your AI previews each calculation's cost before running it — the service admits each job
against your balance and caps the charge at its own quote. Sign in, complete Stripe Checkout, manage payment
methods in the Customer Portal.
What a pack funds in practice — founder workflows with copy-paste prompts: Use cases
Setup: Get started · Machine-readable: /pricing.json