Data sources and licences
Paddock has no indexer. One nightly job makes a handful of HTTP requests and stores what comes back. Almost every figure we publish is a number an upstream already computed, re-served with its universe, its basis and its capture date attached. This page is who those upstreams are.
What Paddock adds is not collection — it is the methodology on top: consistent universes that are never divided into each other, wash and circular detection with a published version and a detection date, payTo wallet attribution, and an unbroken dated series. See the methodology for how each figure is computed, and the API docs for what each field means.
- What we take
- The settlement census — total settled volume, transaction counts, unique buyers, and the per-recipient seller list that every attribution figure is built from.
- Where it appears
- Total Settled Volume · Attributed Volume · Verified Mapped Market · ASV · get_market_summary · get_provider_revenue · the settlement-recency block in verify_before_pay
- Licence
- Public API, no licence asserted. Read-only, attributed here and in the methodology.
- Note
- Figures are re-served as the upstream computes them. The rolling-24h basis of its per-recipient list is stated wherever we sum across days.
- What we take
- The x402 resource catalogue: declared endpoints, their payTo wallets and advertised prices — the join that turns a wallet into a named seller.
- Where it appears
- payTo wallet attribution · category assignment · the listed-price comparison in verify_before_pay
- Licence
- Public API, no licence asserted.
- What we take
- Independent HTTP liveness probing of agent-commerce endpoints: success rate, latency distribution, sample counts.
- Where it appears
- get_liveness · the reliability input to get_best_value_provider
- Licence
- Public API, no licence asserted.
- Note
- Captured nightly. Its success rate is that prober's numerator over its own attempts — it is not, and is never presented as, a success rate for the payment path.
- What we take
- The MPP (Machine Payments Protocol) service directory, tracked as a listing count.
- Where it appears
- The MPP rail row in the rails table
- Licence
- Public API, no licence asserted.
- Note
- Engagement, not settlement. MPP settlement is not yet captured and no MPP volume figure is published.
- What we take
- Registered MCP server counts.
- Where it appears
- Ecosystem context in the monthly report
- Licence
- Open registry.
- What we take
- Stars, forks and push activity for the protocol repositories.
- Where it appears
- Developer-engagement proxy in the monthly report
- Licence
- Public API under GitHub's terms.
- Note
- A developer-engagement proxy, never presented as settlement.
- What we take
- An independent paid-verification census: a third party pays x402 endpoints with real USDC and publishes whether a valid response came back, with the settlement transaction hash.
- Where it appears
- The paid_fulfillment block in verify_before_pay
- Licence
- Portions of paid-fulfillment data © nohumans.directory, licensed CC-BY 4.0.
- Note
- Paddock does not buy from sellers, and does not plan to. This is somebody else's purchase record, re-served with its own verdict dates attached and never combined with any figure we measure. Coverage is partial and the response says so; a verdict describes behaviour at a point in time.
Portions of paid-fulfillment data © nohumans.directory, licensed CC-BY 4.0. Source: https://nohumans.directory.
Re-served in the paid_fulfillment block of verify_before_pay only. Each verdict carries the date it was observed by the source and the date we captured it — those are different, and both are on the response. Paddock does not pay endpoints and does not plan to; this signal is somebody else's purchase record and is never combined with anything we measure.