reliability-v1

How CrowdCode decides which services are reliable

Before a CrowdCode agent pays for a service, CrowdCode looks up that service's state. The state comes from a short, versioned rule over evidence anyone can inspect, and every state comes with the reasons behind it.

The three states

reliable
The agent pays automatically, within the limits its owner set.
unverified
The agent asks its owner first, and shows the reasons. This includes every service CrowdCode does not track, and any endpoint it has never seen.
unreliable
The agent refuses to pay, and says why.

The rule

StateWhen
unreliableAny one of these: a CrowdCode operator blocked it, with a public note; the last 3 daily probes all failed; the payee changed in the last 7 days to an address the service's own 402 had not advertised; or there are 4 or more judged purchases in 30 days and fewer than 50% were delivered.
reliableNot unreliable, and all of these: a valid 402 in at least 2 of the last 3 daily probes; the latest price at most 2× its 7-day median; and at least 3 judged purchases in 30 days, with at least 80% delivered.
unverifiedEverything else.

The rule runs every hour, and again for a service as soon as it gets a new judged purchase. Each service's page names the rule version behind its state and publishes every number the rule read, so anyone can check the answer by hand.

Where the evidence comes from

  • Daily probes. Once a day CrowdCode sends each tracked endpoint one unpaid request (about the crawler). A valid answer is a 402 payment request naming a price and a payee. If the seller rejects the request body CrowdCode built, the probe is inconclusive: it is neither a failure nor a valid 402.
  • Judged purchases. When a CrowdCode agent buys from a service, a judge model reads what came back and records whether it was delivered, partial or not delivered, and CrowdCode signs that record. Partial counts as not delivered. CrowdCode's own test purchases count too, and they are labelled as test purchases.
  • Paid calls through crowdcode-mcp. These count as payers and show that a service is up. They never count as delivery.
  • Payees. A payee change counts only if the new address is one the service had not already advertised in its own 402, or registered with CrowdCode. A service that issues a new payee for every request, as confirmed by an operator, is not counted as changing.
  • Payers. Payer counts from the x402 Bazaar are shown for context. They decide what CrowdCode tracks and tests, not whether a service is reliable.

Right now

loading…

Reliable services

Check an endpoint