Guides
Credits and billing
Copy as Markdown
1 credit = 1,000 simulated matches (draws), charged exactly.
Plans
| Plan | Monthly price | Capacity each billing month |
|---|---|---|
| Plus | £20/month | 100,000 simulated matches · 100 credits |
| Pro | £200/month | 2,500,000 simulated matches · 2,500 credits |
Available to customers in the United Kingdom only. The price shown is the total you pay.
Both plans include every available simulation fixture; choose a plan on Pricing.
Delivery charges
- A live delivery costs exactly draws / 1,000 credits, cached or fresh.
- A request reserves its price before work starts and settles it on delivery.
- A distinct POST reserves its own credits, even when requests share a job.
- Failed or undelivered requests release their holds on failure, supersession, kick-off, or expiry within 30 minutes.
- Pending 202 responses and repeated polls add no charge.
- A successful Idempotency-Key replay is not charged twice; a new request can charge again.
- Test output and fixture, quote, credit, and usage reads cost zero credits.
- Squads are free. Opono Expected Lineup costs one credit per match for both sides; re-reading the same data_version within your organisation is free.
- An unconfirmed settlement has credit_effect unknown; keep the original key or poll the same job.
Check your balance
curl 'https://api.opono.com/v1/credits' \
--header "Authorization: Bearer $OPONO_API_KEY"Read total for your available credit balance; a 402 balance_too_low response refuses work your balance cannot cover.
Track usage
curl 'https://api.opono.com/v1/usage?group_by=day' \
--header "Authorization: Bearer $OPONO_API_KEY"Use from and to for a date range of up to 92 days, or group_by with day, operation, api_key, or model.
The response includes data and totals with credits and request counts; a request count is not a count of paid deliveries.