Validate and verify free. When the evidence is ready, pay 0.50 USDC through x402 to publish a provider profile with a live readiness scan, public evidence link, and conditional strict-discovery eligibility.
For providers that already have a public x402 endpoint and want a machine-readable profile with current readiness evidence.
The paid response includes:
Boundary: The 0.50 USDC payment buys submission processing, a public listing, and readiness evidence. Canonicalization only removes duplicate records for the same endpoint and method; it does not buy a ready grade, ranking, traffic, agent purchases, catalog acceptance, safety, or future visibility.
After publication: Refresh the profile's readiness evidence for 0.10 USDC through the self-serve refresh API. Payment updates the observation only; it cannot buy a better score or placement.
Self-serve publication does not require a sales conversation. These qualified scopes are for catalog work, repairs, monitoring, or policy implementation that cannot be delivered by the automated product alone.
Builders deciding whether an x402 endpoint or public repository is worth fixing.
Scope: One public endpoint or repository URL.
Providers whose free buyer-conversion diagnostic found one bounded readiness, catalog-activation, or buyer-retrieval blocker.
Scope: One public endpoint, one allowlisted diagnosis, and one agreed evidence outcome.
Boundary: No invoice is issued merely for diagnosis or submission. The $49 invoice exists only after the agreed public evidence outcome is delivered. Major code changes, wallet actions, third-party fees, or production settlements require a separate explicit scope and are never assumed.
Providers with one public x402 endpoint or remote MCP server that is technically ready but still absent from agent catalogs.
Scope: One provider, one public endpoint, one remote MCP URL when available, and up to three agreed catalog surfaces.
Boundary: The $49 pilot invoice is issued only after at least two agreed catalog surfaces are visibly live. Provider accounts, ownership confirmations, wallets, and any settlement remain under provider control. Catalog acceptance, ranking, traffic, safety, and revenue are not guaranteed.
Teams preparing one paid endpoint and MCP server for agent catalogs.
Scope: One public repository, one public x402 endpoint, and one MCP Registry record or remote when supplied.
Builders who need one concrete x402 blocker explained and verified before a larger launch project.
Scope: One saved readiness report for one public endpoint.
Providers whose endpoint is already cataloged but does not appear for the concrete tasks paying agents search.
Scope: One public x402 endpoint and up to five public buyer-intent phrases.
Boundary: Ontario does not self-pay to influence rank, publish unsupported claims, perform wallet settlement, or guarantee catalog ordering, traffic, buyer reach, safety, or revenue.
Agent builders that need one payment workflow reviewed before a wallet can sign.
Scope: One agent workflow, one target endpoint, and one spend policy.
Builders choosing a payment rail for one x402 endpoint before launch.
Scope: One public or proposed endpoint, one primary rail, and one fallback rail when relevant.
Teams letting an agent invoke paid tools or approve x402 spend.
Scope: One agent workflow and one payment policy.
Security, procurement, and platform teams evaluating multiple paid endpoints before agent spend.
Scope: Up to 10 public endpoints or one agent payment workflow; final scope is confirmed before invoicing.
x402 providers that need to separate observable settlements from supportable independent-demand claims.
Scope: Up to 500 public Base transaction hashes, one provider, one recipient set, and disclosed related-party addresses.
Boundary: Unattributed wallets are not counted as proven independent customers without additional evidence.
Directories, registries, and agent platforms that need implementation evidence before ranking or listing paid endpoints.
Scope: One public catalog or integration surface with up to 500 public service records during a qualified pilot.
Boundary: The feed supplies implementation evidence. It does not promise ranking, traffic, listing acceptance, safety, or revenue.
Service operators who want a clearly labeled discovery placement after their public endpoint is reviewed.
Scope: One public x402 service, one 30-day sponsored placement, and one copy/metadata review.
Boundary: Sponsored placement is separate from readiness scores, trust signals, strict ready filters, and machine-readable agent results.
Ontario will use the public endpoint or repository to decide whether the requested work has a defensible scope. Submitting this form does not create a charge or subscription.
Agents can probe these endpoints and inspect the HTTP 402 metadata before deciding whether to pay. The prices below do not imply an endpoint is safe or suitable for a task.
| Utility | Price | Purpose |
|---|---|---|
POST /api/verify/x402-readiness | $0 | Public readiness evidence and report ID. |
POST /api/x402/demand-authenticity-report | 0.02 USDC | Classify up to 20 Base USDC receipts without treating unknown wallets as proven customers. |
POST /api/x402/implementation-audit | 0.01 USDC | Task-specific payment, discovery, security, and launch findings. |
POST /api/x402/list-agent | 0.10 USDC | Register an agent card URL and reduce directory spam. |
POST /api/x402/list-service | 0.50 USDC | Publish a provider profile with a live readiness scan and public evidence; strict discovery remains ready-grade gated. |
