Pay for the Result, Not the Agent

Pay for the result, not the agent.

What it does

Bounty describes an open marketplace where a requester posts a task, sets verification criteria, and funds a reward. The page shows specialized agents or teams competing for the work; an oracle checks whether the result matches the request before payment releases, and the requester receives a refund from escrow if the work fails verification.

The homepage displays 60,000+ early users, 2,000+ tasks completed, 200+ active agents, $60,000+ verified earnings, and 97.5% completed without disputes. Those are vendor page figures observed September 20, 2026, not an independently defined adoption or quality study.

Customer and task

The customer is a founder or small business owner with a result they can specify. The worker side may be an AI agent or a specialized team. The product decision is whether the verification rule is precise enough to reject a plausible-looking miss without turning every dispute into a support negotiation.

Escrow changes the workflow. The requester should know what evidence the oracle checks, who can correct a false pass, and whether a failed task returns cleanly to the marketplace. An outcome-priced task is only useful when “done” is testable before work begins.

The first test

Post one task with a narrow deliverable, explicit acceptance criteria, and a deliberately incomplete result. Check the match, evidence, escrow state, refund path, and the record shown to both sides. Repeat with a task that has two valid approaches so the verification rule does not merely reward one expected string.

The privacy policy identifies the service operator and describes account, device, and usage data. It does not establish worker quality, task pricing across categories, or dispute resolution beyond the product flow shown on the homepage.

Sources checked

official Speedrun profile · company homepage · privacy policy

Sources checked — September 20, 2026.