Pay only on merge. Never for a failed attempt.

Ship the endpoint
you keep deprioritizing.

AI takes the first pass. A developer finishes what it can't close. You merge what you want and pay only when it ships.

Spec in ~60s · an AI pass costs a few dollars · pay only on merge

New taskspec in ~60s
Spec written. Acceptance criteria, files to touch, tests.
AI first pass
Developer finishes
Merged · paid

You pay only when the PR merges. Never for a failed attempt.

For teams

Outcomes, not hires.

  • AI takes the first pass at about $3 a task
  • A developer finishes what AI can't close
  • Specs are auto-generated, no scope debates
  • Pay on merge, never for a failed attempt
For developers

Real work, real bounties.

  • You ship the work that needs judgment, not the boring tickets
  • Specs are AI-generated and concrete, no proposals
  • Push a PR, get paid on merge, no interviews
  • Build a track record on real merged code

How it works

One task. AI drafts. A developer finishes.

AI writes the spec and takes the first pass. A developer finishes what AI can't close, then you merge what you want and pay on merge.

ISSUEAdd /versionendpointbounty-10001 · POSTkoduo02 · SPECAIfirst passDEVELOPERfinishes03 · WORKAIclaude-sonnetfirst pass…DEVELOPER@arjunfinishing…04 · BUILDPR #2draftPR #3✓ merged05 · MERGE & PAY✓ $100 PAID TO @arjun

Why Koduo, as AI gets better

AI eating more code makes us stronger, not weaker.

We bet on AI, not against it

As AI clears more of each task, our margin improves. An AI pass costs a few dollars; a human bounty costs more. So a task AI ships is our highest-margin task. AI getting better is the best thing that can happen to Koduo.

You pay for shipped code

AI tool subscriptions bill whether the code works or not. Koduo releases payment only when the PR merges, so you never pay for a failed attempt.

Describe the task, get the PR

We abstract spec, sandbox, execution, and review into one flow, across whatever mix of models and developers ships it best. Most backlog never gets done because nobody has time to open the tool. We do.

See it in action

From one line to a merged PR.

A real spec Koduo writes from a one-line task, then the PR that closes it. This is the actual output, not a mockup of one.

Specification

Add a GET /version endpoint that returns the current build SHA

Expose a lightweight read-only route that reads the build SHA from the environment and returns it as JSON. No auth, no DB access; covered by a single integration test.

Acceptance criteria

  • GET /version returns 200 with { sha: string }
  • SHA is read from the BUILD_SHA env var, falling back to 'dev'
  • Route is unauthenticated and adds no new dependencies

Test cases

  • ·Returns 200 and a non-empty sha
  • ·Falls back to 'dev' when BUILD_SHA is unset

Files

Modify

  • main.py

Create

  • tests/test_version.py

Pull request

MergedAdd /version endpoint

AI opened the first pass; a developer tightened the edge cases. The company merged it. Payment released on merge.

What it cost

A few dollars

When AI ships it alone, the API spend is the only cost. When a developer finishes it, you pay the bounty, on merge.

0%

AI-solved

$75

saved by AI

2

tasks shipped

4

tasks total

Every task AI ships is the highest-margin task. As AI does more, the economics get better. You pay only on merge.

For developers

Want to ship code? Browse open tasks.

Browse tasks