# Gomry > Gomry is where people find things to do and get in: concerts, parties, > festivals, sports, classes, workshops and other live events and experiences. > Browse what's on nearby, register for free events, buy tickets, and keep > every ticket and order in one wallet. Running events or selling tickets? Everything for organizers and businesses (features, fees, the organization API and MCP server) is at https://business.gomry.com/llms.txt. This file covers the attendee side only. ## What a person can do on Gomry - Discover public events and recurring experiences near them, or anywhere, by city, date or free-text search. - Register for free events and buy tickets for paid ones. Prices are shown in the visitor's local currency by default, and any fees are shown before paying. - Pay with 100+ methods, including major cards, Apple Pay, Google Pay and local methods. Payments run through Stripe. - Keep tickets in the Wallet (profile menu, then Wallet): upcoming, past and passes, each with its QR code. Tickets can also be saved to Apple Wallet. - Find every order and its receipt under Orders (`https://www.gomry.com/personalSettings?tab=orders`), and cancel an order or ask for a refund there, under the refund policy the organizer set for that event. - Ask Aven, Gomry's assistant, about their tickets, an event's time and venue, or what's on, from the website or app chat, by WhatsApp or SMS, or by email at aven@gomry-mail.com. ## Finding events - [Browse events](https://www.gomry.com/home): the public event feed - [Search events](https://www.gomry.com/home/search?q=): free-text event search (`q` is the query) - Natural-language query endpoint (NLWeb): `POST https://www.gomry.com/ask`. Send `{"query": "..."}` and get schema.org `Event` items back. Supports SSE streaming with `Prefer: streaming=true`. No credential needed. - Event catalog API: `GET https://www.gomry.com/api/v1/catalog/events` (search by `q`, filter by `starts_after`, `starts_before`, `city`), and one event with its ticket types at `GET https://www.gomry.com/api/v1/catalog/events/{eventId}`. - Structured data feeds (schema map): https://www.gomry.com/schemamap.xml ## Buying a ticket for a person (agents) **To find a ticket and hand a person a page to pay on, you need no credential at all.** `GET https://www.gomry.com/api/v1/catalog/events`, then `POST https://www.gomry.com/api/v1/checkout_sessions` with no `Authorization` header, and send the person the response's `continue_url`. Nobody signs in to Gomry. **To pay yourself, get a credential, also without a human or a dashboard.** Register with `POST https://www.gomry.com/api/mcp/oauth/register` and the body `{"client_name": "", "grant_types": ["client_credentials"]}`, then exchange the `client_id` and `client_secret` for a 15-minute access token at `POST https://www.gomry.com/api/mcp/oauth/token` (`grant_type=client_credentials`, form-encoded). Send it as `Authorization: Bearer `. It reads the event catalog and buys tickets (`/api/v1/checkout_sessions`). Steps: https://www.gomry.com/auth.md **Buying a ticket for a person: two ways, pick by what you can do.** - **You can pay with a Stripe Shared Payment Token** (an agent payment provider, a Link wallet): buy it yourself, end to end, through `/api/v1/checkout_sessions`. Steps: https://www.gomry.com/auth.md#payment - **You can't:** create the same checkout session (with or without a credential) and send the buyer its `continue_url`. They pay by card, Apple Pay or Google Pay with no Gomry account, and the tickets are issued when they do. Each ticket type's `checkout_url` in `GET https://www.gomry.com/api/v1/catalog/events/{eventId}` opens Gomry checkout instead (the buyer signs in there). **Can't hold a client secret?** If the person can sign in, run OAuth 2.1 (authorization code + PKCE) and ask for `checkout:write`. Their access token buys for them on `/api/v1/checkout_sessions`. Steps: https://www.gomry.com/auth.md - Agentic checkout (ACP): Gomry implements the Agentic Commerce Protocol. Endpoint: `POST https://www.gomry.com/api/v1/checkout_sessions` (it lives under `/api/v1`, NOT at the domain root). Update, complete and cancel are `/api/v1/checkout_sessions/{id}`, `.../complete` and `.../cancel`. Headers: `API-Version` is validated (this deployment implements `2025-09-12`) and `Idempotency-Key` is honoured on writes with a 24h replay window. Auth: none to quote and get `continue_url`; the credential above to `complete` with a payment token. No request signature is needed: omit the `Signature` header entirely unless you have been issued a signing secret, because a signature we cannot verify is rejected rather than ignored. Card data is never accepted; payment arrives as a delegated token (`payment_data.token`, `provider: "stripe"`). - Personal Agent Protocol (Poppy): https://www.gomry.com/.well-known/poppy.json. A personal agent acting for one person browses the catalog and buys tickets (ACP checkout) with a DPoP Session Token, as a guest or, after Direct Sign-In with `poppy:write`, on the person's own Gomry account. Signed in, it also reads the person's tickets and orders (`/api/v1/me`, `poppy:read`), transfers a ticket (`poppy:write`), and talks with Aven (the `agent` conversation endpoint). - Getting a credential: https://www.gomry.com/auth.md - Agent capabilities: https://www.gomry.com/agents.md - OpenAPI document (catalog and checkout included): https://www.gomry.com/openapi.json - Commerce profile (UCP): https://www.gomry.com/.well-known/ucp - Service catalog: https://www.gomry.com/.well-known/api-catalog - Agent card: https://www.gomry.com/.well-known/agent-card.json - Resource catalog (ARD): https://www.gomry.com/.well-known/ard.json - [Commerce docs](https://docs.gomry.com/commerce/introduction): the catalog and checkout reference ## Help and contact - [Contact](https://www.gomry.com/contact): support for tickets and orders - [Privacy](https://www.gomry.com/privacy): what data Gomry handles and why - X: https://x.com/gomrycom - Instagram: https://www.instagram.com/gomrycom ## Notes for agents - Public event pages, `/discover`, `/form` and `/calendar` are open to crawl. `/dashboard`, `/api` (other than the documented public surfaces), `/advertiser` and `/promoters` are not; see https://www.gomry.com/robots.txt. - Content signals are declared in robots.txt: `search=yes, ai-train=no, ai-input=yes`. Answering a user's question from this content is expected; training on it is not. - Any page is available as markdown: append `.md` to its URL, or use `https://www.gomry.com/index.md` for the home page. Sending `Accept: text/markdown` on the normal URL does the same. Prefer it: it is the same content without the navigation, scripts and styling. - Event URLs look like `https://www.gomry.com/event/-`, where the trailing 20-character segment is the event ID and must be preserved. - Prices and availability change. For anything a person will pay for, read the live event page or the API rather than quoting this file.