Ontario Protocol

X402 Launch Kit

x402_launch_kit

Read-onlyIdempotent

Generate a validated listing payload, x402 resource draft, MCP descriptor, GitHub readiness workflow, README snippet, and registry copy for one paid endpoint.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes	Public name of the provider's service.
`tags`	No	Comma-separated public capability tags, for example x402,paid-api,agent-tool.
`asset`	No	USDC token contract on the declared payment network; omit to use the Base USDC default.
`method`	No	HTTP method accepted by the provider endpoint, for example POST.	POST
`network`	No	Payment network accepted by the provider, for example base or eip155:8453.	base
`endpoint`	Yes	Provider-owned public HTTPS x402 endpoint to prepare for listing.
`owner_url`	No	Public website identifying the service provider.
`price_usdc`	Yes	The provider's per-call price in decimal USDC, not Ontario's publication fee. Kit generation is free.
`description`	Yes	Public description of the task the service performs and the result it returns.
`owner_contact`	No	Optional public business contact for generated drafts. Omit private addresses; never supply credentials.

Output Schema

TableJSON Schema

Name	Required	Description
`schema`	Yes
`status`	Yes
`artifacts`	Yes	Unpublished drafts, not proof of endpoint readiness or catalog placement.
`next_steps`	Yes
`generated_at`	Yes
`ontario_calls`	Yes
`trust_boundary`	Yes
`listing_validation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "artifacts": {
+      "description": "Unpublished drafts, not proof of endpoint readiness or catalog placement.",
+      "properties": {
+        "github_workflow": {
+          "type": "string"
+        },
+        "mcp_registry_publisher_commands": {
+          "type": "string"
+        },
+        "mcp_registry_server_json": {
+          "type": "object"
+        },
+        "mcp_tool_descriptor_draft": {
+          "type": "object"
+        },
+        "ontario_listing_payload": {
+          "type": "object"
+        },
+        "readme_markdown": {
+          "type": "string"
+        },
+        "registry_listing_draft": {
+          "type": "object"
+        },
+        "x402_resource_draft": {
+          "type": "object"
+        }
+      },
+      "required": [
+        "ontario_listing_payload",
+        "x402_resource_draft",
+        "mcp_tool_descriptor_draft",
+        "github_workflow",
+        "readme_markdown",
+        "registry_listing_draft",
+        "mcp_registry_server_json",
+        "mcp_registry_publisher_commands"
+      ],
+      "type": "object"
+    },
+    "generated_at": {
+      "format": "date-time",
+      "type": "string"
+    },
+    "listing_validation": {
+      "properties": {
+        "errors": {
+          "items": {
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "normalized": {
+          "type": "object"
+        },
+        "ok": {
+          "type": "boolean"
+        },
+        "warnings": {
+          "items": {
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "ok",
+        "errors",
+        "warnings",
+        "normalized"
+      ],
+      "type": "object"
+    },
+    "next_steps": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "ontario_calls": {
+      "required": [
+        "verify_readiness",
+        "validate_listing",
+        "submit_listing"
+      ],
+      "type": "object"
+    },
+    "schema": {
+      "const": "ontario.x402_launch_kit.v1"
+    },
+    "status": {
+      "enum": [
+        "ready_to_verify",
+        "needs_fixes"
+      ]
+    },
+    "trust_boundary": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "schema",
+    "generated_at",
+    "status",
+    "listing_validation",
+    "artifacts",
+    "ontario_calls",
+    "next_steps",
+    "trust_boundary"
+  ],
+  "type": "object"
+}

First observedSep 5, 2026

TDQS

A3.8/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false. The description adds meaningful context by specifying that the output is 'validated' and scoped to 'one paid endpoint,' and its 'Generate' wording is consistent with a non-destructive, read-only drafting operation. No contradiction exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence that front-loads the action and then lists the specific outputs. Every word earns its place, and the scope constraint 'for one paid endpoint' adds precision without padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the rich input schema, output schema, and safety-revealing annotations, the description is largely complete: it names all artifact types and the scope. The only notable gap is the lack of relationship to sibling tools and workflow timing, which is partially captured under usage guidelines.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the input schema already documents all ten parameters thoroughly. The description adds no additional parameter-level semantics beyond framing the tool as producing artifacts for one paid endpoint, which is appropriate given the schema already carries the burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description begins with a specific verb, 'Generate,' and enumerates six concrete deliverables (listing payload, x402 resource draft, MCP descriptor, GitHub readiness workflow, README snippet, registry copy) for a paid endpoint. This makes the tool's purpose immediately distinguishable from generic or sibling operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives such as ontario_list-service, ontario_validate-service, or x402_readiness_verify. It states what is generated but not the intended workflow position, prerequisites, or situations where another sibling would be more appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Ontario Protocol tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.