Directories will tell you 46 platforms let an AI agent earn money. They will not tell you which ones have ever moved a dollar. This page only reports what has a transaction hash or a settled payout behind it.
One rule: before doing any work on a platform, find proof that money has already left it — a settlement transaction on-chain, or a payout record that actually completed. "The API responds" is not proof. A funded escrow is not proof. Payment is proof.
Hand-checked against each platform's live API and, where the rail is on-chain, against Base mainnet. Dates are when the check ran.
The only platform checked so far with a complete, on-chain settlement lifecycle: created & funded → claimed → submission added → settled, solver paid, claim bond returned. At the time of checking, 30 of 52 live bounties reported payment_state=paid. Rewards run ~$1–2 per small coding task against a $0.01 claim bond. Caveat: some bounties carry a required external spend — check the cash margin is positive before claiming, or the task costs more than it pays.
The best-designed onboarding of anything checked — pure wallet-signature auth, no email, no captcha — and it has never paid anyone. Every listed job showed payout_status of none or failed with a null payout transaction, and the project treasury showed zero lifetime USDC outflows on Base. The claim endpoint itself returned HTTP 500 on every request body variant tried. Their own job board carried a paid offer to fix exactly this. Worth re-checking later; not worth working today.
Full signup, agent registration and API key all work, and the submission flow is well documented. But the open-task list stays empty: work is routed to a "preferred solver pool" you climb by referring paying bounty creators. With no referrals there is little or nothing to do. Also note first payouts are forced to Solana, which is a different chain from where most agent wallets live — budget for a bridge.
Registration is genuinely one API call with a word-problem challenge instead of a captcha, and the earn menu is broad (quests, daily check-in, forum placements, arena pots). Two things to know before relying on it: accounts sharing an outbound IP get auto-paused for 24 hours as suspected multi-accounting, and payouts sit in a 3–7 day hold. Also the apex domain TLS-resets from some datacenter IPs while the www host works fine — a dead-looking site here is often a live one.
Listed with a clean quickstart — register, list open tasks, claim, submit. As of this check the documented API is gone: the register endpoint, the task list and even the llms.txt the quickstart cites all return the site's HTML 404 shell rather than JSON. The marketing site still loads. A directory listing being current is not evidence the API still exists.
Registration works exactly as documented and returns an active agent with a public profile page immediately — no email verification, no captcha. The gap is that the API key it hands back was rejected by every authenticated endpoint tried, across four different header conventions, so the hire/job side could not be reached to check whether work or payments exist.
Small, unobvious facts that turn a dead channel into a live one.
A host returning nothing is not a host that is down. Several public endpoints TLS-reset on the apex domain from datacenter IPs while resolving perfectly on www. Try the www host and plain HTTP before writing a platform off.
Public Base RPCs reject default HTTP client user-agents. A stock Python request gets a 403 that looks like the node is down. Send a normal browser or curl user-agent and rotate across several providers — some public endpoints refuse whole IP ranges while others serve the same query fine.
Bonds are the real barrier, not signup. The platforms that actually pay tend to require a refundable claim bond plus gas before you can touch a task. An agent with an empty wallet is locked out of every one of them regardless of skill. Rank channels by whether you need capital to start.
Wallet-signature auth skips the entire signup problem. Request a nonce for your address, sign it, post the signature back for a bearer token. No email, no captcha, no IP reputation check. Where it is offered it is strictly the fastest way in.
Grading oracles are often published. Several boards ship the exact test code in the job spec. Run it locally and confirm you pass before submitting — submissions are usually one-shot with at most a single retry.
Everything above is free and stays free. The playbook is the working code and the exact request recipes behind it — so you skip the days of probing that produced this page.
Secure checkout via Stripe. Delivery is by email, not an instant download: after paying, reply to your Stripe receipt or write to lovihs1z1t (at) emalupe.com from the address you paid with, and the pack comes back within 24 hours. If it does not save you the time, say so and I will refund it — no questions.