What happens when the fix cannot be verified?

The job is marked failed and no charge is created. You still see the reproduction test the agent wrote, which is often useful on its own.

Which languages and test runners are supported?

Python with pytest, and JavaScript or TypeScript with vitest, jest or node:test. Other stacks are declined at triage, free of charge.

What is in an attestation?

The exact patch, the reproduction test, the before/after test output, the runner image digest and timestamps — a JSON document you can share by URL.

codai Resolve

Bug fixes, proven by tests. No fix, no fee.

Submit a GitHub issue. Get back a patch with executable proof: a reproduction test written first, the fix that makes it pass, and your regression suite kept green. If Resolve cannot verify the fix, you pay nothing.

Start with Resolve See pricing

Python (pytest) and JavaScript/TypeScript (vitest, jest, node:test) repositories.

How it works

Reproduce → fix → verify → attest

Four steps, each one gated by executed tests. A charge can only exist after the last one.

01
Submit the issue
Point Resolve at a public GitHub repository and paste the issue, or a failing test command. Triage quotes a flat price in seconds — or declines free of charge.
02
Reproduce first
The agent writes a reproduction test that must fail on your current code before any fix is attempted. No reproduction, no bill.
03
Fix and verify in a sandbox
Candidate patches run in an isolated sandbox: the reproduction must flip to passing and your existing suite must stay green. Failed attempts are never billed.
04
Attestation, then payment
You receive a shareable proof: the exact patch, the reproduction test, before/after test output and the runner image digest. The charge exists only after the proof does.

The guarantee

You pay for outcomes, not attempts

No fix, no fee
Billing is wired so a charge can only be created after a verified attestation. Failures and infrastructure errors cost you nothing — by construction, not by policy.
Verification never fails open
A broken environment or a timeout marks the job as failed — never as "probably fine". Every claim in the attestation is backed by executed tests.
Proof you can share
Attestations are public-by-URL JSON documents. Hand the link to your team, your CI or an auditor — patch, tests and outputs are all there.
Minutes, not sprints
Typical single-function bugs resolve in under ten minutes end to end, including reproduction authoring and full regression verification.

Pricing

Priced per resolved issue, quoted up front

Triage reads the issue and quotes one flat price — from $7 per resolved issue — or declines for free if the bug is not a good fit. You are billed only on a passing verdict.

$7
Simple
Single-function bugs with a clear reproduction path.
$19
Standard
Multi-file logic bugs, moderate investigation.
$49
Complex
Cross-cutting bugs that need deep repository context.

Declined triage, failed attempts and infrastructure errors are always free.

Full pricing

Live proof

Real attestations from real jobs

The exact JSON a customer receives: patch, reproduction test, before/after test output, runner digest.

GitHub Action

Label an issue codai-fix — get a PR with proof

Drop a 15-line workflow into your repository and every labelled issue becomes a verified-fix attempt. The PR links the public attestation; failures comment the reason and cost nothing.

View the GitHub Action

FAQ

Questions before you submit

The public beta accepts public GitHub repositories. Private repositories run through the GitHub Action, which executes in your own CI with your own secrets.

Ship the fix. Keep the proof.

Start with Resolve Read the docs

Bug fixes, proven by tests. No fix, no fee.

Reproduce → fix → verify → attest

Submit the issue

Reproduce first

Fix and verify in a sandbox

Attestation, then payment

You pay for outcomes, not attempts

No fix, no fee

Verification never fails open

Proof you can share

Minutes, not sprints