Ontario Protocol

Agents compare several surfaces before they spend. Your service origin should expose the x402 metadata appropriate to its implementation, while your MCP listing, OpenAPI, README, and payment challenge agree on purpose, method, price, asset, and network.

- Publish the service's x402 manifest and keep its price, asset, network, and resource current.
- For MCP, expose a stable HTTPS remote and a registry server.json with exact tool names and descriptions.
- Link the public readiness report instead of using a badge or launch claim as the only proof.

A registry listing is only an entry point. Agents need a short path from discovery to verification, policy, and a payment decision without guessing which URL or amount is authoritative.

- Put the verifier command and report link in the GitHub README beside the endpoint description.
- Use Ontario's agent buyer guide and payment policy as reference surfaces for preflight decisions.
- Do not promise registry placement, ranking, safety, or agent traffic; those outcomes are not controlled by metadata alone.

Run the free scorecard, readiness verifier, and payment-challenge checks before submitting to a catalog. Re-run them after any price, network, facilitator, or tool-schema change.

- Save the report ID and inspect warnings, freshness, integrity, and remediation text.
- Use a sandbox or testnet for rehearsal; never include private keys or seed phrases in a scan.
- If public evidence needs coordinated repair, request the fixed-scope $199 launch review after free qualification.

Use this as a starting point in a provider README. Replace the service URL, inspect the result, and keep the public report link current.

# 1. Publish and inspect your machine-readable surfaces curl -sS https://YOUR_SERVICE/.well-known/x402.json curl -sS https://ontarioprotocol.com/.well-known/agent-buyer.json # 2. Verify the endpoint before promotion curl -sS -X POST https://ontarioprotocol.com/api/verify/x402-readiness \ -H 'Content-Type: application/json' \ -d '{"target_url":"https://YOUR_SERVICE/api/paid"}' # 3. Put the resulting public report URL in your README and listing copy

Publish the endpoint's current manifest, OpenAPI, MCP metadata, and buyer-facing policy links.

Probe the endpoint without payment and confirm its HTTP 402 challenge is structured and intentional.

Run Ontario's free catalog scorecard and readiness verifier; keep the public report URL.

Copy the report link, verifier command, and exact endpoint facts into the README and registry draft.

Submit or promote only under the operator's own registry policy, then recheck freshness after changes.

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

Extentos is a multi-vendor development platform for adding smart-glasses capabilities to existing iOS and Android apps. The simplest analogy is Stripe for smart glasses

An MCP server tailored for React Native–first development using Gluestack UI

Create and read feature flags, review experiments, generate flag types, search docs, and interact with GrowthBook's feature flagging and experimentation platform.

Gives AI agents public URLs (tunnels) for localhost, live HTTP traffic inspection, snapshot publishing, and access control.

Understand, develop, and debug authorization policies in Oso Cloud.

Up-to-date documentation for your coding agent. Covers 1000s of public repos and sites. Built by ref.tools

Points agents to the canonical Agentry install docs for errors, product analytics, and deploy attribution.

Gives coding agents deterministic, read-only documentation handoffs with edit boundaries, ownership, and required checks before repository changes.

Deterministic JSON checks with signed evidence and x402-paid execution