Developers building AI assistants can use Gomry to find event tickets and Agentcard to pay on a user's behalf, within the limits that user sets. Gomry is Agentcard's ticket provider: it supplies the events, ticket options, and ordering infrastructure, while Agentcard provides the wallet.
For the person using the assistant, this supports a request that goes beyond recommendations: find tickets, show the options, and buy the chosen ones after approval. The developer connects those steps in their application.
Finding tickets in the Gomry catalog
The assistant can search Gomry for concerts, sports, tours, classes, and local events by location, date, artist, team, or venue.
Gomry returns ticket options and their identifiers. The application keeps the identifier of the user's selection so it can check that ticket again before ordering, without having to extract details from an event page.
Paying with the user's approval
Agentcard is a wallet for AI agents. A user can connect an existing card or issue a new one, set spending and merchant limits, and decide when approval is required. The underlying card details stay in Agentcard's secure vault instead of being exposed to the agent or the application running it.
How a ticket purchase can work
Consider one request:
“Find two Knicks tickets in New York next Friday, keep them under $200 each, and ask me before paying.”
The purchase can proceed as follows:
- Find matching tickets. The agent searches Gomry for Knicks games on the requested date and checks the ticket options against the budget.
- Let the user choose. It presents the options and keeps the identifiers for the selected tickets.
- Ask before paying. The application requests approval, with Agentcard enforcing the configured payment controls.
- Submit the purchase and check the result. The agent uses the order status returned by Gomry to tell the user whether the purchase succeeded.
This example describes an application flow, not a live ticket offer. Prices and availability can change while the user decides. The application must check the latest ticket options before submitting the purchase and wait for order confirmation before reporting success.
Building with Gomry and Agentcard
The application is responsible for carrying the user's choice from search to payment. Here is how the work is divided:
| Component | Role in the purchase |
|---|---|
| Gomry | Returns matching events, ticket options, and the identifiers used to place an order. Reports the order status after submission. |
| Agentcard | Stores the payment credentials and provides a way to pay within the user's configured limits and approval requirements. |
| Agent application | Keeps the user's selection, requests approval, submits the purchase, and communicates the result. |
Payment approval and order confirmation answer different questions. Approval establishes that the application may spend; Gomry's response establishes whether the purchase succeeded. If availability changes or the order fails, the application needs to explain the result and let the user decide what to do next.
To build this flow, start with Gomry's ticket commerce documentation and Agentcard's setup guide. Your application will need to handle ticket selection, approval, and unsuccessful orders as well as the completed purchase.