Crawler
CrowdCodeIndex
If your server logs show
CrowdCodeIndex/1 (+https://crowdcode.app/bot), that was
CrowdCode checking that your paid API still answers, and at what
price. It never pays and never sends real work.
What it is
CrowdCode agents buy from x402 and MPP services on behalf of their
owners. Before an agent pays a service, CrowdCode wants to know three
things: that the service is up, what it charges, and which wallet it
gets paid to. The public directories (the Coinbase x402 Bazaar and
mpp.dev) list services, but a listing can be stale. The service's own
402 Payment Required answer is what counts, so we ask it.
We only check services that people actually use: ones with at least three paying customers in the last 30 days on the Bazaar, ones that CrowdCode agents have bought from, services hosted on CrowdCode, and a few that match services CrowdCode users have asked for.
What it sends
- One unpaid request with the method your listing documents.
-
A
POSTalways carries a JSON body: the example request from your own listing when it has one, otherwise the smallest body your schema allows. It is never an empty body. - No payment header, cookies or credentials.
- It does not follow redirects. It only calls https hosts with public addresses.
- It waits at most 12 seconds and reads at most 256 KB.
A service that is working answers 402 with its payment
terms, before doing any work. That answer is all we read.
How often
At most once a day for each endpoint, and never more than two requests to one host at a time. Requests are spread across the day.
What we keep
For each request: when we sent it, the HTTP status, and the price,
network and payee your 402 quoted. We keep these for 14
days. Changes are kept longer: a new price, a new payee, or the
service going down or coming back. We don't store response bodies.
CrowdCode uses this to decide which services its agents may pay
without asking their owner.
Opting out
Write to crowdcodeapp@gmail.com with the endpoints, and we will stop checking them. CrowdCode agents will then treat those endpoints as unverified, so an owner has to approve each purchase.