/vendor/bird/AgentRouting.json or
/vendor/bird/AgentContext.json directly.
bird.co
Overview
Does bird.co support MCP?
No confirmed MCP support was found for bird.co as of 2026-07-01.
What agentic protocols does bird.co support?
No confirmed agentic protocol support was found for bird.co as of 2026-07-01.
Is bird.co's API publicly accessible or partner-gated?
Access tier information is not available for bird.co.
Does bird.co explicitly prohibit automated access?
Yes. bird.co's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is bird.co agent-ready?
Not currently. No confirmed agent-callable interface was found for bird.co as of 2026-07-01.
Protocols
No evidence that bird.co (micromobility/e-scooter operator) has any involvement with the Agent2Agent protocol. The A2A launch partner list of 50+ organizations includes enterprise technology vendors such as Atlassian, Box, Salesforce, SAP, PayPal, and Workday — none of which is bird.co, and no subsequent announcement or documentation links bird.co to A2A adoption. Confirmed not_found rather than unable_to_verify because the relevant partner lists and public A2A documentation were directly examined.
No evidence found that Bird (bird.co), the electric scooter/micromobility company, appears in any ACP launch partner list or has adopted the Agentic Commerce Protocol. ACP launch partners identified in search results are e-commerce and retail-oriented merchants enabled via Stripe; Bird operates in transportation/mobility and was not among them. No vendor-specific statement, integration announcement, or documentation referencing ACP was found for bird.co.
No evidence that Bird (bird.co), the electric micromobility company, appears in any AP2 launch partner list or endorsement announcement. The 60+ named AP2 launch partners include payment networks (Mastercard, Adyen, American Express, Worldpay), fintechs (PayPal, Revolut, Coinbase), and merchants (Etsy, Lowe's) — Bird is absent from all published partner lists. No Bird-specific AP2 documentation, implementation, or commitment was found.
Searches across bird.co's platform and developer surfaces found no evidence of a vendor-published or vendor-endorsed MCP server. The only MCP-related result involving bird-related data was a third-party GitHub project (moonbirdai/ebird-mcp-server) wrapping the eBird ornithology API — entirely unrelated to bird.co's scooter/micromobility platform. Bird.co's own documented API surface consists of informal reverse-engineered endpoints and a separate messaging-platform API (docs.bird.com) with no MCP integration announced.
No evidence that Bird (bird.co), the e-scooter micromobility operator, appears among MPP launch partners or has any documented integration with the Stripe + Tempo multi-rail machine payment settlement protocol. MPP's known early adopters include API-economy and developer-tooling services listed on mpp.dev; Bird's payment news concerns PayPal integration and a legacy 'Bird Pay' pilot, neither of which is related to MPP. Choosing not_found rather than confirmed_absent because no Bird-specific statement or deprecation notice was located — simply no evidence of participation.
Named NLWeb early partners confirmed from Microsoft's Build 2025 launch include Chicago Public Media, Hearst, Shopify, TripAdvisor, Eventbrite, O'Reilly, and Yoast — bird.co (Blue Jay Transit, Inc., a micromobility/e-scooter operator) does not appear in any NLWeb partner list or announcement. No evidence of /ask or /mcp endpoints at bird.co was found. No vendor-specific statement or implementation from bird.co regarding NLWeb was discovered.
Bird (bird.co) is a micromobility company (electric scooters/e-bikes) and does not appear in any UCP-related announcements, partner lists, or documentation. The UCP launch partners named by Google and Shopify include retail merchants such as Walmart, Target, Nike, Sephora, Fenty, Steve Madden, and Wayfair — none of which are Bird. No evidence was found of Bird implementing or announcing any intent to implement UCP. This is a not_found rather than confirmed_absent because no vendor-specific statement from Bird addresses UCP.
No evidence that bird.co (shared electric scooter/e-bike platform) has implemented or announced WebMCP support. WebMCP is a nascent browser-layer protocol driven by Google and Microsoft; known adopters are generic web app demonstrators (e.g., a demo booking app called 'AirBird') rather than established consumer travel or micromobility vendors. Bird's developer-facing surface focuses on city-operator APIs and a consumer mobile app, neither of which aligns with the browser-session model WebMCP targets.
No evidence that Bird (bird.co), a shared electric scooter and e-bike operator, has any involvement with the x402 protocol. The confirmed Coinbase x402 launch partners include BuffetPay, Cal.com, Cred Protocol, Fewsats, and Exa — all API/AI-adjacent services, not consumer micromobility operators. Bird's own site shows no mention of x402, stablecoin payments, or HTTP 402 integration. Bird is a micromobility company with no apparent developer payment protocol surface relevant to x402.
No evidence of a ChatGPT Apps SDK integration for bird.co (Bird scooters/micromobility). The only OpenAI-related finding for the broader Bird brand space is bird.com (a separate CRM/communications platform) consuming OpenAI APIs within its own internal workflow automation — this is outbound API usage, not a published ChatGPT App. The scooter-focused bird.co entity shows no ChatGPT App presence in any searched source.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
bird.co (Bird electric scooters) shows no evidence in web search results of publishing llms.txt, agents.md, or /.well-known/agent discovery files. Note: docs.bird.com references to llms.txt found in search results belong to a distinct company (bird.com / MessageBird), not bird.co. Direct HTTP probing of bird.co from the research environment was blocked by network restrictions, so the absence of a fetch-based result reflects infrastructure constraints rather than a confirmed negative — hence unable_to_verify rather than not_found.
Summary
Has agent interface: false
No confirmed agent-callable interface exists for bird.co across any of the nine protocols researched. Recommended action is to park this vendor as low priority and re-evaluate only if Bird (Blue Jay Transit, Inc.) launches a public developer API or announces participation in any agentic commerce or AI agent protocol. Monitor bird.co developer or press channels for API announcements.
AgentContext
Five discrepancy categories were checked for bird.co: (1) pricing — searches found consumer complaints about charges for failed rides and general opacity concerns, but no verified regulatory action or documented structural hidden-fee mechanism; (2) availability — searches found complaints about scooters failing to unlock or stopping mid-ride, reflecting hardware reliability rather than advertised-vs-actual inventory discrepancies; (3) identity — searches found no evidence of a franchisee or third-party operator structure that would create merchant-of-record ambiguity or deflect dispute responsibility away from Bird; (4) policy — searches surfaced BBB and Trustpilot complaints about inconsistent refund handling, but no independently verified gap between Bird's published policies and a defined enforcement practice; (5) undisclosed constraints — searches confirmed Bird uses geofencing that can halt rides at boundaries, but found this is disclosed in Bird's rental agreement and municipal filings rather than concealed. All five categories returned no finding meeting the inclusion bar, and no handoff triggers are warranted. Coverage was substantive across all categories; no scans were blocked or missing, though absence of regulatory enforcement history limits definitive conclusions on billing-dispute consistency.