Settlement evidence before demand claims

Was it a customer, or just a transaction?

Inspect a Base USDC receipt and classify the observable payer relationship. Ontario reports direct self-payment, user-declared related-party payment, or unattributed evidence without turning an unknown wallet into a fake customer claim.

FreeOne receipt, no wallet or API key.

0.02 USDCMachine-readable batch report for up to 20 receipts.

$199Human-reviewed provider audit for up to 500 receipts.

Check one receipt

Inputs are used for this request and are not stored by the checker.

Payer-

Recipient-

Amount-

Independent demand-

Why this exists

Transaction volume is not the same as independent demand

A July 2026 empirical study of x402 activity on Base reported 21.20% of observed settlements as fictitious and 63.78% as internal within linked clusters under its methodology. The useful product response is not suspicion by default; it is a reproducible evidence boundary.

Apply the research with the free demand-claim calculator · Read the primary study

Direct self-payment

The observed USDC payer and recipient are the same address. This is not independent demand.

Declared related-party

The payer and recipient both appear in the submitted related-address set. The classification is only as complete as that disclosure.

Unattributed

Unattributed does not mean independent demand. No disclosed relationship was established, but this does not prove a customer, an autonomous agent, or an HTTP x402 call.

Agent-priced batch report

Give a buyer crawler a task worth 0.02 USDC

The paid endpoint analyzes up to 20 receipts, reports payer concentration and relationship classes, and returns a canonical evidence digest. Probe first to inspect its x402 v2 challenge.

curl -X POST https://ontarioprotocol.com/api/x402/demand-authenticity-report \
  -H 'Content-Type: application/json' \
  -d '{"tx_hashes":["0x..."],"related_addresses":["0x..."]}'

Review the $199 provider audit Inspect the paid OpenAPI contract

Evidence boundary: Ontario can observe Base USDC transfers, EIP-3009 authorization events, declared relationships, recipient matches, and concentration. It cannot prove from a receipt alone that an HTTP x402 request caused a payment, that an unknown payer is independent, or that future demand will continue.