Event discovery
Turn “basketball in New York next weekend” or “a concert near the hotel on Friday” into a catalog search and a short list of events.
100,000+ events. Ready for your agent.
A consumer asks for an event. Your agent searches Gomry's catalog, returns current ticket options, and carries the selected event into commerce. Use the Catalog API from your backend or Gomry MCP from an MCP client.
We already distribute:
Event catalog.
One endpoint.
The Gomry Catalog API gives consumer agents a structured event search surface. Start with List Catalog Events.
GET
https://www.gomry.com/api/v1/catalog/events
Use the documented search, location, date, and pagination parameters to narrow the catalog. Authenticate server-side with a Gomry API key. Keep the event identifiers returned by the API: they connect discovery to the next commerce call.
Use cases
What an agent can do.
Travel planning
Search around a destination and travel dates, then add the selected event to an itinerary before the user continues to checkout.
Sports tickets
Find events by competition, league, team, city, venue, or date. Return event records and ticket options from the API response.
Concerts and festivals
Search by artist, festival, venue, city, or date. Use the catalog result instead of generating an event name, price, or schedule.
Local recommendations
Answer “what can I do tonight?” or “show live events near me” with catalog results that can continue into commerce.
Chat and voice
Keep discovery inside the interface the consumer is using. Search, present options, record the selection, and pass it to commerce.
Request to checkout
Four steps. Keep the data with the choice.
-
01
Read the request
Extract the location, date range, category, names, budget, and ticket quantity the consumer gave you. Do not invent missing constraints.
-
02
Search the catalog
Call List Catalog Events with the relevant filters. Paginate when the request is broad.
-
03
Present returned options
Show the event name, schedule, venue, location, ticket information, and currency as returned. Keep the catalog identifiers with each option.
-
04
Continue into commerce
Once the consumer chooses, use the selected catalog record with the Gomry commerce flow .
Search again when the consumer changes the city, date, event, or ticket requirement. Availability and prices can change between turns. A search result is not a completed order; only the commerce response confirms the next state.
Integration
Catalog API or MCP.
REST
Catalog API
Use the API when your application owns the interface and orchestration. Your backend sends HTTP requests, applies product rules, stores identifiers, and decides how results appear.
MCP
Gomry MCP
Use MCP when the agent runtime already supports Model Context Protocol. The agent calls Gomry tools inside the conversation instead of using a custom tool wrapper.
Both routes let an agent work from Gomry data. The API is the direct integration surface for an application; MCP is the tool surface for an MCP-compatible agent.
For agents
Use the catalog as the source.
- Search Gomry before stating that an event or ticket is available.
- Use current responses for names, dates, venues, prices, currency, and availability.
- Preserve event and catalog identifiers between discovery and commerce calls.
- Paginate broad searches instead of treating the first page as the whole catalog.
- Ask one short follow-up when location, date, or quantity is needed to narrow the result.
- Do not call a ticket reserved, purchased, or confirmed until the commerce response says so.
Connect your agent to Gomry.
Tell us whether you are building event discovery, ticket search, travel planning, a recommendation product, a voice assistant, or another consumer agent. We will follow up about Catalog API, MCP, and commerce access.