/vendor/delta/AgentRouting.json or
/vendor/delta/AgentContext.json directly.
delta.com
Overview
Does delta.com support MCP?
No confirmed MCP support was found for delta.com as of 2026-06-24.
What agentic protocols does delta.com support?
As of 2026-06-24, delta.com has confirmed support for proprietary.
Is delta.com's API publicly accessible or partner-gated?
Access varies by protocol: platform mediated, partner only.
Does delta.com explicitly prohibit automated access?
Yes. delta.com's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is delta.com agent-ready?
Partial. delta.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 that Delta Air Lines (delta.com) has adopted, announced, or implemented the Agent2Agent (A2A) protocol. Searches across Delta's news hub, developer resources, and third-party coverage found no mentions of A2A, agent cards, or agent-to-agent interoperability from Delta. Delta's AI activity is focused on its internal Delta Concierge product (a customer-facing AI assistant launched in beta early 2026) with no indication of an externally callable A2A-compliant agent surface. Named A2A launch partners include Google, Microsoft, AWS, Salesforce, SAP, ServiceNow, Workday, and IBM (150+ as of April 2026); Delta is not among them.
No evidence found that Delta Air Lines (delta.com) has implemented or announced ACP (Agentic Commerce Protocol). Named ACP launch partners for product discovery include Target, Sephora, Nordstrom, Lowe's, Best Buy, The Home Depot, and Wayfair; Delta is not among them. Confirmed initial Instant Checkout partners included Etsy and a small set of US retailers; Delta is not listed. Delta's AI activity is focused on its own Delta Concierge assistant and internal AI pricing tools — no vendor-specific statement, integration announcement, or documentation referencing ACP was located, so this is recorded as not_found rather than confirmed_absent.
No evidence found that Delta Air Lines (delta.com) has adopted, announced support for, or been named as a partner in the AP2 (Agent Payments Protocol). Named launch partners at AP2's September 2025 announcement include Mastercard, American Express, Adyen, PayPal, Coinbase, Revolut, Worldpay, JCB, Salesforce, ServiceNow, Etsy, Forter, Intuit, Ant International, and Mysten Labs; travel-segment partners cited by third parties include Amadeus, Booking.com, and Trip.com — Delta is not among them. Delta's public AI announcements concern Delta Concierge (a consumer-facing AI assistant) and AI-driven pricing (Fetcherr partnership), with no reference to AP2 or cryptographic payment mandates. Recorded as not_found rather than confirmed_absent because no vendor-specific statement from Delta disclaiming or deprecating AP2 was located.
No official MCP server from Delta Air Lines (delta.com) was found. The only Delta-branded MCP server located is an unofficial, community-built tool (github.com/markswendsen-code/mcp-delta, listed on Glama) that uses Playwright browser automation to scrape delta.com — it is not a sanctioned Delta API surface and is not vendor-issued. Delta's developer portal at apiportal.delta.com shows no MCP tooling. Industry coverage of travel MCP adopters (AltexSoft, Thoughtworks) names Kiwi.com and Sabre as 2025 MCP leaders; Delta is not among them. No vendor-specific statement, deprecation notice, or official announcement was located, so this is recorded as not_found rather than confirmed_absent.
No evidence found that delta.com (Delta Air Lines) has implemented, piloted, or announced MPP support. MPP launched March 18, 2026, co-authored by Stripe and Tempo; named launch and design partners are Anthropic, DoorDash, Mastercard, Nubank, OpenAI, Ramp, Revolut, Shopify, Standard Chartered, Visa, Deutsche Bank, and Lightspark — Delta is not among them. Delta's publicly visible payment surfaces are all human-checkout oriented (Affirm, Sezzle, Zip, credit cards); no delta.com developer documentation references MPP or HTTP 402 machine payment flows.
No evidence found that delta.com has implemented NLWeb. Multiple searches across NLWeb launch and partner contexts returned no mention of Delta Air Lines or delta.com. Named early adopters/partners identified in public NLWeb announcements include Condé Nast, Redfin, Eventbrite, Priceline, and TripAdvisor — delta.com is not among them. Direct endpoint probes of delta.com/ask and delta.com/mcp were blocked by the sandbox's lack of network access (not a delta.com-specific block), so direct confirmation of absence is not possible; status is recorded as not_found rather than confirmed_absent because no vendor-specific statement or deprecation notice was located.
No evidence that Delta Air Lines (delta.com) has adopted or endorsed UCP. Named UCP launch co-developers are Shopify, Etsy, Wayfair, Target, and Walmart; the 60+ endorsing partners span payment networks (Visa, Mastercard, Amex, Stripe, Adyen), retailers (Best Buy, Macy's, Home Depot, Zalando), and hospitality brands (Booking.com, Expedia Group, Hilton, Marriott, IHG, Accor, Amadeus, Choice Hotels, Trip.com, Wyndham) — Delta is not among them. UCP's travel expansion (announced Google I/O May 2026) targets hotel booking, not airline ticketing; industry commentary notes that airlines remain a future opportunity, not a current UCP vertical. Recorded as not_found rather than confirmed_absent because no Delta-specific statement declining or deprecating UCP was located.
No evidence found of delta.com implementing WebMCP. The webmcp.cool live directory of sites exposing WebMCP tools does not list delta.com. The Google ChromeLabs travel flight-search WebMCP demo (googlechromelabs.github.io/webmcp-tools/demos/react-flightsearch/) is a generic reference implementation, not affiliated with delta.com. PhocusWire coverage of WebMCP in travel contexts names no specific airline adopters; it discusses the protocol as an opportunity for the sector generally. The only Delta-adjacent MCP artifact found is a third-party Playwright-based automation wrapper on Glama (not WebMCP). No vendor-specific statement, deprecation notice, or implementation evidence was located.
No evidence that Delta Air Lines (delta.com) has implemented or adopted x402. The x402 Foundation's named founding members include Coinbase, Cloudflare, Stripe, Google, AWS, Microsoft, Visa, Mastercard, American Express, Adyen, Circle, Shopify, KakaoPay, Polygon Labs, Solana Foundation, and Fiserv — Delta is not among them. No Delta developer documentation, press release, or third-party report references x402 adoption. Delta's public API/developer surface is travel-focused (booking, check-in, loyalty) with no known crypto/stablecoin payment integration. Recorded as not_found rather than confirmed_absent because no vendor-specific statement of non-adoption was located.
No evidence found of Delta Air Lines (delta.com) building or listing an app on the OpenAI ChatGPT Apps platform. The platform launched at OpenAI DevDay in October 2025 with named travel pilot partners including Expedia, Booking.com, Tripadvisor, Skyscanner, Uber, TheFork, Almosafer, Accor, Lighthouse, DirectBooker, and eDreams; Delta is not among them. Delta's own AI investment (Delta Concierge, Fetcherr pricing AI) is internal and proprietary with no documented OpenAI Apps SDK integration. Three community-built "Delta" GPTs exist on chatgpt.com but are not official Delta Air Lines products. No vendor-specific Delta statement or deprecation notice regarding this protocol was located, so this is recorded as not_found rather than confirmed_absent.
Passenger-side flight search, flight offers retrieval, and customer journey management for travel industry integrators. Specific endpoint capabilities cover searching available flights and fares and managing the customer travel lifecycle; full scope is not publicly documented without registration.
Delta Air Lines operates a developer portal at apiportal.delta.com with an API catalogue (apiportal.delta.com/apis and apiportal.delta.com/publish also resolve). Multiple secondary sources consistently describe the suite as covering flight search, flight offers, and customer journey management. Access requires signing up on the portal and registering an application before detailed documentation is available; the portal content itself was not retrievable without credentials, so auth type and full endpoint inventory could not be confirmed. Recorded as confirmed_present because the portal's existence is independently corroborated across multiple sources, but access_tier is platform_mediated and sketchiness_rating is insufficient_data due to the gated check.
Cargo-side freight shipping integration: search available flights and current rates with capacity/product/station validation (shopping); create and manage cargo bookings with real-time status updates (booking); receive real-time shipment tracking including GPS positioning and DASH Door-to-Door details (tracking).
Delta Cargo's proprietary REST API is documented at deltacargo.com/Cargo/catalog/delta-cargo-api and in a publicly accessible API Toolkit PDF (https://www.deltacargo.com/content/dam/cargo/images/pdf/API-Toolkit.pdf, dated February 2021). Access requires submitting an API request form; Delta Cargo then issues client credentials for a testing phase, after which production credentials are granted. Free to use with no setup or transaction fees. Target audience is freight forwarders and cargo customers, distinct from Delta's passenger-side API. Endpoint docs page is publicly reachable and confirmed vendor-owned; sketchiness_rating is clean based on HTTPS, domain alignment (deltacargo.com), and consistent official documentation.
No evidence found of delta.com publishing any self-declaration files (llms.txt, AGENTS.md, /.well-known/agent, or similar). Direct fetch attempts to www.delta.com were blocked (network unreachable from sandbox — all HTTP responses returned 000), preventing an in-band check of the actual paths. Web searches produced no indexed references to any such file at delta.com; the llmstxt.site directory returned no delta.com entry. Delta Air Lines does publish an AI Terms of Use page (https://www.delta.com/us/en/legal/ai-terms-of-use) indicating active AI product investment, but no agent-facing self-declaration convention file was located. Recorded as not_found rather than unable_to_verify because the domain-level fetch failure is a sandbox network limitation, not a gating/auth barrier on Delta's side — third-party search indexes, which do crawl the public web, also returned zero evidence of such files.
Summary
Has agent interface: partial
Register at apiportal.delta.com to obtain credentials for the passenger-side API (flight search, flight offers, customer journey management). For cargo use cases, submit the API request form at deltacargo.com/Cargo/catalog/delta-cargo-api to obtain client credentials for the cargo REST API covering shopping, booking, and tracking. No standardized agent protocols (MCP, A2A, UCP, etc.) are confirmed present; all agent interaction must go through these proprietary authenticated REST APIs. Do not attempt to scrape delta.com or related properties — automated access is explicitly prohibited by Delta's own published Terms of Use.
AgentContext
Verified discrepancies
Vendor claim: Delta.com displays fares to users during the search and booking flow, allowing them to proceed through seat selection and payment entry at a stated price before the transaction is finalized.
What actually happens: Multiple independently documented reports — including a long-running FlyerTalk thread specifically titled 'Bait and Switch - Delta.com Fares' — confirm that Delta's booking engine can display a fare class (e.g., deep-discount 'U' inventory) that is re-priced to a higher fare class (e.g., 'H') at or near the final checkout step. The system allows users to progress through the entire checkout flow, including entering payment details, before surfacing a higher price or an 'earlier fare no longer available' message. This is a structural behavior tied to how Delta's real-time inventory interacts with its booking engine, not isolated user error.
Agent guidance: An agent booking on delta.com must not treat a fare as confirmed until the final booking confirmation number is issued. At the payment submission step, the agent should explicitly verify that the price shown on the final confirmation screen matches the price displayed during search before proceeding. If a price discrepancy appears at checkout, the agent should abort, re-search, and present the new price to the user for approval rather than completing the booking at the higher rate.
- A dedicated multi-page FlyerTalk thread documents repeated instances where Delta.com quoted fares in deep-discount fare buckets (e.g., U class) that were re-priced at checkout to higher buckets (e.g., H class), with frequent-flyer members confirming this is a recurring engine behavior rather than isolated incidents.
- A ComplaintsBoard.com complaint (marked investigated and resolved) describes a Delta.com session where a fare was displayed, credit card and insurance details were entered, and then a message appeared stating 'The fare quoted earlier is no longer available' immediately before payment processing.
Vendor claim: Delta's published policy (effective October 28, 2024, aligned with DOT rules) states that passengers are entitled to a full refund if their flight is subject to a qualifying significant schedule change — including a departure or arrival shift of 180 minutes or more (domestic) or 360 minutes or more (international), a routing that adds a stop, an airport change, or a flight-number change. Delta's own help pages and customer service plan document these thresholds explicitly.
What actually happens: A March 2025 industry analysis found that Delta's schedule-change refund policy, while formally documented, is structured and applied in a way that functions as if it is designed to be bypassed or ignored in practice. Customers attempting to invoke the stated refund entitlement for qualifying schedule changes frequently encounter obstacles in the claims process. Additionally, Delta maintains a complex two-track eligibility system — different thresholds apply depending on whether a ticket was issued before or after October 28, 2024 — creating conditions under which agents or customers may be told they are ineligible even when their situation qualifies under the current rules.
Agent guidance: When requesting a refund for a schedule change on behalf of a user, do not assume the stated eligibility criteria will be automatically accepted by Delta's system or agents. Explicitly document the qualifying change type and delay duration, note the ticket issuance date (before or after October 28, 2024) to determine the applicable threshold, and if the online refund flow does not surface the option, escalate via phone (800-221-1212) or written complaint rather than accepting a rejection at face value. If a refund is denied for a schedule change that meets the documented thresholds, advise the user to file a DOT complaint at airconsumer.dot.gov as a follow-up step.
- Aviation industry analyst article from March 2025 titled 'Delta's Punitive Schedule Change Policy is Built to be Ignored,' documenting that Delta's formal schedule-change refund policy is structured such that it operates differently in practice from what is stated.
- Delta's own help page shows a dual-threshold system for ticket-date eligibility, with different refund rules for tickets issued before vs. after October 28, 2024, creating a policy that may be misapplied at the point of a refund request.
- Delta's delayed/canceled flight page confirms the post-October 2024 thresholds but retains footnotes about the pre-October 2024 120-minute standard, requiring careful parsing to determine applicable rules.
Human handoff required for
Abort booking and present updated fare to user for approval when the price shown at the final confirmation screen is higher than the price displayed during the search phase — this fare-bucket mismatch occurs structurally in Delta's booking engine and can surface only after payment details have been entered.
Escalate to a human agent when Delta's online refund flow does not surface a refund option for a schedule change that meets the documented qualifying thresholds (domestic: 180+ min shift; international: 360+ min shift; routing additions; airport changes), rather than accepting an automated or agent rejection at face value.
Pause and verify ticket issuance date against the applicable refund threshold set (pre-October 28, 2024 vs. post-October 28, 2024) before accepting any Delta agent or system determination that a schedule-change refund claim is ineligible, as the dual-threshold system creates material risk of incorrect denial.
Five categories were checked for delta.com. Discrepancy_pricing: No finding — searches returned general FTC junk-fees coverage and speculative AI-pricing commentary, but no confirmed regulatory enforcement or documented checkout-price gap against Delta specifically; Delta's DOT-mandated full-fare display requirement appears to be met without identified violations. Discrepancy_availability: Finding present — a structural fare-bucket mismatch in Delta's booking engine is documented in a long-running FlyerTalk thread and corroborating consumer complaints, where a lower fare class shown during search is re-priced to a higher class at the final checkout step. Discrepancy_identity: No finding — Delta's Contract of Carriage and Help Center transparently disclose the merchant-of-record split between Delta and third-party agents; no deceptive counterparty ambiguity was identified. Discrepancy_policy: Finding present — Delta's schedule-change refund policy, while formally documented, is characterized in a March 2025 industry analysis as structured to be bypassed in practice, and a dual-threshold system (pre/post October 28, 2024 ticket issuance) creates material risk of incorrect refund denial. Discrepancy_undisclosed_constraint: No finding — Delta's own FAQ discloses limitations around eCredits and partner-award bookings, and no independently verified hidden constraint causing agent transaction failure was identified; the Companion Certificate fare-class restriction is disclosed in Delta's terms.