Methodology

Money2046 publishes advertised vs settled for machine payments — fee, settle time, fail — with dispositions and evidence IDs. Card spend and MYR corridors are secondary subgraphs. Two audiences, one object: agents read /agents.md; humans cite this page and research.

Verification rules

1. Never invent a number. Fees, settle times, availability, and counts fail closed. INSUFFICIENT_EVIDENCE is a correct answer.
2. Dispositions are the only truth. See the vocabulary.
3. Never rank on SCHEMA_ONLY. agent-index.json emits ranking: [] until its gates pass.
4. Pending evidence is invisible in public feeds except as a count in meta.
5. Discovery quotes are not settlements. A method: X402 QUOTE is still a QUOTE. It never enters the agent index.
6. No volume board. We do not rank on volume, user counts, or payToCount.
7. The free index is delayed. Settlements captured in the last 7 days are LOCKED on the free pages and omitted from the public agent-index.json. QUOTE rows stay labeled QUOTE. A paid plan unlocks only after Airwallex confirms the payment. We charge you in USD.

Dispositions

Machine-readable enum. Agents treat everything except VERIFIED_FRESH as non-factual. Anchors are stable.

• SCHEMA_ONLY — schema or estimate; zero verified evidence. Do not rank.
• VERIFIED_FRESH — verified within 30 days. Fact.
• STALE_REVERIFY — was verified; older than 30 days. Re-verify before reliance.
• UNAVAILABLE — not eligible in the stated jurisdiction.
• INSUFFICIENT_EVIDENCE — cannot score. A correct answer, not a stall.

Evidence permalinks

Every published number carries a stable URL. Observations live at /evidence/{id}/. Route quotes keep /receipts/{id}/. Listing-shape epoch counts cite /epochs/#{epoch_id} (named exemption: not an observation or payment count). The element convention is data-evidence-id on an <a> whose href resolves. An unlinked measurement fails the build (EVIDENCE LINK FAILED). Zero marks also fail — deleting the attribute cannot satisfy the gate. Each publishing surface declares data-evidence-surface: measurements requires ≥1 mark on that page; hole-only requires zero measured cells. The committed list is src/data/evidence-surfaces.json — evidence-page self-links cannot satisfy the observatory. The gate prints how many marks it checked across how many pages. SCHEMA_ONLY estimates are not measurements and must not carry the attribute. HOLE cells stay unmarked.

What we measure

• Agent rails (primary) — wallet capability map (SCHEMA_ONLY), labeled x402 bazaar polls (QUOTE), measured FEE / SETTLE / FAIL from OPERATOR_PROBE settlements.
• CHAIN flow (gated) — on-chain joins to versioned registry epochs. See below. Local collector only until the addendum gates pass.
• Card spend / corridors (secondary) — measured FX and MYR landed cost when settlements exist; schema models stay labeled.

CHAIN addendum

No aggregate payment count renders on a page, in a feed, or in a docs example unless every gate in docs/chain-addendum.md holds. Binding points:

• Only provenance CHAIN may enter a published on-chain aggregate. OPERATOR_PROBE and COMMUNITY are a different object (the agent index).
• Every discovery poll is a registry epoch. Retired payTo addresses stay attributable. Unversioned joins are refused.
• Batched settlement (Circle Gateway, Nanopayments, aggregator nets) is excluded from call-level counts — per-call attribution is invalid.
• Any CHAIN surface must disclose attributionPrecision, epochIds, joinRule, and epoch. Those values are pinned by assertChainFlowPayload — invented members and incoherent UNJOINABLE / epochIds / VERIFIED_FRESH tuples fail the build.
• Outlier and single-address concentration gates refuse the window rather than guess.
• Still never renders: volume ranking, user counts, payToCount.

The public CHAIN payload is allowlisted (/data/v1/chain-flow.json): extra keys including payToCount fail the build. The feed census-guard is a name-shaped tripwire on the other feeds, not a semantic guarantee. Abbreviations (vol_usd) and invented names (nPayments) escape.

Registry epochs (listing shape)

The full local snapshot is not a public feed. A listing-shape projection may ship: /epochs/ and /data/v1/registry-epochs.json. Address and listing counts are allowed. They are never activity, usage, or adoption; they are never joined to transfer rows; they are never trended as growth. Transfer and payment counts are not. Publishing the bazaar’s address set does not make a CHAIN payment aggregate publishable.

What we don't do

• No fabricated payout screenshots
• No "guaranteed returns" language
• No ranking on SCHEMA_ONLY wallets or discovery resource counts
• No affiliate-first rankings — commissions are disclosed, never the ranking criterion

Affiliate disclosure

Money2046 may earn commissions from links. This never changes a ranking — a provider that pays us and a provider that doesn't are compared on the same verified numbers. You can check any claim in the Watch.

Disclosure: Money2046 publishes receipts for agent payments: fee, time, fail, facilitator, chain — or INSUFFICIENT_EVIDENCE. Not financial advice. Evidence can be insufficient. We charge you in USD. Payment processing by Airwallex. Money2046 does not move customer funds and is not a wallet, an exchange, or a payment processor.