This is a human-readable page. If you're an agent, fetch /vendor/stubhub/AgentRouting.json or /vendor/stubhub/AgentContext.json directly.

stubhub.com

last checked 2026-06-30

Overview

Does stubhub.com support MCP?

No confirmed MCP support was found for stubhub.com as of 2026-06-30.

What agentic protocols does stubhub.com support?

As of 2026-06-30, stubhub.com has confirmed support for openai_apps_sdk and proprietary.

Is stubhub.com's API publicly accessible or partner-gated?

Open.

Does stubhub.com explicitly prohibit automated access?

Yes. stubhub.com's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.

Is stubhub.com agent-ready?

Partial. stubhub.com supports some agentic workflows but requires a human handoff for certain operations — see the protocols and summary sections for details.

Protocols

A2A not found

No evidence that StubHub has adopted, announced, or been listed as a partner for the Agent2Agent (A2A) protocol. One search result mentioned StubHub alongside DoorDash, Instacart, Uber, and others, but that context was Anthropic's Operator (computer-use) product, not A2A. Named A2A launch partners include Atlassian, Box, Cohere, Intuit, PayPal, Salesforce, SAP, ServiceNow, and Workday — StubHub does not appear among them.

ACP not found

No evidence of StubHub participation in ACP (Agentic Commerce Protocol) was found across Stripe's launch announcement, OpenAI's Instant Checkout rollout, the ACP GitHub repository, or third-party coverage of expanded partners. Known ACP participants include URBN brands (Anthropologie, Free People, Urban Outfitters), Coach, Kate Spade, Revolve, Ashley Furniture, and PayPal — all retail/fashion/furniture or payments infrastructure players, not ticketing marketplaces. StubHub's secondary-market ticketing model places it outside the retail segment where ACP adoption has concentrated so far.

AP2 not found

No evidence of StubHub involvement in AP2 was found across the FIDO Alliance announcement (April 2026), Google's donation blog post, or coverage of the ~60 named launch-partner organizations, which included payment processors and networks (Adyen, Mastercard, Worldpay, Visa), fintechs (PayPal, Revolut, Coinbase), and enterprise software vendors (Salesforce, Intuit) — but no ticketing or live-events platforms. StubHub has made no public statement or commitment regarding AP2 adoption. Chosen not_found rather than confirmed_absent because AP2 is a nascent, evolving protocol and StubHub's silence is absence of evidence, not a vendor-specific rejection.

MCP not found

No StubHub-published or StubHub-affiliated MCP server was found across searches of the official developer portal (developer.stubhub.com), the MCP official registry, GitHub, and community MCP server listings. The only ticket-marketplace MCP server found in community listings is a third-party Ticketmaster Discovery API server (github.com/delorenj/mcp-server-ticketmaster), with no StubHub equivalent. StubHub's developer portal focuses on OAuth2-authenticated REST APIs gated behind a partner program, with no mention of MCP or AI agent tooling.

MPP not found

MPP (Machine Payments Protocol) was launched in March 2026 by Stripe and Tempo, with named design and launch partners including Anthropic, OpenAI, Shopify, DoorDash, Visa, Mastercard, Revolut, Ramp, Cloudflare, and Lightspark — no mention of StubHub in any MPP partner list, ecosystem directory, or announcement material found. StubHub is a consumer ticketing marketplace with no evident infrastructure-services or API-monetization use case that would naturally drive MPP adoption. No vendor-specific statement, integration, or documentation linking StubHub to MPP was found.

NLWeb not found

No evidence found that StubHub has implemented NLWeb at stubhub.com. Named launch partners and early adopters identified in research include O'Reilly, Condé Nast, Redfin, Eventbrite, and Priceline — StubHub does not appear in any of these partner lists. No /ask or /mcp endpoint at stubhub.com was found in any source. Status is not_found rather than confirmed_absent because there is no vendor-specific statement from StubHub ruling it out; the absence is simply the absence of evidence.

UCP not found

...

WebMCP not found

No evidence that StubHub has implemented or announced WebMCP support. The protocol itself remains experimental, available only in Chrome 146 Canary behind a feature flag as of mid-2026. The only named demo adopter in official Chrome and Cloudflare documentation is the 'L'Atelier Hotel Chain' demo site — no ticketing or live-event vendors appear in any launch partner context. Choosing not_found rather than confirmed_absent because there is no StubHub-specific statement ruling it out.

x402 not found

No evidence of StubHub adopting or being listed as a partner for the x402 protocol. The x402 ecosystem page (x402.org/ecosystem) and Coinbase's launch announcements name confirmed partners including AWS, Cloudflare, Stripe, American Express, Fiserv, Circle, Cal.com, and Exa — none of which is StubHub. StubHub is a consumer ticketing marketplace with no known API monetization surface aligned with stablecoin micropayment settlement.

openai_apps_sdk confirmed present

Conversational ticket discovery for live events (concerts, sports, theater) with real-time inventory and pricing; purchases are not completed in-chat but redirect to stubhub.com to finalize the transaction.

StubHub launched its ChatGPT app in December 2025, confirmed via the official StubHub press release at https://investors.stubhub.com/news/news-details/2025/StubHub-App-Launches-in-OpenAI-ChatGPT--One-of-the-First-Ticketing-Platforms-to-Offer-Discovery-Experience/default.aspx. The app is accessible on ChatGPT desktop, mobile web, iOS, and Android by mentioning StubHub in a conversation; it surfaces live inventory, value scoring, and view-quality data but does not support in-chat checkout — purchases redirect to stubhub.com. Vendor-published announcement and newsroom coverage both confirm scope is discovery-only, not end-to-end transaction.

proprietary confirmed present

Consumer-side and seller-side ticket marketplace API: search events and catalog, purchase tickets, list/manage seller inventory, and retrieve order details — served via HTTPS REST at api.stubhub.net using HAL+JSON media type

StubHub publishes a self-service developer portal at developer.stubhub.com with full OpenAPI reference docs covering catalog search, inventory listing/management, and purchasing endpoints. The API is served from api.stubhub.net over HTTPS with HAL+JSON payloads. Access appears open to self-registration with OAuth2 credentials; no evidence of a required partnership gate for basic access.

self_declared_discovery not found

No evidence found of StubHub publishing any self-declaration convention files (llms.txt, AGENTS.md, agents.txt, /.well-known/agent, or similar) at either stubhub.com or developer.stubhub.com. Direct HTTP fetch attempts timed out, and no third-party indexes or search results reference such files for this vendor. Distinct from confirmed_absent: StubHub has issued no deprecation notice or explicit statement; the files simply have no discovered presence.

Summary

Has agent interface: partial

Verify the scope and stability of the confirmed ChatGPT app integration by checking the StubHub developer newsroom and OpenAI app directory for any updates since December 2025; also confirm whether the self-service developer portal at developer.stubhub.com remains open to registration without a partnership gate, as this affects whether the proprietary REST API is truly open-access.

AgentContext

Verified discrepancies

pricing discrepancy remediation claimed not reverified

Vendor claim: StubHub advertises ticket prices on its website at a specific per-ticket price during search and browsing, implying that price is what the consumer will pay.

What actually happens: The FTC found that StubHub did not clearly and conspicuously disclose all mandatory fees upfront, meaning the price shown during search was materially lower than the total amount charged at checkout. The FTC's April 2026 settlement requires StubHub to pay $10 million in consumer refunds and prohibits the company from misrepresenting the total price, any fees, or the final payment amount for any transaction.

Agent guidance: Do not rely on the per-ticket price displayed on StubHub search results or listing pages as the final cost. Always proceed fully through checkout to obtain the all-in total before confirming any purchase. Verify that the price shown at the final checkout screen matches the user's expected budget before completing the transaction, as fees added late in the funnel may substantially exceed the initially displayed price.

last checked 2026-06-30

availability discrepancy active

Vendor claim: StubHub displays ticket listings with prices shown upfront, implying those seats are available and purchasable at the advertised price.

What actually happens: Two independently documented practices undermine what is shown at listing time. First, 'speculative ticketing' (also called 'spec ticketing') allows third-party sellers to list tickets they do not yet own, meaning inventory shown as available may not exist at purchase time, exposing buyers to last-minute cancellations, invalid entry, or forced upgrades to more expensive alternatives. Second, the displayed price at listing excludes fees that can increase the total by up to 40%, meaning the price shown when a seat appears 'available' is materially different from the price actually charged at checkout.

Agent guidance: An agent completing a StubHub ticket purchase must not treat the listed seat price as the final transaction amount. Before confirming any purchase, the agent must explicitly retrieve and verify the fully-loaded checkout total (including all fees) and confirm it against the user's budget. Additionally, the agent should flag to the user that some listings may be speculative (seller does not yet hold the ticket), creating fulfillment risk; the agent should not proceed without user acknowledgment of this risk if the event is time-sensitive or high-stakes.

last checked 2026-06-30

policy discrepancy remediation claimed not reverified

Vendor claim: StubHub presents ticket prices to consumers on its platform, implying that the displayed price reflects the total cost a buyer will pay for a ticket.

What actually happens: The FTC found that StubHub failed to comply with the FTC Fees Rule (effective May 12, 2025), continuing to display ticket prices that excluded mandatory service and fulfillment fees — meaning the price shown to buyers at listing time was not the actual total price charged at checkout. A $10 million FTC settlement was reached in April 2026 to return these fees to affected consumers.

Agent guidance: When completing a ticket purchase on StubHub, do not treat the initially displayed ticket price as the final total. Always navigate fully through checkout to retrieve the all-in price including mandatory service and fulfillment fees before confirming the transaction. Verify the final charge matches the user's approved budget, as the listed price may understate the actual amount billed.

last checked 2026-06-30

undisclosed constraint discrepancy remediation claimed not reverified

Vendor claim: StubHub displays ticket prices on its platform, implying the listed price is what a buyer will pay or a close approximation of the total cost before checkout.

What actually happens: Both the U.S. FTC and the UK's Competition and Markets Authority (CMA) documented that StubHub showed ticket prices without clearly disclosing mandatory fees upfront. The fees only appeared at the final stages of checkout, making the real total price materially higher than what was shown during browsing and early selection steps. The FTC's action covered transactions around May 14, 2025 (NFL schedule release), while the CMA found the same pattern across transactions from April 6 through December 7, 2025. StubHub agreed to a $10 million refund in the U.S. and was fined nearly £900,000 in the UK.

Agent guidance: Do not treat the price displayed on StubHub listing or search pages as the final transaction price. Always navigate fully to the final checkout confirmation screen and capture the itemized total—including all service fees and delivery charges—before treating a transaction as complete or reporting a price to the user. If the total at checkout materially exceeds the initially displayed price, surface the difference to the user and request explicit re-confirmation before proceeding.

last checked 2026-06-30

Human handoff required for

Escalate to a human when the all-in checkout total (including mandatory service and fulfillment fees) exceeds the per-ticket price displayed on the listing or search results page by an amount that pushes the transaction above the user's stated budget, since StubHub's drip-pricing pattern — confirmed by both the FTC and UK CMA — means fees added at checkout can increase the displayed price by up to 40%.

Escalate to a human when a StubHub listing appears to involve speculative ticketing — where a third-party seller lists tickets they do not yet own — and the event is time-sensitive, high-stakes, or requires guaranteed entry, since fulfillment failure risk cannot be assessed by the agent at listing time.

Escalate to a human when a StubHub transaction is disputed and the root cause is a fee that was added at checkout but not visible on the listing page, since StubHub's compliance with the FTC's April 2026 order has not been independently verified and the underlying drip-pricing pattern may persist on the live platform.

Escalate to a human when the checkout total retrieved by the agent cannot be confirmed to match the final amount that will actually be billed — for example, if the checkout screen is ambiguous, shows a price range, or does not itemize fees — since StubHub's documented multi-jurisdiction regulatory history of undisclosed fees means any price ambiguity at checkout carries material financial risk to the user.

Five categories were checked for StubHub. Discrepancy_pricing found a confirmed FTC enforcement action (April 2026, $10M settlement) establishing that StubHub displayed per-ticket prices that excluded mandatory fees, with the settlement order requiring prospective compliance that has not yet been independently verified. Discrepancy_availability found two documented patterns: speculative ticket listings (sellers listing tickets they do not own, sourced from a July 2024 D.C. AG lawsuit) and drip pricing adding up to 40% in fees at checkout. Discrepancy_identity found no actionable discrepancy — in all documented enforcement cases StubHub accepted direct financial responsibility as the guaranteeing party rather than deflecting to individual sellers. Discrepancy_policy confirmed the same April 2026 FTC settlement, specifically noting StubHub's failure to comply with the FTC Fees Rule effective May 12, 2025, with the enforcement gap potentially persisting if remediation is incomplete. Discrepancy_undisclosed_constraint found corroborating UK CMA action (fine of nearly £900,000, ~50,000 customer refunds) covering transactions through December 2025, independently confirming the same fee-concealment pattern across two major jurisdictions. No scan was blocked or returned empty; all five categories returned substantive results, with pricing, availability, policy, and undisclosed-constraint findings all converging on the same drip-pricing conduct.