/vendor/grubhub/AgentRouting.json or
/vendor/grubhub/AgentContext.json directly.
grubhub.com
Overview
Does grubhub.com support MCP?
No confirmed MCP support was found for grubhub.com as of 2026-06-29.
What agentic protocols does grubhub.com support?
As of 2026-06-29, grubhub.com has confirmed support for openai_apps_sdk and proprietary.
Is grubhub.com's API publicly accessible or partner-gated?
Access varies by protocol: open, partner only.
Does grubhub.com explicitly prohibit automated access?
Yes. grubhub.com's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is grubhub.com agent-ready?
Partial. grubhub.com supports some agentic workflows but requires a human handoff for certain operations — see the protocols and summary sections for details.
Protocols
No evidence found that Grubhub is a launch partner, adopter, or contributor to the Agent2Agent protocol. The Linux Foundation's June 2025 A2A project announcement names technology companies such as ServiceNow, Microsoft, and Google as founding participants — Grubhub does not appear among them. No Grubhub-specific developer documentation, blog post, or integration referencing A2A was surfaced.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
No evidence that Grubhub is among the roughly 60 organizations that joined Google's AP2 donation to the FIDO Alliance in April 2026. Named launch partners include Adyen, American Express, Ant International, Coinbase, Etsy, Forter, Intuit, Mastercard, PayPal, Revolut, Salesforce, and Worldpay — no Grubhub. AP2 is an early-stage, pre-production protocol (v0.2 as of April 2026) with no consumer-facing travel or food-delivery verticals confirmed as adopters.
No official Grubhub MCP server was found. Grubhub's developer surface (developer.grubhub.com) exposes REST/webhook Partner APIs for POS and menu integration with no MCP layer. Third-party artifacts exist — an internal-tooling GitHub repo (asuar16/gdp-mcp-tools) targeting Grubhub's internal data platform, community mcpmarket.com listings wrapping Grubhub's public site via scraping, and an Apify scraper MCP — but none are vendor-sanctioned. The api-evangelist/grubhub repo references an MCP adapter concept but is a third-party taxonomy project, not an official Grubhub release.
No evidence found of Grubhub participating in the Stripe/Tempo Machine Payment Protocol (MPP) launch or any subsequent adoption. MPP launch coverage names no food-delivery or consumer marketplace partners; the protocol is focused on AI agent-to-agent payments infrastructure. Grubhub's own public materials show no MPP involvement.
No evidence found that Grubhub has implemented or been named as a launch partner for Microsoft's NLWeb protocol. Named launch partners at the May 2025 Build announcement include O'Reilly and Serious Eats (used as a demo site), with no food-delivery platforms mentioned. Grubhub's developer surface is focused on its own REST-based ordering/partner API, with no reference to NLWeb /ask or /mcp endpoints.
No evidence found of Grubhub implementing or partnering on UCP. Google's own blog (blog.google/products-and-platforms/products/shopping/shopping-updates-google-marketing-live/) mentions expanding UCP to 'local food delivery' as a new category, but names only Nike, Sephora, Target, Ulta Beauty, Walmart, Wayfair, and Shopify merchants as current checkout partners — Grubhub is not mentioned. No Grubhub-specific UCP announcement, developer documentation, or press release was found across four targeted searches.
WebMCP is a browser-native agent protocol currently in early-preview/origin-trial stage (Chrome 149), with no public list of named adopters. Google's own communications reference "global consumer brands experimenting" generically but name no specific companies. No evidence was found of Grubhub implementing or announcing WebMCP support; searches against food-delivery vendors (Grubhub, DoorDash, Uber Eats) returned no WebMCP-related results specific to those brands. Not_found rather than confirmed_absent because Grubhub has made no vendor-specific statement ruling it out — the protocol is simply too new and lightly adopted for any attribution here.
No evidence that Grubhub (grubhub.com) is a launch partner or adopter of the x402 HTTP 402 stablecoin micropayment protocol. The Coinbase x402 launch page names infrastructure partners such as Cloudflare and Solana, with no mention of Grubhub. Grubhub is a consumer food-delivery platform with no public developer surface relevant to stablecoin HTTP payments.
Restaurant discovery and food ordering handoff: users can browse real-time restaurant options and menu items via ChatGPT conversation, then are redirected to Grubhub to finalize the transaction. The integration supports meal search and restaurant browsing within the ChatGPT interface but completion occurs on Grubhub's own platform.
Grubhub launched a live ChatGPT app integration in June 2026, confirmed by Fast Casual (June 19, 2026) and Grubhub's own news archive. The integration uses OpenAI's Apps SDK/ChatGPT Apps platform to allow meal discovery and restaurant browsing inside ChatGPT, with order finalization redirecting to Grubhub. No developer-facing docs URL for Grubhub's specific implementation was found; the confirmed_present status is based on vendor-specific press coverage and Grubhub's own news page.
Grubhub Marketplace Partner Integration API (V2): allows POS systems, third-party online-ordering providers, and merchants to manage menus, ingest catalog content, and handle order lifecycle (receive, accept, update status) for orders placed on the Grubhub Marketplace. Does not cover delivery logistics fulfillment for external-origin orders.
Documented at grubhub-developers.zendesk.com. Access requires completing Grubhub's partner onboarding process (pre-production credentials issued first, then QA pilot phase before production). No self-serve signup — relationship-gated. Base API host visible in example calls is api-third-party-gtm.grubhub.com.
Grubhub Connect (DaaS) API: delivery-as-a-service interface allowing external platforms (delivery aggregators, marketplaces, enterprise merchants) to dispatch orders into Grubhub's nationwide courier network for fulfillment. Covers delivery request, driver dispatch, status webhooks, refund updates, and onboarding of merchant locations. Distinct from the Marketplace partner API — does not manage Grubhub Marketplace listings or menus.
Documented at developer.grubhub.com (e.g. https://developer.grubhub.com/docs/5RnVMkJ30pBFfmBSutCQZq/introduction). Marketed explicitly as a DaaS product for orders originating outside the Grubhub app. Access is partner-gated with no public self-serve signup path confirmed. A Postman collection is available for integration testing.
Direct fetch attempts against grubhub.com for /llms.txt, /AGENTS.md, /agents.txt, /.well-known/agent, /.well-known/ai-catalog.json, and /.well-known/agent-card.json all returned HTTP 000 (connection-level failures), indicating the domain blocks automated access. A targeted web search for Grubhub publishing any of these self-declaration files returned no vendor-specific results — only general industry discussion. No evidence that Grubhub has published any self-declared agent discovery file at a predictable domain path. Status is not_found rather than unable_to_verify because the web search (not just the direct fetch) returned no vendor-specific evidence; however, the fetch blockage means passive path checks were impossible, making sketchiness_rating insufficient_data.
Summary
Has agent interface: partial
Verify the June 2026 ChatGPT app integration by checking Grubhub's official news archive and OpenAI's app directory for a stable listing; then assess whether the OpenAI Apps SDK integration exposes any programmatic ordering capability beyond discovery-and-handoff, as current evidence suggests order completion still requires a redirect to Grubhub's own platform.
AgentContext
Verified discrepancies
Vendor claim: Grubhub advertises delivery prices and fees at the point of search and order initiation, implying the costs shown are the full costs the customer will pay.
What actually happens: The FTC and Illinois Attorney General found that Grubhub charged undisclosed 'junk fees' at checkout that in some cases more than doubled the price originally advertised to consumers, constituting a material gap between the displayed price and the actual checkout total.
Agent guidance: Do not treat the price shown on Grubhub's search or menu pages as the final price. Always navigate fully through to the final checkout screen and confirm the itemized total — including all service fees, delivery fees, and any additional charges — before treating the transaction as complete. Compare the checkout total against the price first displayed and flag any gap exceeding a user-specified threshold before confirming the order.
- The FTC press release confirms Grubhub agreed to pay $25 million and to end junk fees to settle charges that it deceived diners about delivery costs, with fees sometimes more than doubling the advertised price.
- A food industry publication reports the FTC found Grubhub 'tacked on junk fees that in some cases more than doubled the original price advertised,' and notes ongoing FTC scrutiny of the broader food delivery fee transparency issue as of April 2026.
- Restaurant Business Online reports the settlement requires Grubhub to disclose full delivery costs up front going forward, confirming the prior practice of not doing so.
Vendor claim: Grubhub presents itself as the single transactional interface for food orders, implying it is the consumer's accountable counterparty for charges, refunds, and account access. Its platform collects payment directly from consumers.
What actually happens: The FTC and the Illinois Attorney General documented that Grubhub blocked consumers from accessing their accounts and the funds held within them after collection, leaving consumers with no clear dispute or refund pathway. Grubhub also listed up to 325,000 restaurants on its platform without those restaurants' permission, meaning consumers could believe they were ordering from an affiliated partner when no such relationship existed — further obscuring who the actual counterparty to the transaction was.
Agent guidance: Before completing any Grubhub transaction for a user, verify that the specific restaurant shown is a confirmed Grubhub partner (not an unaffiliated listing). If a refund or dispute is required post-transaction, do not assume Grubhub will self-resolve it — escalate directly to Grubhub customer support by phone or chat and document the interaction, as account-level blocks have historically prevented fund access. Keep a record of the order confirmation and payment receipt external to the Grubhub app in case account access is restricted.
- The FTC's December 2024 press release details the complaint charge that Grubhub 'blocked their access to their accounts and funds,' and that Grubhub listed unaffiliated restaurants without permission. A $25 million settlement was reached requiring Grubhub to change these practices.
- The FTC's official case record for FTC v. Grubhub Inc. confirms the same charges: deceiving diners about costs, blocking account and fund access, and deceptively listing unaffiliated restaurants.
Vendor claim: Grubhub states that Grubhub+ subscribers receive free or discounted delivery and can cancel their subscription at any time. The platform advertises a simple, low-cost (or no-cost) delivery fee at each step of the ordering flow, implying that the fee shown represents the total cost of delivery services.
What actually happens: The FTC and Illinois Attorney General found, and Grubhub settled, charges that: (1) Grubhub made it deliberately difficult to cancel Grubhub+ subscriptions once enrolled, contrary to its stated easy-cancellation policy; (2) undisclosed 'junk fees' (labeled 'service fees' and 'small order fees') were added only at checkout, often doubling the initially advertised delivery cost; and (3) Grubhub blocked customers from their accounts and gift card balances without adequate notice or recourse. These practices were verified in an 11-count federal complaint filed December 17, 2024, with a $140 million judgment (suspended to $25 million payable) entered against the company.
Agent guidance: Do not rely on the delivery fee displayed during browse or menu-selection steps as the final price — always read the full itemized total on the checkout screen before confirming an order, as additional service fees not shown earlier may materially increase the cost. For Grubhub+ subscription management, verify that a cancellation flow is reachable and confirm cancellation is completed end-to-end rather than assuming the process has concluded; the FTC consent order requires Grubhub to provide simple cancellation but independent re-verification of this fix has not been confirmed.
- FTC case page confirming Grubhub's $25 million settlement for deceiving diners about delivery costs and blocking cancellation of Grubhub+ subscriptions, with the order requiring simple cancellation mechanisms going forward.
- FTC press release detailing all charges, including hidden fees at checkout and suppression of subscription cancellations, filed December 17, 2024.
- FTC complaint PDF filed in federal court spelling out how Grubhub's checkout fees routinely doubled advertised costs and how cancellation flows were deliberately obstructed, in violation of ROSCA and the FTC Act.
Vendor claim: Grubhub advertises low or zero delivery fees (e.g., '$0 delivery' or 'free delivery' for Grubhub+ subscribers) at the point when a user browses and selects items, implying that the displayed price reflects the true cost of completing the order.
What actually happens: At checkout, Grubhub adds substantial undisclosed service fees that were not surfaced earlier in the transaction flow. The FTC found these fees could more than double the advertised delivery cost. Even Grubhub+ subscribers marketed 'free delivery' were charged delivery fees mid-transaction. These constraints are discovered only after the user is already committed to the order, not at the start of browsing.
Agent guidance: An agent placing a Grubhub order must not treat the price shown during browsing or item selection as the final order total. Before confirming any transaction, the agent must capture and present to the user the full itemized checkout screen — including all service fees, delivery fees, and any other charges added after item selection — and obtain explicit user approval of the final total before submitting the order.
- FTC complaint filed December 17, 2024 alleges Grubhub charged hidden fees at checkout that often doubled the advertised cost, and that Grubhub+ 'free delivery' subscribers were still charged delivery fees.
- Grubhub agreed to pay a $25 million settlement to resolve the FTC lawsuit; the agency found the hidden fee practices constituted unlawful deception of consumers.
Human handoff required for
Escalate to a human when the itemized checkout total on Grubhub exceeds the price displayed at browse or menu-selection by more than the user's stated acceptable threshold, because FTC-confirmed undisclosed service fees and delivery fees may materially inflate the final charge beyond what was initially shown.
Escalate to a human when a refund or dispute is required and Grubhub's platform does not provide a clear resolution pathway, because regulators documented that Grubhub blocked consumer access to accounts and funds after collecting payment with no adequate recourse mechanism.
Escalate to a human when the restaurant shown on Grubhub cannot be confirmed as an actual Grubhub partner, because regulators found Grubhub listed up to 325,000 restaurants without their consent, meaning the displayed counterparty may not have an actual transactional relationship with Grubhub.
Escalate to a human when attempting to cancel a Grubhub+ subscription if the cancellation flow does not reach a confirmed end state, because the FTC found Grubhub deliberately obstructed the cancellation process contrary to its stated easy-cancellation policy.
Escalate to a human when a Grubhub+ subscriber is charged any delivery fee mid-transaction despite being marketed 'free delivery,' because the FTC confirmed Grubhub charged delivery fees to subscribers whose plan advertised free delivery.
Five categories were checked for Grubhub. Discrepancy_pricing: a major finding was confirmed via the December 2024 FTC and Illinois AG enforcement action documenting undisclosed junk fees at checkout. Discrepancy_availability: no primary-source finding of systemic pre-checkout inventory misrepresentation was identified; complaints found relate to post-delivery fulfillment accuracy only. Discrepancy_identity: a finding was confirmed documenting that Grubhub blocked consumer account and fund access and listed up to 325,000 restaurants without consent, obscuring the true transactional counterparty. Discrepancy_policy: a finding was confirmed showing Grubhub's cancellation and fee disclosure policies materially differed from actual platform behavior per the FTC complaint. Discrepancy_undisclosed_constraint: a finding was confirmed showing that material service and delivery fees were systematically withheld until the checkout stage. All four findings with confirmed evidence reference the same December 2024 FTC regulatory action; independent post-settlement compliance verification was not available in any category.