1. Can the endpoint be paid?
Checks HTTP 402, accepts entries, manifest, price, network, facilitator metadata, OpenAPI, and freshness without sending payment.
Why aren't agents buying your x402 endpoint?
A listed endpoint can still lose the buyer before payment. Test the full path in one read-only check: payment readiness, catalog activation, buyer-task retrieval, budget and network policy, and public demand evidence.
50,968catalog endpoints in the dated source snapshot
73.23%reported zero calls in the source's 30-day window
13,645reported at least one call
2median calls among the active minority
Snapshot 2026-07-16T14:57:32Z from Agentic Market public services API. These counters are activity signals, not verified customer revenue.
Simulate one buyer journey
Use the exact job a funded agent should hire this endpoint to complete. Public URLs only; no wallet or API key.
Limited to three free diagnostics per hour. The analytics store only diagnosis classes and aggregate stage counts, never your URL, query, budget, or wallet data.
Your first blocker appears here
Ontario will not bury the answer in ten scores. It identifies the earliest observable stage preventing a likely purchase.
Catalog copy freshness
Buyer policy simulation
Alternatives the buyer saw
A point-in-time CDP Bazaar sample, not a global rank or traffic forecast.
Public Buyer Path Receipt
Next justified step
Request scoped helpModel pricing freeNo offer guarantees ranking, traffic, buyers, safety, settlement, or revenue.
2. Can a buyer find and select it?
Checks exact catalog activation and five deterministic buyer-task searches, including observed alternatives and Base-USDC price bands.
3. Would policy allow the spend?
Simulates the submitted budget, network, and evidence strictness. This is a policy test, not a real purchase or demand forecast.
Live metadata and catalog metadata can diverge
Ontario compares the description in the endpoint's current HTTP 402 challenge with the exact description returned by the sampled CDP Bazaar record. When they differ, the result is catalog_metadata_stale, not an automatic metadata-rewrite offer.
The correct action is to keep the live contract accurate and repeat the same buyer queries after the next genuine CDP-facilitated settlement. A self-payment is not customer demand and should not be used merely to refresh catalog copy. See the CDP Bazaar documentation.
What this result cannot prove
Ontario provides observable readiness, catalog, retrieval, policy, and public activity signals. It does not identify customers, verify independent revenue, guarantee future ranking, or certify that an endpoint is safe. Public call and payer counts may include self-funded tests, related parties, retries, or automation.