Encuentra tus entradasIniciar sesión
Crear mi evento gratis

Pandy Tickets for developers

Ticketing
your agent
can use.

A public MCP server and REST API for events in Guatemala. Agents find events, quote prices in quetzales, hand people the checkout link and prepare new events for organizers. No API key.

Connect an MCP clientOpenAPI spec

MCP · tickets.pandy.cloud

“Find medical congresses in Guatemala this November.”

search-events { q: "congreso", from: "2026-11-01", to: "2026-11-30" }

get-checkout-link { slug, ticket_type_id, quantity: 2 }

Here is the link to buy 2 tickets. You pay on Pandy Tickets; I never charge you.

Streamable HTTP · JSON-RPC 2.0

Connect in
one line.

https://tickets.pandy.cloud/mcp
Claude Code
claude mcp add --transport http pandy-tickets https://tickets.pandy.cloud/mcp
Cursor, Windsurf and other clients
{
  "mcpServers": {
    "pandy-tickets": {
      "type": "http",
      "url": "https://tickets.pandy.cloud/mcp"
    }
  }
}
  1. Claude.Settings › Connectors › Add custom connector, then paste the URL.
  2. ChatGPT.Settings › Apps & Connectors with developer mode on, then add the URL. Menu names change by plan.

Tools

  • search-eventsFind upcoming published events by text, date range or way in (free, transfer, card).
  • get-eventOne event: ticket types, prices in GTQ, availability and registration questions.
  • get-checkout-linkThe link where the person buys or registers. Checks availability; never reserves or charges.
  • draft-eventPrepare an event from the conversation and return a one-time link the organizer opens to claim it as a draft.
Results are structured JSON. Errors come back as tool errors with a Spanish message to relay. An unclaimed draft is deleted after 48 hours.

REST API

Same data,
plain HTTP.

Read only, no auth, CORS open and cached for a minute. The OpenAPI 3.1 spec is the contract.

GET /api/v1/events
Upcoming published events, soonest first, 20 per page. Filters: q, from, to (YYYY-MM-DD, Guatemala time), entry (free, transfer, card), page.
GET /api/v1/events/{slug}
One event: ticket types with prices and sold-out state, registration questions, how to get in and a checkout_url per card ticket type.
GET /api/v1/openapi.json
The full contract. Generate a client from it.
Try it
curl "https://tickets.pandy.cloud/api/v1/events?q=congreso&from=2026-11-01"

The rules

What an agent does.
And what it doesn’t.

Can

  • Search upcoming public events and read prices in GTQ.
  • Hand the person the page to buy or register.
  • Prepare an event as a draft the organizer claims.

Can’t

  • Pay, charge or reserve tickets.
  • Register a person on their behalf.
  • See private events, attendees, sales or account data.

FAQ

Before you
build.

Organizing an event?

The Spanish guide shows organizers how to create an event by chatting.

Pandy Tickets con IA llms.txt
Do I need an API key?

No. The MCP server and the REST API are public and read only published events. The one write, draft-event, stores an unowned draft that nothing shows until the organizer claims it.

Can an agent buy tickets or register someone?

No. Agents find events, show prices and availability, and hand the person a link. The person always pays or registers themselves on Pandy Tickets.

Can an agent create an event?

It can prepare one. draft-event returns a one-time claim link valid for 48 hours. The organizer opens it, signs in with Google and gets the event as a draft to review and publish.

Which events are listed?

Upcoming published public events on Pandy Tickets, mostly in Guatemala. Private events are never returned. Prices are in quetzales (GTQ) and times in Guatemala time.

Are there rate limits?

Yes, per IP: 60 requests a minute on the REST API and a higher limit on the MCP server. Assistant platforms call from shared addresses, so the limits guard against floods, not normal use.

Building on
Pandy Tickets?
Tell us.

Questions, limits or an integration idea: write to tickets@pandy.cloud.

Email the team