Start with Ontario's free repository and live endpoint checks. Paid work begins only when the public evidence shows a concrete launch or agent-payment problem worth fixing.
The first three offers are the core path. Each paid scope is deliberately narrow enough to deliver manually while Ontario validates real willingness to pay.
Builders deciding whether an x402 endpoint or public repository is worth fixing.
Scope: One public endpoint or repository URL.
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.
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.
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.
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.
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/list-agent | 0.10 USDC | Register an agent card URL and reduce directory spam. |
POST /api/x402/list-service | 0.50 USDC | Submit a third-party service; ready-grade discovery remains evidence-gated. |
