llms.txt — documentation index for LLMs and agentsllms-full.txt — full documentation corpusMarkdown version of the documentationskill.md — agent skill filePaddock MCP server descriptor
— Index governance

How a Paddock index is governed.

Four documents. Together they are what a third party — an exchange, a HIP-3 perp deployer, a licensee — has to be able to read before deciding whether a Paddock index is safe to settle against.

Published Documents 4Changes dated in the corrections log
01
Methodology spec
What is in the index, why, and on what basis is it weighted?
02
Rebalance calendar
When does it change, who is told, and what happens when the basis changes?
03
Appeals process
If we are wrong about a constituent, how does it get fixed and how fast?
04
Conflict policy
Can a constituent buy its way in or up?
Status — read this first

No Paddock index is currently live. The Agent Commerce Index is suspended, not retired: no new monthly print is computed, existing prints are retained unmodified, and it resumes only under a new version tag once the recipient-list truncation is fixed and the attribution basis is recomputable.

These documents are therefore specification, not description. They define how an index would be governed if one were published. Nothing here should be read as a claim that a governed index exists today.

The commitments are not conditional on that. The service levels in §03.3 and the four firewall rules in §04.1 are promises to third parties, in force from 2026-08-27. They bind Paddock whether or not an index is running, and a change to any of them is a dated entry in the corrections log, never a silent edit.

03.3

The appeals service levels

Printed here in full, not summarised. Business days are Monday to Friday, UTC, and the clock starts on receipt of the appeal, not on receipt of a complete one. Full process: 03 · Appeals process.

Acknowledgementwithin 5 business days of receipt

Paddock acknowledges an appeal within 5 business days of receipt. The acknowledgement confirms receipt, issues a reference the appellant can quote, and — where the appeal is incomplete — names exactly what is missing.

Resolutionwithin 30 calendar days of acknowledgement

Paddock resolves an appeal within 30 calendar days of the acknowledgement, with a written decision stating the outcome and the evidence relied on.

Extensioncommunicated before day 30

If a resolution needs more time, Paddock communicates the extension before day 30, with a new date.

04.1

The firewall

Four sentences. Everything in 04 · Conflict policy is those four applied to a specific situation.

  1. 1Constituents never pay for inclusion.
  2. 2The index never carries a payable ranking.
  3. 3A deployer conditioning the licence on constituent changes is a refusal.
  4. 4Paddock never operates a market, facilitator, or gateway.

Two rules inherited from everything else Paddock publishes

These are not restated in every document; they apply throughout.

Never divide across universes.

Every figure names its universe — census (Total Settled Volume), attributed, or verified-mapped. A numerator from one and a denominator from another produces a real-looking number on a basis that does not exist. See the methodology.

A changed basis is a discontinuity, not a data point.

Any methodology change that moves a published figure is recorded, dated and annotated in the series. Silently fixing an old value destroys the thing a dated series is for. See §02.4.

Something on these pages wrong, or a row you want to contest? File an appeal, or write to [email protected]. Paddock is the independent data layer for AI agent commerce, and publishes its own bad news — corrections to anything here go in the public corrections log whether or not anyone noticed.
— Keep going

What to read next.

Monthly intelligence
Read the report.

The State of Agent Commerce — the citable monthly report on what AI agents actually buy.

See the report →
x402 market
What agents pay for.

Real transaction volume by category. Three sources merged into one live table.

See the market →