AI applications using Agentcard can offer Gomry event tickets as part of a customer's conversation. An assistant can find suitable events, present the selected tickets and total, and submit the purchase after the customer confirms the cart.
Gomry supplies the event inventory and ticket information. Agentcard provides the purchase interface, including follow-up questions and payment approval where required. For teams building travel assistants, concierges or other consumer products, the integration connects an event recommendation to an actual purchase flow.
From a customer's plans to a ticket order
A customer asks for two concert tickets in New York on Friday evening. The application uses Agentcard's Purchase API to find options and resolve missing details. Before buying, it presents a specific selection and current total, not just a recommendation to visit a ticketing website.
The customer's confirmation applies to that cart. If the selection or price changes, the application must show the revised cart and obtain a new confirmation. Agentcard may also require a separate payment approval before proceeding.
The application then reads the returned purchase status and confirmation details before telling the customer that the order is complete. A recommendation, an approved payment and a completed merchant order are different steps.
What an application team integrates
Agentcard lists Gomry among the merchants supported by its Purchase API. Developers use the API's purchase loop to handle questions, present structured cart details and submit the confirmed selection. Compatible assistants can use the same flow through Agentcard's MCP tools.
Purchase calls use a user-scoped token, not an organization token. When payment runs through Agentcard's Vault, it uses the customer's stored card while keeping the real card number out of the agent's context. The application retains the conversation and presents the cart, required approvals and actual purchase result.
An application integrating directly with Gomry can find an event, retrieve its ticket offer and complete the purchase for the customer without a pre-approved integration or a manual Gomry login and checkout. A hosted payment page is an alternative when the application offers browser payment. These options are separate from the Agentcard Purchase API flow described above; they do not establish which Gomry access route Agentcard uses internally.
Gomry's organizer MCP is separate from these consumer purchase interfaces. It lets compatible assistants perform supported operations on an organizer's account, subject to that organizer's permissions; it is not the interface a customer uses to buy a catalog ticket.
What this means for event businesses
The integration adds a route to customers who are planning through an AI application. A concert can become an option in a weekend itinerary, and the customer can carry that choice into a ticket purchase.
The available events depend on the catalog and the connected application's coverage. This consumer purchase flow concerns Event tickets, not recurring Experience enrollment or the purchase of Bundle visits.
For product teams, the next step is the Agentcard Purchase API guide. Teams building directly on Gomry can use its catalog and checkout documentation instead.