Pricing and limits

Resolve prices the outcome, not the tokens — no fix, no fee. Triage quotes one of three flat tiers; you pay that amount if — and only if — the job ends resolved with an attestation. Declines, failures and infrastructure errors are always €0, and your first 3 verified fixes are free.

TiersCopy Anchor Link

Prices are in euro, the same €7 / €19 / €49 shown on codai.ro/pricing. Paid jobs are held on your prepaid codai wallet, which is kept in EUR. No exchange rate is applied anywhere in the pipeline.

The free tierCopy Anchor Link

3 verified fixes per user, across all your keys. It is claimed atomically when a quotable job arrives: the job is created already accepted with tier: "free" and quote_micro_usd: 0, and free_tier_remaining tells you what is left afterwards. A free job that ends failed or error returns its slot. Once the three are used, quotable jobs come back as quoted and wait for your accept.

Free jobs run a single fix candidate (greedy); paid jobs may fan out up to four — see How it works.

How you pay: a wallet holdCopy Anchor Link

Not enough balance: 402 and a top-up linkCopy Anchor Link

If your wallet cannot cover the quote, accept answers 402 and the job stays quoted — nothing is debited:

{
  "error": "insufficient_funds",
  "balance": 5000000,
  "required": 19000000,
  "currency": "micro_eur",
  "topup_url": "https://pay.codai.ro/checkout?topup=14"
}

balance and required are EUR micros. topup_url opens the pay.codai.ro checkout for the shortfall rounded up to whole euros, clamped to the checkout bounds of €10 minimum and €1000 maximum. Top up, then call /accept again on the same job id. The GitHub Action posts this link on the issue for you.

For a t7 job the 402 also carries "bundle_url": "https://pay.codai.ro/checkout?bundle=resolve10" — buying the fix bundle is an alternative to topping up.

Intro priceCopy Anchor Link

Your first paid fix costs €1. On your first paid accept — any of t7, t19 or t49 — Resolve holds €1 instead of the list price. While you are eligible, the 201 quote says so:

{ "status": "quoted", "tier": "t19", "quote_micro_usd": 19000000,
  "intro_price_micro_eur": 1000000, "list_price_micro_eur": 19000000 }

• The intro is used up only by a verified fix. If that job ends failed or error, the €1 is refunded like any hold and the intro is offered again on your next paid accept.
• You are eligible while you have no verified paid job and no other intro job in flight (accepted / running) — so two parallel accepts cannot both get €1.
• The accept response reports "paid_with": "intro" and "held_micro_eur": 1000000.

Fix bundleCopy Anchor Link

€49 buys 10 fix credits — about €4.90 per t7 fix instead of €7. Buy it at pay.codai.ro/checkout?bundle=resolve10.

• Credits pay only for t7 jobs. t19 and t49 always use the intro price or your wallet.
• A credit is taken at accept instead of a wallet hold ("paid_with": "credit", "held_micro_eur": 0), returned on failure or error, and consumed only by a verified fix.
• GET /v1/resolve/balance returns fix_credits, intro_available and wallet_micro_eur.

Which one pays: precedenceCopy Anchor Link

At accept Resolve picks the first that applies: free tier > intro price > fix credit (t7 only) > wallet. paid_with on the accept response (and on GET /v1/resolve/jobs/{id} once accepted) tells you which was used. One exception protects you from a needless 402: if the €1 intro hold does not fit in your wallet but a credit is usable on that t7 job, the credit is used instead.

You can see the upstream model cost per job (not what you pay — what Resolve spent) as cost_micro_usd on GET /v1/resolve/jobs/{id}; it is the sum of gateway usage under the job's session ids.

We never spend more than 2× your quote on model calls for one job (a fixed $2 ceiling for free jobs). That ceiling is ours to absorb — it never changes what you pay.

LimitsCopy Anchor Link

All limits are per user, counted across every key you own.

Caps are checked before triage, so a rejected submission costs neither a slot nor a triage call. The day resets at 00:00 UTC; every 429 body is the flat { "error": "<message>" } shown above, with no Retry-After header.

TimeoutsCopy Anchor Link

Triage runs inline in your POST and is bounded by the gateway's request timeout; a slow triage returns declined with triage unavailable, please retry rather than hanging.

Supported repositoriesCopy Anchor Link

• Public https://github.com/<owner>/<repo> only. Private repos, other hosts and monorepo sub-paths are rejected at submission with a 400.
• Python with pytest, or JavaScript/TypeScript with vitest, jest or node:test (detected from package.json).
• The repo's suite must run from a clean clone plus its committed dependency manifest. Tests that need secrets, running services or system packages beyond the runner image usually end in declined or error.