_done

_done is an API marketplace built specifically for autonomous AI agents. It offers around 25 cloud APIs that handle tasks language models can't reliably do on their own, things like DNS lookups, port scanning, cryptographic hashing, QR code generation, and OCR. The twist is how payment works. Instead of signing up for accounts, managing API keys, or setting up billing, agents pay per call using USDC on the Base or Solana blockchain. No human has to intervene.

The problem it addresses is practical. AI agents can reason and generate text, but they struggle with deterministic operations like computing a SHA256 hash, validating a webhook signature, or extracting text from an image. These tasks require external services, and most services assume a human is registering, verifying an email, and entering a credit card. _done removes that friction by accepting micropayments directly from the agent at request time.

Under the hood it uses the x402 protocol, which implements HTTP 402 Payment Required as an actual payment flow. When an agent calls an endpoint, the server responds with a payment request. The agent signs and broadcasts a small USDC transaction on chain, the server verifies it, and the response comes back. Average response time is under two seconds. Minimum cost per call is one cent, though some endpoints charge more based on compute.

The API catalog spans several categories. Network tools include DNS lookup, WHOIS, port scanning, and IP geolocation. Security tools cover hashing, HMAC verification, and webhook signature validation. Parsing tools handle JSON, SEO meta extraction, and sitemap parsing. Data tools pull US CPI reports and Hacker News feeds. Conversion tools generate QR codes and run OCR on images. There's also a mortgage calculator and a Leetspeak translator for lighter use cases.

Documentation is straightforward. Each endpoint has an OpenAPI spec the agent can retrieve, so discovery and invocation can be fully automated. The design assumes agents will call these APIs without human oversight, which is why there's no dashboard, no key rotation, and no usage limits beyond what you're willing to pay per call.

_done fits developers building agentic systems who want their agents to perform real world operations without manual account provisioning. If you're wiring up an agent that needs to verify DNS records, hash a payload, or scan ports, you can point it at _done and let it pay its own way. The model scales naturally because there's nothing to pre authorize and no monthly minimum.

It's a narrow product with a clear use case. If you're not building autonomous agents, you probably don't need it. But if you are, and you've hit the wall where your agent can't do something deterministic without a human setting up an API account, this is the kind of infrastructure that unblocks that.