OnwardTicket.us for AI Agents

Full developer documentation now lives at /docs — API reference, MCP tool reference, recipes, and a live tool playground.

OnwardTicket.us exposes its booking surface to AI agents via the Model Context Protocol (MCP) and a public REST API. This page is the canonical setup target referenced by /.well-known/api-catalog and the Link: rel="service-doc" header on every public page.

Connect to your AI client

Claude Desktop

Add this MCP server to your claude_desktop_config.json:

{
  "mcpServers": {
    "onwardticket": {
      "url": "https://onwardticket.us/api/mcp"
    }
  }
}

Restart Claude Desktop. The six OnwardTicket tools (list_services, quote_order, place_order, lookup_order, search_blogs, get_blog_post) become available in any chat.

ChatGPT (Pro/Team/Enterprise)

ChatGPT supports MCP servers as Custom Connectors. In Settings → Connectors → Add custom connector, paste:

https://onwardticket.us/api/mcp/sse

Authentication: none. Tools appear automatically once the connector is enabled in your active conversation.

Custom Connector support requires an active ChatGPT Pro, Team, or Enterprise plan.

Cursor / VS Code

Add to your MCP-aware IDE config (e.g. ~/.cursor/mcp.json or Continue's config.json):

{
  "mcpServers": {
    "onwardticket": {
      "url": "https://onwardticket.us/api/mcp"
    }
  }
}

Reload the IDE. The OnwardTicket tools surface alongside your other configured MCP servers.

Don't see your client? Any MCP-compatible agent can connect over Streamable HTTP at https://onwardticket.us/api/mcp (POST only — a GET against it is not a stream and will 404), or over the legacy SSE transport at https://onwardticket.us/api/mcp/sse. The full server-card descriptor lives at /.well-known/mcp/server-card.json.

Discovery surfaces

/.well-known/api-catalog — RFC 9727 linkset
/.well-known/mcp/server-card.json — SEP-2127 server card
/.well-known/agent-skills/index.json — Cloudflare Agent Skills v0.2.0 index
/.well-known/oauth-protected-resource — RFC 9728 (stub: no resources require OAuth in v0)
/.well-known/oauth-authorization-server — RFC 8414 (stub)
/api/openapi.json — OpenAPI 3.1 hand-rolled v0

Tool catalogue

The MCP server exposes these tools:

Tool	Auth	Purpose
`list_services`	none	List service types + base prices + delivery SLAs
`quote_order`	none	Compute a price quote + Stripe Checkout link
`place_order`	email required	Create a pending order and return a Stripe Checkout URL the user can pay with
`lookup_order`	order# + email	Order status + delivery state + downloads
`search_blogs`	none	Search the help center / blog index (top 5 results)
`get_blog_post`	none	Fetch a blog post body as markdown for grounding

Rate limits

Per-IP: 60 requests / minute against /api/* (enforced — returns HTTP 429 on excess).
Per-MCP-connection: 30 tool calls / minute on /api/mcp/messages.
Authentication is available and optional: every tool works anonymously, and an OAuth client (open registration at /api/oauth/register) buys a stable identity and its own rate-limit bucket rather than extra capability. See auth.md.

Contact

Email [email protected]with the subject line “agent integration” for help connecting your agent.