/vendor/blablacar/AgentRouting.json or
/vendor/blablacar/AgentContext.json directly.
blablacar.com
Overview
Does blablacar.com support MCP?
No confirmed MCP support was found for blablacar.com as of 2026-07-01.
What agentic protocols does blablacar.com support?
As of 2026-07-01, blablacar.com has confirmed support for proprietary.
Is blablacar.com's API publicly accessible or partner-gated?
Access varies by protocol: open, partner only.
Does blablacar.com explicitly prohibit automated access?
Yes. blablacar.com's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is blablacar.com agent-ready?
Partial. blablacar.com supports some agentic workflows but requires a human handoff for certain operations — see the protocols and summary sections for details.
Protocols
No evidence that BlaBlaCar appears in any A2A launch partner list or has adopted the Agent2Agent protocol. The confirmed A2A launch partners (50+ at April 2025, 150+ by April 2026) include technology and enterprise firms such as Atlassian, Box, Cohere, PayPal, Salesforce, SAP, and ServiceNow — none in the consumer rideshare/carpooling segment. No BlaBlaCar-specific A2A documentation, announcement, or integration was found.
No evidence that BlaBlaCar has implemented or announced support for the Agentic Commerce Protocol. Known ACP launch partners include URBN (Anthropologie, Free People, Urban Outfitters), Coach, Kate Spade, Revolve, and Ashley Furniture — all retail merchants, not ride-sharing or carpooling platforms. BlaBlaCar's business model (P2P long-distance carpooling) does not map naturally to the retail checkout flow ACP is designed for.
No evidence that BlaBlaCar is among the 60+ named AP2 launch partners. Named partners in the public record include Mastercard, PayPal, American Express, Adyen, Coinbase, Salesforce, ServiceNow, Etsy, Lowe's, Worldpay, and Lightspark — all payments processors, enterprise software, or e-commerce merchants; no ride-sharing or mobility vendors appear. BlaBlaCar has issued no AP2 announcement of its own.
No evidence of a BlaBlaCar-published or BlaBlaCar-endorsed MCP server was found across searches covering blablacar.com's developer documentation, GitHub organization, and MCP ecosystem listings. BlaBlaCar exposes REST APIs for trip search (Search V3) and bus fares, but no MCP layer has been published or announced. The only BlaBlaCar AI-adjacent finding was an internal data-analysis tooling blog post unrelated to MCP.
No evidence found that BlaBlaCar participates in or has adopted MPP (the Stripe + Tempo multi-rail machine payment settlement protocol). Search results for MPP launch partners reference the Tempo and xpay.sh documentation ecosystems, with no mention of BlaBlaCar. BlaBlaCar's own payment documentation covers standard consumer rails (PayPal, card, Apple Pay, Google Pay) with no indication of MPP integration.
No evidence that BlaBlaCar has implemented or been named as an NLWeb adopter. Microsoft's confirmed launch cohort includes Tripadvisor, Shopify, Eventbrite, Hearst, O'Reilly Media, Qdrant, and Chicago Public Media — none of which is BlaBlaCar. BlaBlaCar's own newsroom and developer-facing surfaces show no reference to NLWeb, /ask, or /mcp endpoints.
No evidence found that BlaBlaCar has adopted, announced, or integrated with the Universal Commerce Protocol (UCP). UCP's confirmed adopters include retail merchants such as Nike, Target, Walmart, Wayfair, Etsy, and Shopify merchants — none of these searches surfaced BlaBlaCar. BlaBlaCar is a ridesharing/carpooling marketplace, not a retail merchant, and its core booking flow falls outside the retail checkout discovery use case UCP is designed for.
No evidence that BlaBlaCar has implemented or announced WebMCP support. The protocol is in early preview (Chrome 146, flagged), with ecommerce-oriented early adopters (Shopify, Etsy, Wayfair, Stripe, HubSpot) visible in coverage — BlaBlaCar appears in none of this context. BlaBlaCar exposes a Bus API for B2B partners but no browser-layer agent tooling surface was found.
No evidence found that BlaBlaCar has adopted or evaluated x402. The protocol's confirmed launch partners and early adopters include Coinbase, Cloudflare (co-founding the x402 Foundation), Google (A2A/AP2 integration), and various AI/developer tooling projects — none in the rideshare or carpooling segment. BlaBlaCar has not appeared in any x402 partner announcement, demo day listing, or Bazaar index entry.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
Carpooling trip search and ride data retrieval (read-only); covers trip listings, seat availability, and passenger info via REST at https://public-api.blablacar.com/api/v3
BlaBlaCar operates a documented public REST API (v3) for carpooling trip search at https://public-api.blablacar.com/api/v3, documented at https://support.blablacar.com/hc/en-gb/categories/360002585239-Developer-BlaBlaCar-API. Access requires requesting an API key via a form, after which credentials are emailed with an initial quota of 1,000 queries/day; higher quotas require additional contact. This is a search/read API and does not expose booking or supply-side management.
Bus/coach inventory distribution: route search, seat availability, booking creation, ticket management, and passenger notifications for BlaBlaCar Bus (formerly BlaBlaBus) European coach services
BlaBlaCar operates a separate REST Bus API (v3) at https://bus-api.blablacar.com, documented at https://bus-api.blablacar.com. It targets transport operators, OTAs, and travel aggregators. Access requires signing up to receive an API key; third-party reports indicate access is not trivially self-serve and may require business engagement. This API is entirely distinct from the carpooling API in both endpoint domain and service scope.
Direct HTTP checks for blablacar.com (llms.txt, AGENTS.md, /.well-known/agent, /.well-known/ai-plugin.json) all timed out at the DNS resolution stage, indicating the sandbox has no network route to blablacar.com. Web searches returned no third-party evidence of BlaBlaCar publishing any self-declaration files at predictable domain paths. Network access was blocked, making actual examination of the paths impossible; this is unable_to_verify rather than not_found.
Summary
Has agent interface: partial
Confirm whether the carpooling REST API (public-api.blablacar.com/api/v3) supports sufficient trip search depth for agent use cases, then evaluate whether the partner-only Bus API access tier requires a formal business relationship or allows self-serve enrollment — both APIs are read/search-oriented with no confirmed booking capability on the carpooling side.
AgentContext
Verified discrepancies
Vendor claim: BlaBlaCar presents carpooling seats as available and bookable at displayed prices. The platform allows passengers to 'secure your seat by paying directly through the platform' and implies that listed rides with available seats can be confirmed through a standard booking flow.
What actually happens: A significant portion of BlaBlaCar carpooling listings operate under a 'manual approval' model where the driver must accept each request before the booking is confirmed. An agent or user who pays for a seat may have their booking request expire without driver response, leaving them without confirmed transport while their funds are temporarily held by the platform. BlaBlaCar's own customer support responses publicly acknowledge that 'booking request expire' and funds are 'temporarily held while arranging alternative travel' — confirming this is a systemic platform characteristic, not an edge case.
Agent guidance: Before initiating a carpooling booking on BlaBlaCar, an agent must check whether the specific listing offers 'Instant Booking' or requires manual driver approval. If only manual approval rides are available for the required route and time, the agent should not treat the booking as confirmed until an explicit driver acceptance notification is received. The agent should also surface to the user that funds may be temporarily held even if the request is ultimately declined or expires, and should avoid booking manual-approval rides when the user has a hard travel deadline.
- BlaBlaCar's own Trustpilot support responses acknowledge the recurring pattern of booking requests expiring without driver action and funds being temporarily held, confirming this is a known platform-level behavior.
- A 2025 travel guide explains BlaBlaCar's dual booking model: drivers can 'choose to manually approve each request or enable Instant Booking for a faster process,' meaning displayed seats are not always immediately confirmable.
Human handoff required for
Escalate to a human when a BlaBlaCar carpooling booking has been submitted and payment processed but the driver has not yet accepted the request — the agent must not report the task as complete or treat the seat as confirmed until an explicit driver-acceptance notification is received, because the booking may expire without confirmation while the user's funds remain temporarily held
- BlaBlaCar customer support responses publicly acknowledge that booking requests can expire and that passenger funds are temporarily held during this period, meaning a paid-for seat may never convert to a confirmed ride.
- BlaBlaCar's platform distinguishes between 'Instant Booking' and manual driver-approval listings, and the booking flow allows payment submission before driver acceptance is confirmed, creating a gap between payment and confirmed transport.
Escalate to a human when only manual-approval carpooling rides are available for a route where the user has a hard travel deadline — the agent must not proceed with booking because the driver-acceptance window may expire without confirmation, leaving the user without transport and with temporarily held funds at a critical time
Five categories were assessed for BlaBlaCar (blablacar.com): (1) Pricing discrepancies — no finding; BlaBlaCar publicly documents its 16–20% service fee structure and displays it during checkout, with no regulatory actions or verified complaints indicating a gap between displayed and charged prices. (2) Availability discrepancies — finding present; a structural platform issue was confirmed whereby many carpooling listings require manual driver approval rather than instant confirmation, meaning a submitted, paid booking may expire without converting to a confirmed seat while funds are temporarily held. (3) Identity/merchant-of-record — no finding; BlaBlaCar openly discloses in its Terms and Conditions that it acts as an intermediary rather than a party to the transport contract, so no deceptive counterparty ambiguity was found. (4) Policy enforcement discrepancies — no finding; BlaBlaCar documents a structured cancellation and refund policy, and while one secondary source noted inconsistency in BlaBlaCar Bus operator terms, no primary sources confirmed systematic policy misrepresentation. (5) Undisclosed constraints — no finding; consumer complaints about driver no-shows and account suspensions were noted but did not constitute systematic undisclosed material booking constraints. No search scans were blocked or missing across the five categories.