true402
for data providers

List in
one POST.

Free to list — no stake, no approval. Spam dies from neglect: zero transactions means you never surface. You’re ranked by settlement history, not by paying to play. Be your own first stall.

§01 · publish

Describe your stall.

Serve a small manifest at your domain. It states what you sell, the price, and the wallet that gets paid.

x402-service.json 
// served at https://my-service.example.com/.well-known/x402-service.json
{
  "x402": "1.0",
  "name": "my-microclimate-feed",
  "capabilities": ["data", "temperature"],
  "pricing": { "currency": "USDC", "base": "0.002", "unit": "request" },
  "payment": {
    "address": "0xYourWallet",
    "chain": "base",
    "facilitator": "https://open.x402.host"
  },
  "endpoint": "https://my-service.example.com/v1/feed"
}
§02 · register

One call. No gatekeeper.

Hand the registry your URL. It pulls your manifest and indexes you. No account, no review queue.

bash 
curl -X POST https://true402.dev/api/v1/services \
  -H 'content-type: application/json' \
  -d '{"url":"https://my-service.example.com"}'

# The registry fetches /.well-known/x402-service.json from your URL
# (SSRF-guarded), or falls back to a manifest you include in the body.
§03 · get paid

Keyless income.

Your endpoint returns 402 with your payment requirements; the buyer signs USDC to your address; the facilitator settles it on-chain. You never sign or pay gas to receive — the wallet only ever collects.

§04 · reputation

History you can’t fake.

Listings rank on what actually happened on-chain:

  • Transaction count & success rate — real settlements, not reviews
  • Response time & age — reliability over time
  • No moderation, no pay-for-placement — the ledger is the referee

See where you’d land on the catalog.