← Money Reactor / blog
2026-10-18. All endpoints below are live in production and take less than a minute to call: money-reactor.makar52nn2016.workers.dev.
Every traditional API integration starts with the same friction loop: find the provider, open an account, verify an email, generate a key, store the key, keep a subscription alive. For an autonomous agent this loop is not just annoying — it is usually a hard stop, because signup flows assume a human with an inbox and a credit card. The x402 protocol removes the loop entirely: an endpoint that wants to be paid answers the first request with HTTP 402 and a machine-readable price; the agent signs one USDC payment on Base and retries; the data comes back. No account is ever created, no key is ever issued, and the per-call price can be as low as a tenth of a cent.
| Endpoint | What an agent gets | Price |
|---|---|---|
/api/bounties | Multi-source funded-bounty radar (Superteam Earn + GitHub + GitLab) with honeypot trust scoring and GO/CAUTION/SKIP verdicts | $0.01 |
/api/token-verdict & /api/verdict | On-chain token verdict: contract signals, risk flags | $0.01 |
/api/crypto-price | Live crypto prices (e.g. ?symbol=BTC-USD) | $0.001 |
/api/crypto-news | Aggregated crypto headlines for market-aware agents | $0.001 |
/api/honeypot | Trust scan of any GitHub repository (honeypot risk score) | $0.001 |
/api/erc20-balance | On-chain ERC-20 balance for any wallet/contract pair | $0.001 |
/api/url-to-text | Clean, LLM-ready text extraction from any URL | $0.001 |
/api/weather, /api/uuid, /api/time, /api/block-number | Utility probes — also the canonical endpoints for testing your own x402 client stack | $0.001 |
A free demo of the flagship feed (same schema, truncated data) lives at /api/bounties/demo, and the full machine-readable catalog is published as openapi.json and llms.txt for boot-time discovery by agents.
Three buyer profiles show up repeatedly. First, agent developers testing payment flows: they need a real x402 endpoint to verify their client stack settles correctly, and a penny-priced UUID or block-number probe is the cheapest possible integration test. Second, agent builders wiring market awareness into trading or research loops: they would rather pay fractions of a cent per fresh price, headline, or balance than run their own polling infrastructure against rate limits. Third, human operators — solo developers and analysts — who use the same endpoints from a terminal as a zero-signup research shortcut. Because settlement is per call, all three can burst from zero to thousands of calls and back without talking to anyone.
There is genuinely nothing to register: no email, no key, no dashboard. The payment itself is the identity — the 402 challenge specifies an exact amount and a receiver address on Base, the client pays from any wallet it controls, and the settled transaction is the receipt. This has a practical consequence for budgeting: an agent's spend limit is just its wallet balance, and a parent process can cap exposure by funding the hot wallet with exactly the amount it is willing to lose. There are no invoices to reconcile and no subscriptions to remember to cancel; the cost structure ends when the calls end. That asymmetry — integration cost near zero, walking-away cost exactly zero — is the reason per-call micropaid APIs fit autonomous software better than any account-based model.