/vendor/grab/AgentRouting.json or
/vendor/grab/AgentContext.json directly.
grab.com
Overview
Does grab.com support MCP?
No confirmed MCP support was found for grab.com as of 2026-06-30.
What agentic protocols does grab.com support?
As of 2026-06-30, grab.com has confirmed support for proprietary.
Is grab.com's API publicly accessible or partner-gated?
Partner only.
Does grab.com explicitly prohibit automated access?
Yes. grab.com's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is grab.com agent-ready?
Partial. grab.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 linking grab.com to A2A (Agent2Agent) adoption, partnership, or implementation. The confirmed A2A founding and growth partners include Atlassian, Box, Cohere, Intuit, LangChain, MongoDB, PayPal, Salesforce, SAP, ServiceNow, and Workday — Grab appears in none of these lists. Searches targeting grab.com specifically against A2A returned only general protocol documentation and unrelated results.
No evidence found that Grab (grab.com) has adopted or integrated the Agentic Commerce Protocol. Known confirmed ACP launch partners include URBN brands, Coach, Kate Spade, Revolve, Ashley Furniture, and Checkout.com — none of which are Grab. Grab operates as a Southeast Asian super-app (ride-hailing, food delivery, fintech) and does not appear in any ACP partner lists, OpenAI commerce developer documentation, or Stripe ACP newsroom announcements. Choosing not_found rather than confirmed_absent because no vendor-specific statement or deprecation notice from Grab itself was found.
No evidence of Grab (grab.com) appearing in any AP2 launch partner list or contributor announcement. The ~60 organizations named in the April 2026 FIDO Alliance donation announcement include Adyen, American Express, Ant International, Coinbase, Etsy, Mastercard, PayPal, Revolut, and others — Grab is not among them. AP2 is an early-stage protocol (v0.2 released April 28, 2026) with no vendor-specific Grab documentation or integration found.
No official MCP server from Grab (grab.com) was found. The only MCP server found — github.com/hithereiamaliff/mcp-grabmaps — is explicitly disclaimed as 'NOT officially affiliated with Grab, GrabMaps, or AWS Location Service' and is a community-built third-party wrapper around the GrabMaps REST API (geocoding, routing, places — Southeast Asia only). Grab's own developer portals (developer.grab.com, grabmaps.grab.com) show no MCP offering. The third-party server's existence signals unmet agent demand.
No evidence found that Grab (grab.com) has adopted or listed MPP support. Named launch and ecosystem partners include Anthropic, DoorDash, Mastercard, Nubank, OpenAI, Ramp, Revolut, Shopify, Standard Chartered, Visa, and Cloudflare — Grab does not appear in any of these partner lists. The not_found rather than confirmed_absent status reflects absence of evidence specific to Grab's own posture, not a vendor statement of non-adoption.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
No evidence found that Grab (grab.com) has adopted, integrated with, or announced support for the Universal Commerce Protocol. Searches surfaced UCP partnership announcements naming Shopify, Walmart, Etsy, and Google as collaborators, with no mention of Grab. Grab does operate its own internal AI shopping agent (GrabMart), but this is a proprietary in-app capability, not a UCP-based interface.
No evidence found that Grab (grab.com) has adopted or announced WebMCP support. The WebMCP early preview program (launched via Chrome for Developers) lists no Grab participation; known early adopters are primarily web-native commerce and lead-generation platforms, not Southeast Asian superapps. Grab's publicly documented AI efforts focus on internal model usage and app-native features, not browser-layer agent tooling.
No evidence that grab.com (Grab Holdings / GrabPay) appears in any x402 launch partner list, integration announcement, or developer documentation. Known x402 early adopters and ecosystem participants include Coinbase's own developer platform, Google (via AP2), Stellar Foundation, and various AI-agent tooling projects — none of these reference Grab. Grab's developer surface centers on GrabPay, GrabPlatform, and conventional REST APIs, with no stablecoin or HTTP-402 payment layer mentioned.
No evidence found of Grab (grab.com) publishing an official ChatGPT App (custom GPT or plugin) on the OpenAI platform. Searches surfaced only: (1) a Grab partnership bundling ChatGPT Plus subscriptions with GrabUnlimited consumer plans, and (2) an internal Grab employee AI tool called GrabGPT — neither of which constitutes a publicly callable ChatGPT App built on the OpenAI Apps SDK. No vendor-specific deprecation notice was found, so not_found rather than confirmed_absent is appropriate.
Multi-product platform API covering user identity/authentication (GrabID OAuth), ride-hailing/transport booking, food and grocery delivery, on-demand logistics (GrabExpress), payments, mapping, messaging, and in-app mini-program integrations — collectively branded GrabPlatform. Partner enrollment requires registration through the developer portal at developer.grab.com before credentials are issued; there is no fully open self-serve path.
Grab's proprietary REST API surface is documented at developer.grab.com and spans transport, food delivery, logistics, payments, identity, and mapping verticals under the GrabPlatform brand, announced in 2018. Access requires partner registration; documentation and SDKs (JS, Android, iOS) are publicly visible on GitHub (github.com/grab) and the developer portal, but live endpoint access is gated behind an approved partner account. No evidence of a distinct supply-side or fleet-management API separate from this unified partner-facing surface was found.
Direct HTTP probes of grab.com and www.grab.com for /llms.txt, /agents.md, /AGENTS.md, /.well-known/agent, /.well-known/agents.json, and /agents.txt all returned connection failures (HTTP 000), consistent with the domain blocking automated curl requests rather than serving these files. The same probes against developer.grab.com also failed. No web search results surfaced any evidence of Grab publishing any self-declaration discovery file at any of these paths. No vendor-specific evidence of such files was found.
Summary
Has agent interface: partial
Monitor developer.grab.com for any MCP server announcement or agentic protocol adoption; a community-built third-party MCP wrapper already exists for GrabMaps (github.com/hithereiamaliff/mcp-grabmaps), signaling real unmet agent demand. If direct integration is needed now, pursue partner registration at developer.grab.com to access the confirmed GrabPlatform REST API (OAuth 2.0 / GrabID), which covers transport, food delivery, logistics, payments, and mapping.
AgentContext
Verified discrepancies
Vendor claim: Grab positions itself as the payment collection agent and the platform through which consumers transact, implying end-to-end accountability. Its consumer-facing app collects payment and issues order confirmations directly to users, suggesting Grab is the counterparty to the purchase.
What actually happens: Grab's own published Merchant Terms and Conditions explicitly disclaim liability for goods and disputes, stating that Grab 'shall not be involved in any agreements, terms and conditions or rights and obligations between the End User and the Merchant' and that 'GRAB shall in no event be liable for any liabilities…in respect to any services provided by the Merchant.' Grab further defines its payment collection role as 'solely mechanical and administrative in nature' with no fiduciary duty. Separately, Fiserv's merchant payment agreement for the Grab network (Malaysia, July 2024) confirms that merchants bear all risk of loss on transaction reversals and that the merchant 'may not have rights to dispute a Grab transaction reversal.' This creates a documented gap: consumers pay Grab, Grab disclaims merchant-of-record liability and points to the individual merchant, but those merchants have contractually limited dispute rights against Grab — leaving consumers without a clear, enforceable counterparty for refunds.
Agent guidance: When completing a purchase transaction on Grab on behalf of a user, explicitly confirm with the user before checkout which party (the individual merchant listed in the app, not Grab) will be the responsible counterparty for any refund or dispute. Do not represent Grab as the merchant of record. If the user intends to rely on a specific dispute or refund right, surface the relevant merchant's own return policy before payment is submitted, because Grab's platform terms explicitly disclaim Grab's own liability for goods and order disputes.
- Grab's official Merchant Terms and Conditions (last modified August 2024) state that Grab is not party to the end-user/merchant agreement, disclaim all Grab liability for goods disputes, and describe Grab's payment role as 'solely mechanical and administrative in nature.'
- Fiserv's Merchant Agreement for the Grab Network (Malaysia, Version 5.2, July 2024) states that Fiserv 'has no liability for any failure by Grab' to pay and that the merchant 'may not have rights to dispute a Grab transaction reversal,' placing all loss risk on the merchant.
Human handoff required for
Escalate to a human before completing any purchase on behalf of a user when the user expresses intent to rely on a platform-level refund or dispute right, because Grab's Merchant T&Cs explicitly disclaim Grab's own liability for goods and order disputes and direct users to the individual merchant — who itself has contractually limited recourse against Grab for transaction reversals.
- Grab's published Merchant Terms and Conditions state that Grab 'shall not be involved in any agreements, terms and conditions or rights and obligations between the End User and the Merchant' and that 'GRAB shall in no event be liable for any liabilities…in respect to any services provided by the Merchant,' characterising its payment role as 'solely mechanical and administrative in nature.'
- A Fiserv merchant payment agreement covering the Grab network (Malaysia, July 2024) confirms that merchants bear all risk of loss on transaction reversals and 'may not have rights to dispute a Grab transaction reversal,' leaving consumers without a clear, enforceable counterparty when a dispute arises.
Escalate to a human before submitting payment on behalf of a user if the user has not been explicitly informed that the individual merchant listed in the Grab app — not Grab itself — is the responsible counterparty for any refund, return, or dispute on that order, because Grab collects payment but contractually disclaims merchant-of-record status.
- Grab's Merchant T&Cs make clear that Grab acts purely as an intermediary collecting payment on the merchant's behalf and bears no contractual liability for the goods or services delivered, meaning any post-purchase dispute must be pursued against the individual merchant rather than Grab.
- The Fiserv/Grab merchant agreement confirms that merchants cannot dispute Grab-initiated transaction reversals, creating a structural gap where consumers who paid Grab may find that neither Grab nor the merchant has a clear enforceable obligation to process their refund.
Five categories were checked for Grab (grab.com). Discrepancy_pricing: searches found no documented evidence of hidden fees, checkout-price gaps, or regulatory actions specific to Grab's consumer platform; an unrelated Grubhub FTC settlement and a Grab Holdings securities settlement were surfaced but did not meet the inclusion bar. Discrepancy_availability: searches returned only aggregator legitimacy checks, third-party scam warnings about Grab impersonators, and unrelated sites; no primary-source evidence of ghost listings or bait-and-switch pricing was found. Discrepancy_identity: a finding was confirmed based on Grab's own published Merchant T&Cs (August 2024) and a Fiserv merchant payment agreement (July 2024), both of which document a structural gap between Grab's payment-collection role and its explicit disclaimer of merchant-of-record liability. Discrepancy_policy: Grab's own published cancellation and refund policy pages were located, and a Philippine Senate hearing on a driver-side regulatory dispute was surfaced, but no independently verified evidence of systematic policy-vs-enforcement gaps was found. Discrepancy_undisclosed_constraint: Grab's help center was referenced but not fully accessible; no independently verified reports of hidden capability restrictions or mid-transaction failures were found, and Grab's disclosed GrabPay limit pages are consistent with transparent rather than hidden constraints.