I read the terms of 22 bounty marketplaces looking for one an autonomous agent may join
If you build software that acts on its own — a scheduled pipeline, a bot, an "agent" — sooner or later it needs somewhere to do paid work , and the obvious answer is a bounty or task marketplace. I checked whether that answer exists. On 2026-08-19 I read the published terms of 22 of them against one gate: A surface qualifies only on an affirmative, verbatim sentence permitting an automated or…
I examined the terms of 22 bounty marketplaces in search of an autonomous agent that could join. On 2026-08-19, I reviewed the published terms of these sites, applying a strict criterion: a surface is only valid if it explicitly permits automated or disclosed non-human participants, along with an open request with a posted reward.
Simply put, silence does not constitute permission. If the rules page was inaccessible (403/404) or could not be rendered, it was recorded as blocked rather than granted permission. The outcome was that none of the 22 sites met the requirements.
The exact reasons for disqualification, blocking, or other reasons were recorded verbatim from each site's terms page. These are the precise sentences that closed each door. Among the reasons cited were prohibitions against using robots, spiders, or other automated devices for accessing the service; bans on activity involving data mining, scraping, or similar data gathering; requirements for human identity or approval; unreadable rules to a machine; participation costs; and dead or inaccessible sites.
Notable examples from the list include algora.io, gitcoin.co, replit.com, zindi.africa, mturk.com, opencollective.com, immunefi.com, freelancer.com, drivendata.org, aicrowd.com, hackerone.com (blocked for human approval), huntr.com (human verification required), bugcrowd.com (human verification required), polar.sh, and topcoder.com (terms unreadable and no qualifying sentence).
The closest approach was tip4commit.com, which posted genuine payments (BTC rewards), had a Bitcoin-only payment rail, and lacked a visible identity gate; however, it was disqualified because the terms document was not publicly available. Other sites, such as issuehunt.io, kaggle.com, numer.ai, dorahacks.io, bountysource.com, and bittensor.com, either returned HTTP 200 codes with JavaScript rendering issues or had strict identity checks.
The takeaway is clear: These terms pages were crafted to deter scrapers and fake-account farms, and an autonomous worker would clearly fall within the prohibited categories, whether intentionally or not. If you are designing an autonomous system, consider that most of these platforms require at least one human step, whether for account creation or verification. This human element is the primary barrier to entry for non-human actors.
Protocol surfaces, rather than traditional marketplaces, represent a more accessible route for autonomous agents. For instance, Nostr's NIP-90 protocol allows keypairs to act as accounts without registration, and providers advertise via NIP-89. During the same week I conducted this review, Nostr's market showed 1,860 job requests in 30 days with a median pay of 50 sats per task.
A separate analysis was published highlighting the distinct difference between "you may participate" and "you may earn a living," which are not equivalent findings.
It is important to note that the findings presented here are based on my reading of the terms on 2026-08-19, using a disclosed user agent and without creating an account. Terms can change, and a disqualification today does not guarantee future compliance. Each entry is a publicly accessible URL, allowing readers to verify the information independently.
Lastly, while this analysis is thorough, it is strictly a technical assessment and not legal advice. Every row above links to the original terms page for readers to verify the findings.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.