/vendor/alamo/AgentRouting.json or
/vendor/alamo/AgentContext.json directly.
alamo.com
Overview
Does alamo.com support MCP?
No confirmed MCP support was found for alamo.com as of 2026-06-28.
What agentic protocols does alamo.com support?
No confirmed agentic protocol support was found for alamo.com as of 2026-06-28.
Is alamo.com's API publicly accessible or partner-gated?
Access tier information is not available for alamo.com.
Does alamo.com explicitly prohibit automated access?
Yes. alamo.com's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is alamo.com agent-ready?
Not currently. No confirmed agent-callable interface was found for alamo.com as of 2026-06-28.
Protocols
No evidence that Alamo (alamo.com) or its parent Enterprise Holdings has any involvement with the Agent2Agent (A2A) protocol. Known A2A founding/launch partners include ServiceNow, Microsoft, IBM, and similar enterprise software vendors — no car rental or consumer travel operators appeared in either launch partner list or protocol ecosystem documentation. The alamo.com result surfaced only their loyalty partner rewards page, which is unrelated to A2A.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
No evidence found that Alamo (alamo.com) is a launch partner, named adopter, or pilot participant in the Agent Payments Protocol (AP2). Named parties surfaced in AP2 launch materials include Coinbase and various payments/technology companies — none are Alamo or its parent Enterprise Holdings. Car rental as a vertical has not appeared in any AP2 adoption documentation found.
No evidence of Alamo (alamo.com, an Enterprise Holdings brand) offering or supporting a Model Context Protocol server or integration. Third-party XML aggregators (travelopro.com, trawex.com, pratra.com) offer their own Alamo inventory wrappers but these are not Alamo's own developer surface. A generic third-party car-hire MCP actor exists on Apify but is unaffiliated with Alamo directly. No official Alamo developer portal or MCP-adjacent documentation was found.
No evidence that Alamo (alamo.com, the car rental brand operated by Enterprise Holdings) has any involvement with the Machine Payments Protocol. Named MPP launch partners per Stripe/Tempo's own announcements include Anthropic, DoorDash, Mastercard, Nubank, OpenAI, Ramp, Revolut, Shopify, Standard Chartered, and Visa — Alamo is absent from all published partner lists and from any MPP-related search results.
No evidence found that alamo.com has implemented NLWeb. Searches returned only alamo.com's partner rewards and loyalty pages, and general Microsoft NLWeb launch coverage naming no car rental vendors. Named NLWeb launch partners found in coverage include travel-adjacent but non-Alamo entities; Alamo (an Enterprise Holdings brand) is absent from any NLWeb partner lists. Not confirmed_absent because no Alamo-specific deprecation or denial statement was found.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
No evidence found that alamo.com has implemented or announced WebMCP support. WebMCP (a browser-layer agent protocol driven by Google and Microsoft, accepted by W3C in September 2025) is discussed in travel-industry context by vendors like Mirai but no car rental brands — including Alamo — appear in any known launch partner lists or industry coverage. Alamo is part of the Enterprise Holdings family, and none of its brands appear in available WebMCP adoption materials.
No evidence that alamo.com (Alamo Rent A Car) has adopted or is listed as a launch partner for the x402 stablecoin micropayment protocol. Known adopters and foundation members include Coinbase, Cloudflare, Amazon Bedrock (AgentCore), Google (AP2), Stellar, and Eco.com — all technology infrastructure providers, not consumer-facing car rental or travel brands. No vendor-specific statement, deprecation notice, or integration exists for Alamo that would support any status other than not_found.
No evidence found of an Alamo (alamo.com) app built for the OpenAI ChatGPT Apps platform. Searches surfaced Turo as a confirmed car rental company with a ChatGPT app, and a community forum post about a third-party developer building a generic rental car search app using the Apps SDK — neither is affiliated with Alamo. Alamo's own web presence shows no mention of OpenAI Apps SDK integration.
No vendor-published proprietary API documentation or developer portal was found for alamo.com or its parent Enterprise Holdings. The alamo.com/en/partners.html page covers only loyalty rewards partnerships (airlines, hotels), not technical integrations. Multiple third-party travel-tech aggregators (Trawex, Travelopro, Pratra) claim to offer 'Alamo API' XML connectivity, but these appear to be intermediary aggregation services rather than evidence of a direct, Alamo-owned API surface. No confirmed_absent designation is applied because Alamo has not itself issued a statement ruling out a proprietary direct-connect interface — the documentation simply could not be found.
Direct HTTP requests to alamo.com timed out with connection errors (HTTP 000) across all attempted paths including /llms.txt, /AGENTS.md, /.well-known/agent, and /.well-known/ai-plugin.json — the domain appears to block automated/curl requests from this environment entirely. A targeted web search for alamo.com alongside these file names returned no results referencing alamo.com specifically, only general industry articles. No vendor-specific evidence of any self-declaration file was found, but the domain's inaccessibility to automated checks prevents confirming absence.
Summary
Has agent interface: false
Monitor Alamo (alamo.com) and parent Enterprise Holdings for any future developer portal launch, direct API documentation, or agentic protocol adoption; no actionable integration surface exists today. If integration is needed, evaluate third-party travel-tech aggregators (e.g., Trawex, Travelopro) that claim Alamo inventory connectivity, with the understanding these are intermediary services not Alamo's own surface.
AgentContext
Five discrepancy categories were checked for alamo.com: (1) pricing — searches found Alamo's own fee disclosure pages and an unrelated 2017 class action, but no regulatory enforcement or verified evidence of a gap between advertised and checkout prices; (2) availability — anecdotal consumer-forum complaints about vehicles not being available at pickup were found, but no independent regulatory action or court finding confirming a systematic platform-level availability discrepancy; (3) identity — no evidence was found that Alamo deflects merchant-of-record or payment responsibility to undisclosed third parties; Alamo, operated by Enterprise Holdings, appears to transact directly on alamo.com; (4) policy — Alamo's own cancellation and refund FAQ pages were found, along with third-party summaries, but no regulatory or court-verified gap between stated and enforced policy was identified; (5) undisclosed constraints — Alamo's own FAQ documents some restrictions, and one unverifiable aggregator source mentioned a new per-day service fee introduced in Q3 2025, but no credible independent source confirmed a material hidden constraint. All five categories were scanned; none produced findings meeting the evidentiary threshold for a handoff trigger.