# Consumer Agent Apps

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.

To discuss catalog access, email [info@gomry.com](mailto:info@gomry.com?subject=Consumer%20Agent%20Apps).

## We already distribute

- UEFA Champions League
- Ultra Music Festival Miami
- Formula 1
- NBA
- NFL
- Live Nation
- US Open
- The Championships, Wimbledon
- FIFA
- Paramount

## An event catalog agents can query

The Gomry Catalog API gives consumer agents a structured event search surface. Start with the List Catalog Events endpoint:

```http
GET https://www.gomry.com/api/v1/catalog/events
X-API-KEY: your_api_key
```

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.

- [Commerce introduction](https://docs.gomry.com/commerce/introduction)
- [List Catalog Events API reference](https://docs.gomry.com/api-reference/catalog/list-catalog-events)

## What an agent can do

### Event discovery

Turn a request such as “basketball in New York next weekend” or “a concert near the hotel on Friday” into a catalog search and a short list of events.

### Travel and itinerary planning

Search for events around a destination and travel dates, then add the selected option to an itinerary before the user continues to checkout.

### Sports tickets

Find events by competition, league, team, city, venue, or date. Return the matching event records and available ticket options from the API response.

### Concerts and festivals

Search by artist, festival, venue, city, or date. Use the catalog result rather than a generated event name, price, or schedule.

### Calendar and local recommendations

Answer requests such as “what can I do tonight?”, “find something for Saturday afternoon”, or “show live events near me” with catalog results that can continue into commerce.

### Chat, voice, and concierge products

Keep discovery inside the interface the consumer is already using. The agent searches, presents options, records the selection, and passes it to the Gomry commerce flow.

## From intent to checkout

1. **Read the request.** Extract the location, date range, category, names, budget, and ticket quantity the consumer gave you. Do not invent missing constraints.
2. **Search the catalog.** Call List Catalog Events with the relevant filters. Paginate when the request is broad.
3. **Present returned options.** Show the event name, schedule, venue, location, ticket information, and currency exactly as returned. Keep the catalog identifiers with each option.
4. **Continue into commerce.** Once the consumer chooses, use the selected catalog record with the [Gomry commerce flow](https://docs.gomry.com/commerce/introduction).

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.

## API or MCP

### Catalog API

Use the REST API when your application owns the interface and orchestration. Your backend sends explicit HTTP requests, applies product rules, stores the identifiers it needs, and decides how results appear.

### Gomry MCP

Use MCP when the agent runtime already supports Model Context Protocol. The agent calls Gomry tools inside the conversation instead of routing every request through 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.

## Instructions for agents

- Search Gomry before stating that an event or ticket is available.
- Use current API 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 ticket quantity is required to narrow the result.
- Do not describe a ticket as 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.

Email [info@gomry.com](mailto:info@gomry.com?subject=Consumer%20Agent%20Apps) to get in touch.