Live x402 readiness evidence
Run the endpoint check, preserve the report ID, review HTTP 402 metadata, and identify the highest-impact blockers before payment or listing.
Make one x402 endpoint legible to agent catalogs.
The MCP + x402 Agent Catalog Launch Pack turns public endpoint, repository, and registry evidence into a concrete launch decision. Start with the free checks; pay only after Ontario confirms the work has a defensible scope.
$199 one-time qualified scopeNo checkout invoice only after agreementNo custody never send keys or seed phrasesNo guarantee evidence is point-in-time
A launch packet your team can inspect and publish
The work is limited to public, observable surfaces. It is designed for a provider who has an endpoint but is unsure whether agents, MCP hosts, and registries can understand it.
MCP Registry readiness
Review the server name, public remote or package metadata, tools/list behavior, and the fields the official registry workflow expects.
Discovery consistency
Compare the endpoint, OpenAPI, x402 manifest, MCP descriptor, README, and registry copy so agents do not receive contradictory price or network facts.
Copy-ready release artifacts
Return a launch checklist, README/registry wording, CI review notes, and concrete remediation examples. Publishing remains under your control.
Free evidence first, then a decision
Run public evidence
Use the scorecard, verifier, repository gate, and MCP Registry checker with URLs your team controls.
Receive go / fix-first / not-a-fit
Ontario confirms whether the public evidence supports the fixed scope. No invoice is created by the check.
Publish under your control
Apply the agreed changes, re-run the checks, and keep the resulting report ID with your registry submission.
Metadata opens the door; observed settlement creates evidence
Ontario listing, MCP Registry, and Coinbase Bazaar are separate surfaces. A launch packet can align the public endpoint, manifest, README, and registry copy, but it cannot claim a Bazaar placement. Coinbase documents cataloguing Bazaar-enabled routes after the CDP Facilitator observes a successful settlement.
- Run the free scorecard and correct the public price, network, accepts, manifest, and 402 response.
- Rehearse on a sandbox or testnet with no production spend.
- After the provider approves its own policy, make the smallest controlled production settlement and retain report, payment, and transaction evidence.
- Verify the external catalog response; placement and traffic remain unguaranteed.
Ontario does not take wallet custody, request private keys, execute purchases, or promise agent traffic. Read the official Bazaar documentation.
Why providers use it
Pay for fewer launch surprises, not for a ranking claim.
Catalogs and payment rails can expose an endpoint without making its purpose, price, network, response contract, or freshness easy for an agent to evaluate. This pack focuses on those observable integration gaps.
What is outside scope
- No registry acceptance or search ranking promise.
- No safety, fraud, revenue, uptime, or settlement guarantee.
- No private repository access, wallet custody, or production deployment.
- No automatic publishing to MCP, Bazaar, GitHub, or other directories.