/vendor/bolt/AgentRouting.json or
/vendor/bolt/AgentContext.json directly.
bolt.eu
Overview
Does bolt.eu support MCP?
No confirmed MCP support was found for bolt.eu as of 2026-06-30.
What agentic protocols does bolt.eu support?
No confirmed agentic protocol support was found for bolt.eu as of 2026-06-30.
Is bolt.eu's API publicly accessible or partner-gated?
Access tier information is not available for bolt.eu.
Does bolt.eu explicitly prohibit automated access?
Yes. bolt.eu's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is bolt.eu agent-ready?
Not currently. No confirmed agent-callable interface was found for bolt.eu as of 2026-06-30.
Protocols
No evidence found that bolt.eu (the ride-hailing and mobility platform) has adopted, announced support for, or been listed as a partner in the Agent2Agent (A2A) protocol. The confirmed launch partners include Atlassian, Box, Cohere, Intuit, LangChain, MongoDB, PayPal, Salesforce, SAP, ServiceNow, UKG, and Workday — all enterprise software vendors, not consumer mobility platforms. Searches combining bolt.eu with A2A and Agent2Agent returned no relevant results for this vendor.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
No evidence of bolt.eu participation in AP2 (Agent Payments Protocol) was found in any launch partner lists or announcements. The 60+ named AP2 launch partners include Mastercard, American Express, PayPal, Revolut, Adyen, Coinbase, Etsy, Worldpay, and Salesforce — bolt.eu does not appear among them. No bolt.eu-specific AP2 documentation, integration, or public statement was identified.
All MCP-related search results for 'bolt' and 'Model Context Protocol' resolve to unrelated entities: bolt.new (StackBlitz AI app builder), BoltAI (a macOS AI client), boltic.io (a workflow automation platform), and Bolt IoT — none of which are bolt.eu (the European mobility/ride-hailing company). The bolt.eu developer portal at developer.bolt.eu surfaces only standard REST API documentation with no mention of MCP. No vendor-specific evidence of an MCP server, connector, or client role was found for bolt.eu.
No evidence that bolt.eu (the ride-hailing/mobility platform) is among the launch partners or early adopters of MPP. The confirmed Tempo ecosystem launch partners include Anthropic, DoorDash, Mastercard, Nubank, OpenAI, Ramp, Revolut, Shopify, and Standard Chartered — bolt.eu is not named in any MPP announcement, partner list, or integration registry found. The search result for 'partnerpayments.bolt.eu' returned a JavaScript-gated app with no accessible content, but that subdomain concerns Bolt's own affiliate/partner payout tooling, not MPP adoption.
No evidence that bolt.eu has implemented NLWeb or any /ask or /mcp endpoints associated with the protocol. Named launch partners at Microsoft's Build 2025 NLWeb announcement were TripAdvisor, Shopify, Eventbrite, Hearst, and O'Reilly — none are mobility/ride-hailing vendors, and bolt.eu does not appear in any NLWeb partner list or adoption coverage. bolt.eu's developer surface (developer.bolt.eu) is a conventional REST API portal with no NLWeb indicators found.
No evidence found that bolt.eu (the European ride-sharing and mobility platform) has adopted or announced support for the Universal Commerce Protocol. Named UCP co-developers and early partners include Shopify, Google, Etsy, Wayfair, Target, and Walmart — bolt.eu does not appear among them. The 'Bolt' entity referenced in Stripe's UCP/agentic commerce partner list refers to bolt.com (a US-based checkout technology company), not bolt.eu.
No evidence that bolt.eu has implemented or announced support for WebMCP. The protocol is a Google/Microsoft co-developed early-preview W3C draft; known entities active around it include Google Chrome, Microsoft Edge, and Cloudflare (infrastructure). Bolt.eu does not appear in any WebMCP launch partner list, announcement, or developer documentation.
No evidence that bolt.eu (Bolt Technology OÜ, the Estonian ride-hailing and mobility super-app) has adopted or is evaluating the x402 HTTP 402 stablecoin micropayment protocol. Search results for x402 launch partners and adopters surface Coinbase, Cloudflare, Stellar, and eco.com — not Bolt. Bolt's own recent partnership activity is focused on autonomous vehicle collaborations (Stellantis, Pony.ai), with no cryptocurrency payment infrastructure signals found.
No evidence of bolt.eu (Bolt Technology OÜ, the ride-hailing and mobility company) having built or published an app on OpenAI's ChatGPT Apps platform. Searches surfaced unrelated entities (BoltAI, a Mac desktop app; Bolt IoT; bolt.new, an AI app-builder), none of which are bolt.eu. Bolt's own developer portal (developer.bolt.eu) focuses on food/store delivery APIs for merchant integrations, with no mention of OpenAI Apps SDK or ChatGPT App platform participation.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
Direct HTTP checks against bolt.eu (the Estonian mobility/ride-hailing company) for /llms.txt, /AGENTS.md, /.well-known/agent, and /.well-known/ai-plugin.json all failed due to DNS resolution timeout in the research environment — the domain was unreachable, making direct path verification impossible. Web searches returned no indexed evidence of bolt.eu publishing any self-declaration discovery files; all results referencing 'Bolt' alongside these conventions pointed to bolt.new (a separate AI coding platform), not bolt.eu.
Summary
Has agent interface: false
Monitor bolt.eu developer portal (developer.bolt.eu) for any MCP, A2A, or agentic protocol announcements; no current agent-callable interface exists to pursue. If an integration is needed, initiate a formal partnership inquiry via Bolt's business/developer channels rather than automated access.
AgentContext
Verified discrepancies
Vendor claim: Bolt's own Terms for Riders state that Bolt processes in-app payments, handles payment disputes, and will resolve Bolt in-App Payment complaints — creating a strong implication that Bolt is the consumer's transactional counterparty.
What actually happens: Bolt's Terms for Riders simultaneously state that Bolt 'does not provide transport services,' that the transport contract exists solely between the passenger and the driver, and that 'disputes arising from consumer rights, legal obligations or from law applicable to the provision of transport services will be resolved between the passengers and drivers.' Bolt collects payment but disclaims responsibility for the service itself, leaving consumers uncertain whether to pursue a refund or service dispute against Bolt or the driver.
Agent guidance: When completing a ride-booking transaction on Bolt, do not assume Bolt is the merchant of record for the transport service. For any post-ride dispute about the journey itself (overcharge, route, service quality), the legal counterparty is the individual driver, not Bolt. Only in-app payment processing failures should be directed to Bolt support. An agent handling a refund request should distinguish whether the issue is a payment-processing failure (Bolt's remit) or a service-quality complaint (driver's remit) before initiating a dispute or chargeback, since misrouting could result in no resolution.
Human handoff required for
Escalate to a human when a post-ride refund or dispute request arises and it is unclear whether the issue is a payment-processing failure (Bolt's remit) versus a service-quality or consumer-rights complaint (the individual driver's remit), because Bolt's Terms for Riders simultaneously position Bolt as the payment collector and disclaim all responsibility for the transport contract, leaving no single accountable counterparty for combined payment-plus-service disputes.
Escalate to a human when a passenger has been charged an amount that differs from the in-app estimate and the discrepancy cannot be clearly attributed to disclosed surge pricing, because the split between Bolt (payment processor) and the driver (service provider) means neither party unambiguously owns the obligation to correct an unexplained overcharge, and misrouting a chargeback request could result in no resolution.
Five categories were checked for bolt.eu: (1) discrepancy_pricing — searches returned Bolt's own surge-pricing disclosures and consumer review aggregates but no regulatory enforcement or verified hidden-fee finding; (2) discrepancy_availability — searches returned no evidence of ghost inventory, bait-and-switch fares, or undeliverable displayed prices, with the disclosed Flex bidding feature being the only notable item; (3) discrepancy_identity — a confirmed finding was identified based on Bolt's own published Terms for Riders, which simultaneously position Bolt as the in-app payment handler and disclaim responsibility for the transport service contract, creating a verified merchant-of-record ambiguity; (4) discrepancy_policy — searches returned only Bolt's own help pages on cancellation and refunds with no independent regulatory or court-filing evidence of a policy-versus-enforcement gap; (5) discrepancy_undisclosed_constraint — searches returned Bolt support pages, a UK Parliament submission, and general company history but no documented hidden booking limitations or undisclosed mid-transaction constraints. No scan was blocked or missing; all five categories returned accessible results, though categories 1, 2, 4, and 5 produced no findings meeting the inclusion bar.