Ontario Protocol.
x402 pre-payment decision playbook

Compare x402-paid APIs for Coinbase Bazaar publishers

The buyer or agent needs structured choices, not a flat list of claims. This playbook maps the decision to observable Ontario evidence so an agent can fail closed before payment.

Compare paid APIs Bazaar teams No-payment first
Decision question: Can Coinbase Bazaar publishers rely on this x402 endpoint without listed services that are payable but not agent-readable?

Only after Coinbase Bazaar publishers can inspect benchmark score, payment correctness, price clarity, schema quality, network clarity, and report history. If the evidence is missing, stale, or contradictory, the agent should fail closed.

Required evidence

  • Confirm the endpoint maps to a real payment resource for service teams preparing x402 metadata before marketplace discovery.
  • Require benchmark score, payment correctness, price clarity, schema quality, network clarity, and report history.
  • Reject when there is unclear price, no payment metadata, no report history, or benchmark rows without safety flags.
  • Link the final decision to a public report, manifest, benchmark row, or policy outcome.

Reject conditions

Reject or send to human review when there is unclear price, no payment metadata, no report history, or benchmark rows without safety flags.

Do not let a positive-looking badge or directory row override a stale or contradictory live check.

Agent workflow

  1. Start with the no-payment evidence path.
  2. Run the Ontario verifier or policy endpoint shown below.
  3. Compare live endpoint behavior against manifest and discovery metadata.
  4. Store the report_id or policy decision with the agent's payment log.
  5. Send the payment only when the agent's own policy allows it.

Command or probe

curl 'https://ontarioprotocol.com/api/benchmarks?protocol=x402'
# Use benchmarks to shortlist, then verify the chosen endpoint directly.

Primary Ontario surface: /api/benchmarks?protocol=x402

Sourceability note

Search Console showed early impressions for live benchmark and comparison pages.

KPI: more listed services with fresh readiness reports.

Trust boundary

Ontario Protocol provides readiness and trust signals based on observable endpoint behavior, manifest metadata, payment challenge behavior, report history, and public evidence. It does not guarantee endpoint safety, service quality, financial outcome, or future behavior.

Open x402 benchmarks Run verifier Browse discovery Read trust boundary