Endpoint metadata
Draft locally first. Live verification happens after generation.
Free x402 developer tool
Give agents enough evidence to find your paid API.
Enter one endpoint. Get a validated Ontario listing payload, x402 resource draft, MCP descriptor, official MCP Registry server.json draft, GitHub readiness workflow, README snippet, and registry copy. No wallet, API key, or payment is required.
What this fixes
Agents skip vague tools. The generated artifacts make endpoint purpose, price, network, asset, owner, CI checks, and readiness actions explicit.
Generated artifacts
Generating a draft...
{}
Launch sequence
1. GenerateCreate explicit listing, x402, MCP, CI, README, and Registry drafts.
2. PublishExpose discovery metadata on the same origin as the paid endpoint.
3. VerifyRun the free readiness API and keep the public report URL.
4. Gate CIFail a release when the endpoint drops below the readiness threshold.
5. ListValidate for free, then submit only when metadata and policy are ready.
Free first, paid only when useful
Request the Agent Catalog Launch Pack
Send the endpoint and generated context. Ontario returns a free scope decision. If there is concrete work, the optional fixed-price MCP + x402 pack is $199.
The review covers observable readiness and discovery evidence. It does not publish to third-party registries, guarantee ranking or agent traffic, guarantee endpoint safety, or handle wallet custody.
Does this publish my endpoint?
No. It generates drafts and validates listing fields. You must publish, verify, and submit through each registry's current process.
Does this prove the endpoint is safe?
No. Operator metadata is not proof. Run a live readiness check and treat the report as evidence, not a guarantee of safety or future behavior.