--- title: "What AI Agents Can Do on Ticket Fairy | ACP, UCP, MPP, x402 and MCP" description: "Find events, buy tickets over ACP, UCP, MPP or x402, help ticket buyers and run events for organizers. Every capability your AI agent can use, with links to the developer docs." canonical: "https://www.ticketfairy.com/agents" --- For AI agents and their developers # What AI agents can do on Ticket Fairy Your agent can find events, buy tickets with the buyer's approval, help buyers with their orders and run events for organizers. Each capability below names the protocol your agent uses and links to the developer documentation that shows how. [Read the developer documentation](https://www.ticketfairy.com/developers) [Get this list as JSON](https://www.ticketfairy.com/agents.json) - ACP - UCP - AP2 - Stripe Shared Payment Tokens - MPP - x402 - MCP - Agent2Agent - NLWeb - WebMCP ## Find events and answers Your agent can search live events, answer questions about Ticket Fairy and read every page, with no account or key. ### Find events Status: Live Search live public events by words, place and date, read one event from its link, or ask a question in plain language. Each result links to its event page, and clients that support MCP Apps show the results as event cards. - **Protocols:** MCP, Agent2Agent with A2UI, NLWeb, Event API (OpenAPI 3.1), WebMCP - **Events MCP server:** `https://www.ticketfairy.com/agentic/mcp` - **Agent2Agent endpoint:** `https://www.ticketfairy.com/agentic/a2a` - **NLWeb ask endpoint:** `https://www.ticketfairy.com/ask` - **Event API:** `https://www.ticketfairy.com/api/v1/events/listing` - **Tools:** `search_events`, `get_event`, `ask_events`, `search_events (WebMCP)` - **Credential:** None - [Events MCP server](https://www.ticketfairy.com/developers/ai-agents#mcp) - [Agent2Agent](https://www.ticketfairy.com/developers/ai-agents#a2a) - [NLWeb](https://www.ticketfairy.com/developers#nlweb) - [Event API](https://www.ticketfairy.com/developers#public-api) ### Answer questions about Ticket Fairy Status: Live Search the how-to guides and read any guide as plain text, to answer how to do something on Ticket Fairy. Ready-made agent skills teach your agent jobs such as finding tickets or managing orders. - **Protocols:** MCP, Agent Skills - **Guides MCP server:** `https://www.ticketfairy.com/docs/mcp` - **Agent skills index:** `https://www.ticketfairy.com/.well-known/agent-skills/index.json` - **Tools:** `search_guides`, `get_guide` - **Credential:** None - [Guides MCP server](https://www.ticketfairy.com/developers/ai-agents#mcp) - [Agent skills](https://www.ticketfairy.com/developers/ai-agents#skills) ### Read every page as Markdown Status: Live Add .md to any page address, or send Accept: text/markdown, to get the page as Markdown for far fewer tokens than the HTML. Known AI crawlers and assistants get Markdown without asking, and one catalog lists every agent resource. - **Protocols:** Markdown content negotiation, llms.txt, Agentic Resource Discovery, API catalog (RFC 9727) - **This page as Markdown:** `https://www.ticketfairy.com/agents.md` - **llms.txt:** `https://www.ticketfairy.com/llms.txt` - **AI catalog:** `https://www.ticketfairy.com/.well-known/ai-catalog.json` - **Credential:** None - [Markdown pages](https://www.ticketfairy.com/developers/ai-agents#markdown) - [Discovery files](https://www.ticketfairy.com/developers/ai-agents#documents) ## Buy tickets for a person Your agent can hold tickets, pay with the buyer's approval and follow the order afterwards, through the protocol it already speaks. ### Buy tickets with ACP Status: Live Hold tickets, change the order and complete the purchase over the Agentic Commerce Protocol. Your agent registers itself for a buyer key and can start selling at once. - **Protocols:** Agentic Commerce Protocol (ACP) - **ACP checkout API:** `https://www.ticketfairy.com/api/v1/agentic/acp` - **Buyer key registration:** `https://www.ticketfairy.com/api/v1/agentic/agents/register` - **Credential:** A buyer key your agent registers for - [Register your agent](https://www.ticketfairy.com/developers/agent-checkout#register) - [Checkout endpoints](https://www.ticketfairy.com/developers/agent-checkout#endpoints) - [Agentic Commerce Protocol specification](https://www.agenticcommerce.dev) ### Buy tickets with UCP Status: Live Search the catalog, hold tickets, complete the purchase and read the order over the Universal Commerce Protocol, by REST or Agent2Agent. Your agent signs each request with a key from its own UCP profile. - **Protocols:** Universal Commerce Protocol (UCP) - **UCP shopping API:** `https://www.ticketfairy.com/api/v1/agentic/ucp` - **UCP Agent2Agent card:** `https://www.ticketfairy.com/.well-known/ucp-agent-card.json` - **Credential:** Requests signed with a key your agent's UCP profile publishes - [Sign requests with your profile](https://www.ticketfairy.com/developers/agent-checkout#register) - [Checkout endpoints](https://www.ticketfairy.com/developers/agent-checkout#endpoints) - [Universal Commerce Protocol specification](https://ucp.dev) ### Pay with Stripe Shared Payment Tokens Status: Live Pay inside your agent with a Stripe Shared Payment Token the buyer approved, for example from their Link wallet. It covers cards, including Mastercard Agent Pay and Visa Intelligent Commerce, Link, and Affirm or Klarna where the event offers them. - **Protocols:** Stripe Shared Payment Tokens, ACP, UCP - **Credential:** A Stripe Shared Payment Token for the checkout - [Payment inside your agent](https://www.ticketfairy.com/developers/agent-checkout#payment) ### Pay with an AP2 mandate Status: Live Complete a UCP purchase with an Agent Payments Protocol mandate the buyer signed. Ticket Fairy checks the mandate before it charges. - **Protocols:** Agent Payments Protocol (AP2), UCP - **UCP shopping API:** `https://www.ticketfairy.com/api/v1/agentic/ucp` - **Credential:** A mandate the buyer signed - [Purchases the buyer approved](https://www.ticketfairy.com/developers/agent-checkout#payment) ### Pay with the Machine Payments Protocol Status: Live Complete an ACP checkout over HTTP 402. Ticket Fairy answers with a payment challenge for the exact total, and your agent sends the same request again with a Stripe Shared Payment Token. - **Protocols:** Machine Payments Protocol (MPP), HTTP 402, Stripe Shared Payment Tokens - **MPP payment:** `https://www.ticketfairy.com/api/v1/agentic/mpp/checkout_sessions/{checkout_id}/complete` - **Credential:** Your buyer key and a Stripe Shared Payment Token - [Payment inside your agent](https://www.ticketfairy.com/developers/agent-checkout#payment) - [Machine Payments Protocol specification](https://mpp.dev) ### Pay in USDC with x402 Status: Live Complete an ACP checkout priced in US dollars by paying USDC on Base over x402. Ticket Fairy answers with the exact amount, and your agent's wallet signs one payment for it. - **Protocols:** x402, HTTP 402, USDC on Base - **x402 payment:** `https://www.ticketfairy.com/api/v1/agentic/x402/checkout_sessions/{checkout_id}/complete` - **Credential:** Your buyer key and a wallet with USDC on Base - [Payment inside your agent](https://www.ticketfairy.com/developers/agent-checkout#payment) - [x402 specification](https://www.x402.org) ### Hand the buyer to the checkout page Status: Live Send the buyer to finish in their browser when they want to pay another way or choose seats on the seat map, with their tickets still held. On the checkout page, browser agents can read and fill in the form with WebMCP tools, and the buyer still pays themselves. - **Protocols:** ACP and UCP continue\_url, WebMCP - **Tools:** `read_ticket_checkout (WebMCP)`, `enter_ticket_checkout_field (WebMCP)`, `activate_ticket_checkout_action (WebMCP)` - **Credential:** None - [Payment in the browser](https://www.ticketfairy.com/developers/agent-checkout#payment) - [WebMCP in the browser](https://www.ticketfairy.com/developers/ai-agents#webmcp) ### Follow every order Status: Live Read the current state of an order your agent sold, get a signed webhook each time it changes, and ask for a refund the buyer approves. - **Protocols:** Signed order webhooks, UCP Get Order, ACP order reconciliation - **UCP order:** `https://www.ticketfairy.com/api/v1/agentic/ucp/orders/{id}` - **ACP order:** `https://www.ticketfairy.com/api/v1/agentic/acp/orders/{id}` - **Credential:** The buyer key or UCP profile that sold the order - [After the purchase](https://www.ticketfairy.com/developers/agent-checkout#after-purchase) ## Help ticket buyers With the buyer's approval, your agent can read their orders and tickets and talk to Ticket Fairy's assistant for them. ### Help a buyer with their own tickets Status: Live Read a buyer's orders and tickets, and talk to Ticket Fairy's assistant for them, with a person from the support team when they ask. The buyer approves your agent in their browser and can disconnect it at any time. - **Protocols:** Personal Agent Protocol (Poppy), OAuth 2.0 with DPoP - **Personal agent addresses:** `https://www.ticketfairy.com/.well-known/poppy.json` - **Buyer account API:** `https://www.ticketfairy.com/api/v1/poppy/account` - **Conversations:** `https://www.ticketfairy.com/api/v1/poppy/conversations` - **Credential:** Read access the buyer approves - [A ticket buyer's own assistant](https://www.ticketfairy.com/developers/ai-agents#personal-agents) ## Work for event organizers Your agent can read an organizer's sales and set up their events with the tools of the Ticket Fairy CLI, as their team role allows, and can sign up new organizers. ### Run events for an organizer Status: Live Read sales, orders, customers, check-in and the team, and create or change events, ticket types, add-ons and promotions, with the tools of the Ticket Fairy CLI. Your agent acts as the person who signed in and can do only what their team role allows. - **Protocols:** MCP, Ticket Fairy API (OpenAPI 3.1), Ticket Fairy CLI, OAuth 2.0 with PKCE - **Event organizer MCP server:** `https://www.theticketfairy.com/agentic/organizer/mcp` - **Ticket Fairy API:** `https://www.theticketfairy.com/api/openapi.json` - **Ticket Fairy CLI:** `npm install -g ticketfairy` - **Credential:** A sign-in or token the organizer approves - [Authentication](https://www.ticketfairy.com/developers/authentication) - [Ticket Fairy API](https://www.ticketfairy.com/developers/organiser-api) - [MCP server for your account](https://www.ticketfairy.com/mcp-server) - [Ticket Fairy CLI](https://www.ticketfairy.com/cli) ### Sign up a new organizer Status: Live Start a Ticket Fairy account for a new organizer from your platform, or build a draft event and hand it over. The organizer signs in, accepts the terms and enters their payout details themselves. - **Protocols:** Ticket Fairy API, Stripe Projects - **Organizer onboarding:** `https://www.theticketfairy.com/api/agent/organizer/v1/onboardings` - **Guest event drafts:** `https://www.theticketfairy.com/api/guest-event-drafts` - **Credential:** An application credential for onboarding; none for a draft - [Sign up new organizers](https://www.ticketfairy.com/developers/organiser-api#onboarding) - [Hand a draft event to an organizer](https://www.ticketfairy.com/developers/organiser-api#draft-handoff) ## Connect reliably Your agent can see its limits before it reaches them, try the API without live events and prove who it is. ### Stay within the limits Status: Live Read the RateLimit headers to slow down before you reach a limit, send an Idempotency-Key so a retry never repeats a change, and try the API in the sandbox without touching live events. - **Protocols:** RateLimit headers, Idempotency-Key, API versioning policy - **Sandbox:** `https://www.ticketfairy.com/sandbox` - **Versioning policy:** `https://www.ticketfairy.com/api/v1/versioning.md` - **Credential:** None - [Rate limits and errors](https://www.ticketfairy.com/developers#public-api) - [Sandbox](https://www.ticketfairy.com/developers#sandbox) ### Prove who your agent is Status: Live Sign your agent's requests with Web Bot Auth, so Ticket Fairy knows which agent sent them, and check the signature on the requests Ticket Fairy sends you. - **Protocols:** Web Bot Auth (HTTP Message Signatures) - **Ticket Fairy's signing keys:** `https://www.ticketfairy.com/.well-known/http-message-signatures-directory` - **Credential:** Your agent's own signing key - [Signed requests](https://www.ticketfairy.com/developers/ai-agents#signed-requests) ## Questions about AI agents on Ticket Fairy ### Where do I find the setup steps and code? In the developer documentation. Each capability on this page links to the section that shows its addresses, credentials and example requests. ### Does my agent need approval from Ticket Fairy? No. Event search, the guides and Markdown pages need no account or key. A shopping agent registers itself for a buyer key, or signs with its own UCP profile, and can start selling at once. To act for an organizer or a ticket buyer, your agent needs the access that person approves. ### When does my agent get order webhooks and refund requests? Your agent can read an order it sold from the start. Ticket Fairy sends order webhooks to an address our team sets up with your agent platform, so contact us to add yours. Refund requests are switched on for each agent platform on request, and an ACP agent also needs refund access added to its credential. Each refund follows the event's refund rules and needs the buyer's approval. ### Which payment methods can a buyer use inside my agent? Over ACP and UCP, a Stripe Shared Payment Token covers cards, Link, and Affirm or Klarna where the event offers them, and a UCP agent can also pay with an AP2 mandate the buyer signed. Over MPP, a shared payment token covers cards and Link. Over x402, your agent pays in USDC on Base. For any other method, the buyer pays on the checkout page, with the same tickets still held. ### Which events can my agent pay for with MPP or x402? Events whose ticket payments Ticket Fairy takes directly. When an event takes payments into the organizer's own payment account, your agent pays with ACP or UCP and a shared payment token, or hands the buyer to the checkout page. x402 also needs a price in US dollars. ### Will my agent get better access than the event page? No. Your agent sees the same tickets, prices and fees as a person on the event page, and the event's limits for each order apply. No agent gets priority, extra holds or lower fees. ### Can an organizer stop agents selling their tickets? Yes. Agent sales are on for every brand by default. A brand owner or admin can turn them off for the whole brand, or pause them for one event, in the dashboard or by asking Fai, Ticket Fairy's AI teammate. Ticket Fairy then refuses a new checkout for that brand or event. ### What does the hosted organizer MCP server leave to the organizer? Refunds, cancellations, deletions, publishing, team changes, messages to buyers and other changes that cannot be undone. The organizer does them in the Ticket Fairy dashboard. For every other change, your agent sends confirm: true with the tool call. ### What happens when my agent goes over a limit? It gets 429 with a Retry-After header. Wait that many seconds, then send the request again. ### Is there a machine-readable version of this page? Yes. /agents.json lists every capability with its protocols, addresses, credential, status and documentation, and /agents.md is this page in Markdown. --- This page is on Ticket Fairy, a ticketing, marketing and operations platform for live events and the venues that host them: festivals, club nights, concerts, conferences and tours, and night clubs, beach clubs and concert venues. It grows revenue with fan rewards that turn an audience into a sales channel, and runs the money side with payments and payouts, Vault business banking, and working capital advanced against ticket sales. [How Ticket Fairy ticketing works](https://www.ticketfairy.com/event-ticketing) ยท [Ticket Fairy for AI assistants](https://www.ticketfairy.com/llms.txt)