Ticketmaster

Limits

• It cannot buy, reserve, pay for or cancel anything. Ticketmaster states the assistant does not process payment and that purchases complete on Ticketmaster. Every result terminates in a link you follow.
• Ticketmaster publishes no tool list. The two names come from Anthropic's directory and could not be diffed against a vendor enumeration, because none exists. Ticketmaster's own connector page never prints either name.
• We could not verify the auth posture live. Anthropic's directory records the endpoint as authless with an auth posture of no auth, and Ticketmaster says no account is needed to search — but both are claims *about* the server, not our observation of it. Our single anonymous initialize request returned HTTP 403 from a Varnish edge cache with an HTML error body and no WWW-Authenticate header, which is an edge block rather than an authentication challenge. authVerified is therefore false on this page.
• No scope document is readable. Four probes for RFC 9728 and OAuth metadata each returned the same 437-byte Varnish 403 as a deliberately nonsensical control path, differing only in the cache-node identifier the error prints. No scopes_supported value was observed either way, so no boundary between reading and any other operation is claimed or refuted.
• We could not read any tool schema or safety annotation. No parameter name for either tool appears anywhere we could find.
• Whose credential the server presents is undocumented. Ticketmaster's APIs authenticate by an API key issued to a registered developer or partner, passed as an apikey parameter or an x-api-key header — a company credential carrying no user identity. No document states whether this connector calls under such a key or under something else, so who bears the quota and terms consequences of a call is unresolved.
• Terms restrict what you may do with the data. Ticketmaster's API Terms of Use forbid caching or storing Event Content other than for reasonable periods needed to provide your service, forbid selling or deriving revenue from API access, and forbid applications that replicate the essential user experience of Ticketmaster.com. They also require removing Event Content within 24 hours of an owner's request. Building a product on connector output is a licensing question, not just a technical one.
• No rate limit is published for the MCP endpoint, and Ticketmaster's own two figures disagree. The getting-started page states 5,000 calls per day at 5 requests per second; the developer FAQ states 5,000 per day at 2 requests per second. Both describe the public API, not this endpoint, and we found no statement that the MCP server shares either quota.
• One Ticketmaster documentation path is dead, and the real one is elsewhere. The path /support/partner-api-terms-of-use/ redirects to a 404 page. The Partner API Terms of Use do exist, at /support/terms-of-use/partner/, and repeat the General Terms' restrictions verbatim. The developer portal's sitemap is also stale: it lists 19 URLs, most with a 2016 last-modified date, and omits the Partner API FAQ and the current Discovery v2 path entirely.
• Ticketmaster's terms say nothing about AI agents. Neither Terms of Use nor the developer FAQ contains AI-, LLM- or model-specific language; the General Terms were last updated in June 2023. The applicable clauses are generic ones — no automated content, no concealing your application's identity, and rate limiting for calls not primarily in response to direct user actions. Read them as covering the case by implication, not by name.
• Prices and availability move fast. Ticketmaster states results reflect what is actually on sale right now. For a high-demand onsale, a snapshot in a conversation can be stale by the time you follow the link.
• The consumer Terms of Use could not be read. Ticketmaster's fan-facing terms render entirely client-side; the fetched HTML carries no __NEXT_DATA__, RSC flight payload or embedded JSON block, so its clauses on automation and ticket limits are not reported here. That is an extractor failure on our side, not evidence Ticketmaster published nothing.

Frequently asked questions

Sources

• Ticketmaster connector documentation, "Using Ticketmaster in ChatGPT and Claude" (retrieved 2026-08-22). Named as the documentation URL in Anthropic's directory entry. Carries no text addressed to AI systems. Three alternate doc routes — llms.txt, llms-full.txt and the .md suffix — each returned a 302 to a 31-byte redirect stub, so the nominated page is the only one. · retrieved 2026-08-22
• Ticketmaster developer FAQ (retrieved 2026-08-22). Source for the 2-per-second / 5,000-per-day default quota and for Partner Commerce API access being restricted to a select few business partners. · retrieved 2026-08-22
• Ticketmaster Partner API FAQ (retrieved 2026-08-22). Source for the reserve, payment, shipping, commit-cart and fulfillment stages, and for card encryption being mandatory. · retrieved 2026-08-22
• Ticketmaster API Terms of Use (retrieved 2026-08-22). Source for the caching, revenue, replication, 24-hour-removal and automated-content restrictions. · retrieved 2026-08-22
• Ticketmaster Partner API documentation (retrieved 2026-08-22). Source for the Partner API being closed, for apikey / x-api-key authentication, and for the best practice that add-billing and commit-cart not be chained programmatically. · retrieved 2026-08-22
• Ticketmaster Partner API Terms of Use (retrieved 2026-08-22). The nav path /support/partner-api-terms-of-use/ 404s; this is the working URL. · retrieved 2026-08-22
• Ticketmaster developer getting-started page (retrieved 2026-08-22). Source for API-key registration, for transacting against offers being partners-only, and for the 5-per-second quota figure that conflicts with the FAQ's 2. · retrieved 2026-08-22
• Ticketmaster developer robots.txt (retrieved 2026-08-22). No Disallow rules and no Content-Signal header; the documentation path is permitted. · retrieved 2026-08-22
• Live auth-posture check: one anonymous initialize request to https://partner-mcp.ticketmaster.com/mcp returned HTTP 403 from Varnish with an HTML error body and no WWW-Authenticate header (2026-08-22). Four .well-known probes plus a nonsense control path all returned the same 437-byte Varnish 403, hash-differing only in the cache-node identifier. · retrieved 2026-08-22
• Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
• Ticketmaster support — · Privacy