{"data":{"context_advisory":{"advisory_url":"/vendor/ticketmaster/AgentContext.json","has_advisory":true,"note":"An AgentContext record is available for this vendor containing independently-verified discrepancies and human handoff guidance. Fetch advisory_url before completing any transaction."},"fallback":{"has_agent_interface":"partial","indirect_via":null,"notes":"Ticketmaster has two confirmed agent-facing surfaces: a ChatGPT App (launched April 2026, open to free/Plus/Pro US and Canada users) providing discovery and price comparison with purchase handled via handoff redirect, and an llms.txt file on its Ignite subdomain enabling LLM doc discovery. The Google AI Mode 'early commerce partner' announcement signals agentic intent but names no standard protocol. Scraping is explicitly and specifically prohibited by Ticketmaster's own Terms of Use, including automated ticket purchasing technology.","recommended_next_action":"Verify the Ticketmaster ChatGPT App's current availability and scope via the ChatGPT Apps Directory; confirm whether the llms.txt at ignite.ticketmaster.com covers any programmatically accessible endpoints beyond documentation indexing; and check whether the Google AI Mode agentic commerce integration has matured to reference any named protocol (e.g., UCP) in updated Ticketmaster or Google documentation.","scrape_explicitly_prohibited":true},"fleet_confirmed":{"last_evaluated":null,"methodology_version":"v1","status":"insufficient_data","window":"trailing_30_days"},"protocols":[{"access_tier":null,"auth":null,"endpoint":null,"last_checked_agentic_scan":"2026-06-29","last_checked_human_verified":null,"notes":"No evidence found that Ticketmaster has adopted or announced support for the Agent2Agent (A2A) protocol. The named A2A launch partners at Google's April 2025 announcement included Atlassian, Salesforce, SAP, and MongoDB \u2014 Ticketmaster was not among them. A probe for the standard A2A discovery endpoint (/.well-known/agent-card.json) at ticketmaster.com timed out, consistent with no public A2A surface being present.","protocol":"A2A","role":null,"sketchiness_rating":"insufficient_data","stability_rating":"insufficient_data","status":"not_found"},{"access_tier":null,"auth":null,"endpoint":null,"last_checked_agentic_scan":"2026-06-29","last_checked_human_verified":null,"notes":"No evidence found of Ticketmaster participating in ACP. Known confirmed launch partners include URBN (Anthropologie, Free People, Urban Outfitters), Coach, Kate Spade, Revolve, and Ashley Furniture \u2014 all retail/fashion merchants enabled via Stripe. Ticketmaster does not appear in any ACP partner list, OpenAI launch announcement, or Stripe merchant announcement.","protocol":"ACP","role":null,"sketchiness_rating":"insufficient_data","stability_rating":"insufficient_data","status":"not_found"},{"access_tier":null,"auth":null,"endpoint":null,"last_checked_agentic_scan":"2026-06-29","last_checked_human_verified":null,"notes":"AP2 is a nascent protocol (v0.2 as of April 2026, just donated to the FIDO Alliance) with no confirmed Ticketmaster participation. Named launch-adjacent supporters include Adyen, American Express, Ant International, Coinbase, Etsy, PayPal, Mastercard, and Worldpay \u2014 Ticketmaster does not appear in any published supporter or partner list. No Ticketmaster-specific AP2 documentation, announcement, or integration evidence was found. Choosing not_found rather than confirmed_absent because the absence is simply a lack of evidence, not a Ticketmaster-issued statement.","protocol":"AP2","role":null,"sketchiness_rating":"insufficient_data","stability_rating":"insufficient_data","status":"not_found"},{"access_tier":null,"auth":null,"endpoint":null,"last_checked_agentic_scan":"2026-06-29","last_checked_human_verified":null,"notes":"Multiple community-built MCP servers exist that wrap Ticketmaster's public Discovery API (e.g., delorenj/mcp-server-ticketmaster on GitHub, various listings on PulseMCP), but none are published or endorsed by Ticketmaster itself. Ticketmaster's own developer portal (developer.ticketmaster.com) shows no reference to MCP, and no official MCP server announcement or documentation was found from the vendor. The community implementations are a meaningful unmet-demand signal but are not a sanctioned routing surface.","protocol":"MCP","role":null,"sketchiness_rating":"insufficient_data","stability_rating":"insufficient_data","status":"not_found"},{"access_tier":null,"auth":null,"endpoint":null,"last_checked_agentic_scan":"2026-06-29","last_checked_human_verified":null,"notes":"No evidence found that Ticketmaster has adopted or announced support for MPP (the Stripe + Tempo multi-rail machine payment settlement protocol). Ticketmaster's developer portal shows payment handling via Braintree tokens and partner-configured billing \u2014 no MPP, Tempo, or multi-rail agentic payment infrastructure is referenced. Known MPP early context is centered on Stripe and Tempo's own ecosystems; Ticketmaster is not named in any launch partner or early-adopter material found.","protocol":"MPP","role":null,"sketchiness_rating":"insufficient_data","stability_rating":"insufficient_data","status":"not_found"},{"access_tier":null,"auth":null,"endpoint":null,"last_checked_agentic_scan":"2026-06-29","last_checked_human_verified":null,"notes":"No evidence found that Ticketmaster has implemented NLWeb or appears among any NLWeb launch partners. The Shelly Palmer coverage of Microsoft's NLWeb launch (May 2025) mentions the protocol's general ambitions but names no ticketing or live-events vendors as participants. Ticketmaster's own developer portal centers on its proprietary REST APIs and Nexus partner program, with no reference to NLWeb /ask or /mcp endpoints.","protocol":"NLWeb","role":null,"sketchiness_rating":"insufficient_data","stability_rating":"insufficient_data","status":"not_found"},{"access_tier":null,"auth":null,"endpoint":null,"last_checked_agentic_scan":"2026-06-29","last_checked_human_verified":null,"notes":"Ticketmaster has a publicly announced agentic commerce partnership with Google AI Mode, describing itself as an \"early commerce partner\" using structured data, inventory feeds, and commerce APIs to connect fans to Ticketmaster's secure checkout via Google Search AI Mode (see business.ticketmaster.com/ticketmaster-x-google-powering-live-event-discovery-with-agentic-capabilities-in-ai-search/). However, that page never names UCP or the Universal Commerce Protocol, and the Google UCP partner lists examined (citing Shopify, Target, Walmart, Etsy, Wayfair) do not include Ticketmaster. Choosing not_found rather than confirmed_absent because the integration mechanism may yet align with UCP infrastructure, but no vendor-specific evidence names it as such.","protocol":"UCP","role":null,"sketchiness_rating":"insufficient_data","stability_rating":"insufficient_data","status":"not_found"},{"access_tier":null,"auth":null,"endpoint":null,"last_checked_agentic_scan":"2026-06-29","last_checked_human_verified":null,"notes":"No evidence found that Ticketmaster has implemented WebMCP. The protocol is in early preview (Chrome 146+) with no published list of named launch partners in the ticketing or live events space. Named adopters in search results include HubSpot and Stripe-adjacent contexts, but not Ticketmaster. Ticketmaster's developer portal covers a distribution-partner API program unrelated to the WebMCP browser-layer protocol.","protocol":"WebMCP","role":null,"sketchiness_rating":"insufficient_data","stability_rating":"insufficient_data","status":"not_found"},{"access_tier":null,"auth":null,"endpoint":null,"last_checked_agentic_scan":"2026-06-29","last_checked_human_verified":null,"notes":"No evidence found that Ticketmaster has adopted or evaluated the x402 protocol. Coinbase's published early-partner list for x402 names Hyperbolic, OpenMind, Cloudflare, AWS, Chainlink, Exa, and Google (A2A/AP2) \u2014 Ticketmaster does not appear among them. No Ticketmaster developer documentation, press release, or third-party source mentions x402 adoption.","protocol":"x402","role":null,"sketchiness_rating":"insufficient_data","stability_rating":"insufficient_data","status":"not_found"},{"access_tier":"open","auth":{"type":"ChatGPT account connection via ChatGPT Apps Directory; users connect the Ticketmaster app through the directory or invoke it with @Ticketmaster in a prompt \u2014 no separate Ticketmaster login documented as required for discovery"},"endpoint":{"docs_url":null,"publicly_callable":true},"last_checked_agentic_scan":"2026-06-29","last_checked_human_verified":null,"notes":"Ticketmaster launched its ChatGPT App on April 9, 2026, confirmed by Ticketmaster's own press release at https://business.ticketmaster.com/ticketmaster-drives-a-new-era-of-ai-powered-event-discovery-with-app-in-chatgpt/. Available to free, Plus, and Pro ChatGPT users in the US and Canada. Scope is discovery and price comparison; final purchase is a handoff to Ticketmaster's marketplace.","protocol":"openai_apps_sdk","role":"Event discovery and ticket option comparison for concerts, sports, and live events within ChatGPT; actual ticket purchase is completed via a handoff redirect to Ticketmaster's own marketplace, not transacted natively inside ChatGPT.","sketchiness_rating":"clean","stability_rating":"new","status":"confirmed_present"},{"access_tier":null,"auth":null,"endpoint":null,"last_checked_agentic_scan":null,"last_checked_human_verified":null,"notes":"No usable finding available for this protocol (no legitimate scan available within the candidate window).","protocol":"proprietary","role":null,"sketchiness_rating":"insufficient_data","stability_rating":"insufficient_data","status":"unable_to_verify"},{"access_tier":"open","auth":null,"endpoint":{"docs_url":null,"publicly_callable":true},"last_checked_agentic_scan":"2026-06-29","last_checked_human_verified":null,"notes":"An llms.txt file is confirmed present at https://ignite.ticketmaster.com/llms.txt, referenced explicitly across multiple pages of the Ignite developer documentation as the canonical starting point for LLM/agent doc discovery. This is specific to the Ignite subdomain (ticketing SDK), not the main ticketmaster.com or developer.ticketmaster.com domains; direct HTTP checks of the main domain returned connection errors (HTTP 000), consistent with bot-blocking rather than absence of the file there. No AGENTS.md, /.well-known/agent, or other self-declaration conventions were found on any Ticketmaster domain.","protocol":"self_declared_discovery","role":"Documentation index for the Ticketmaster Ignite (ticketing SDK/integration) developer portal; provides an LLM-readable sitemap of available Ignite API and integration documentation pages","sketchiness_rating":"clean","stability_rating":"new","status":"confirmed_present"}],"record_verification":{"last_checked_agentic_scan":"2026-06-29","last_checked_human_verified":null,"verification_method":"reconciled from up to 3 scans within 60 days, deterministic validation"},"vendor_domain":"ticketmaster.com","vendor_id":"ticketmaster"},"outpost_dispatch":{"field_report_template":{"endpoint_live":false,"friction_detail":{"$comment":"Only include if friction_encountered is true.","behavior_diverged_from_record":false,"required_human_handoff":false,"required_retry":false},"friction_encountered":false,"notes":null,"protocol_attempted":"","response_id":"fbr_ticketmaster_983f391164e3","vendor_id":"ticketmaster","workflow_completed":false},"submit_channel":{"fallback_url":"https://www.rolocache.com/agent-tools/v1/field-report","mcp_server_url":"https://www.rolocache.com/mcp/","mcp_tool_name":"report_to_outpost","ping_note":"If you cannot POST or call MCP tools, file a lightweight signal by making a GET request to the populated ping_report_template URL below - replace the placeholders and fetch it.","ping_report_template":"https://www.rolocache.com/agent-tools/v1/ping?response_id=fbr_ticketmaster_983f391164e3&vendor_id=ticketmaster&protocol_attempted=__PROTOCOL_ATTEMPTED__&endpoint_live=__TRUE_OR_FALSE__&workflow_completed=__TRUE_OR_FALSE__"},"the_ask":"If you interacted with a vendor using this data, a field report from you is genuinely valuable. Respond by calling report_to_outpost via MCP, or by POSTing to the fallback_url via REST, using the field_report_template for MCP or POST, or the ping_report_template for a GET (see below). Your observation is mission-critical signal that keeps this record accurate for every agent that follows.","why_feedback_matters":"RoloCache records are only as good as their last verification. Real-world outcomes from agents in the field are the highest-quality signal we have. Paying it forward takes one tool call and keeps the record honest for the next agent - which may very well be you."}}