AI ticketing
Your box office now speaks AI.
tickts has a built-in MCP server, so your AI assistant can read your live box office. Ask a question in plain English — get the answer from your real sales.
What the AI can see and do
Every tool is scoped to your own API key — the assistant only ever sees your organiser account, nothing else. Read tools work on Growth and up; the two write tools need Pro.
list_events · get_eventBrowse your events and drill into one — ticket types, capacity and sales.
list_orders · get_orderLook up orders and buyers — line items, totals, status.
sales_summaryA live revenue + tickets-sold summary, for the whole account or one event.
list_promos · validate_ticketCheck your discount codes and validate a ticket code.
refund_orderRefund an order — full or partial — on your say-so.
scan_ticketCheck a ticket in at the door, straight from the assistant.
Connect it in three steps
Point your AI at it
Add the tickts MCP endpoint to any MCP-compatible AI client, with your key.
Just ask
"How's my next event selling?" "Refund order 4821." It answers from live data.
One of the first ticketing platforms to speak MCP.
While others bolt on a chatbot, tickts gives your real box office to the AI you already use — safely, scoped to your account.
See the developer docsModel Context Protocol (MCP) is the open standard AI assistants use to connect to tools. Zero booking fees, always — the AI's just a bonus.
