HTTP 402 and payment terms
Check status, accepts entries, resource URL, amount, asset, network, payTo, scheme, timeout, and facilitator context.
Agents can only choose what they can understand. Ontario reviews the public payment challenge, discovery metadata, x402 manifest, OpenAPI, MCP, and registry wording so your endpoint is legible before a provider-approved activation test.
The endpoint may work while its public descriptions disagree. This review focuses on the fields an agent, catalog, or developer must compare before paying.
Check status, accepts entries, resource URL, amount, asset, network, payTo, scheme, timeout, and facilitator context.
Review the v2 discovery extension, input and output schemas, examples, descriptions, and the request shape used for catalog inspection.
Align price, network, method, path, response shape, tool name, and capability descriptions across public machine-readable contracts.
Return the highest-impact blockers, corrected examples, registry and README wording, and a repeatable re-check list for your team.
Use the free Bazaar checker against the exact endpoint your buyers will call.
Correct metadata, schemas, manifests, and registry copy while keeping the public report fresh.
Rehearse on a supported testnet or sandbox, then approve any production payment yourself.
Confirm what was actually indexed. Placement, rank, traffic, and revenue remain unguaranteed.
Coinbase documents that Bazaar cataloging follows a successful settlement for a Bazaar-enabled route. Ontario can prepare the public contract and activation evidence; the provider remains in control of wallets, approval, settlement, and publication.
Use the official Coinbase Bazaar documentation for current extension and settlement requirements. Ontario's review is a provider-side readiness aid, not an official Coinbase service or endorsement.