/vendor/teladoc/AgentRouting.json or
/vendor/teladoc/AgentContext.json directly.
teladoc.com
Overview
Does teladoc.com support MCP?
No confirmed MCP support was found for teladoc.com as of 2026-07-01.
What agentic protocols does teladoc.com support?
As of 2026-07-01, teladoc.com has confirmed support for proprietary.
Is teladoc.com's API publicly accessible or partner-gated?
Partner only.
Does teladoc.com explicitly prohibit automated access?
Yes. teladoc.com's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is teladoc.com agent-ready?
Partial. teladoc.com supports some agentic workflows but requires a human handoff for certain operations — see the protocols and summary sections for details.
Protocols
Teladoc Health (teladoc.com) does not appear in any A2A launch partner lists. The known inaugural partners include Atlassian, Box, Cohere, Intuit, LangChain, MongoDB, PayPal, Salesforce, SAP, ServiceNow, UKG, and Workday — all outside healthcare/telehealth. No vendor-specific evidence of Teladoc adopting or referencing the Agent2Agent protocol was found.
No evidence found that Teladoc (teladoc.com) participates in the Agentic Commerce Protocol. Known launch partners are retail/fashion brands such as URBN (Anthropologie, Free People, Urban Outfitters), Coach, Kate Spade, Revolve, and Ashley Furniture — all consumer goods merchants, not telehealth platforms. Teladoc's B2B/employer-benefits model does not align with the current ACP commerce/checkout use case.
No evidence that Teladoc (teladoc.com) has any involvement with the Agent Payments Protocol (AP2). Named launch partners and collaborators identified in AP2 documentation include Coinbase, CrossMint, EigenLayer, Ethereum Foundation, Mesh, MetaMask, and Mysten — all payments/web3 entities, none in telehealth. AP2 is still in early specification and ecosystem-building stages, making healthcare vertical adoption extremely unlikely at this time.
No evidence of a Teladoc Health MCP server or MCP integration was found across searches targeting teladoc.com's developer hub (api-documentation.teladochealth.com), GitHub presence (github.com/IntouchHealth), and general queries combining 'Teladoc' with 'Model Context Protocol' or 'MCP.' Results surfaced Teladoc's REST API for virtual care (Solo platform) and a Microsoft AI/ambient documentation partnership, but neither involves MCP. Third-party healthcare MCP servers (e.g., Innovaccer, Cicatriiz) appeared in results but are unrelated to Teladoc. No vendor-specific deprecation notice was found either, so confirmed_absent cannot be applied.
No evidence that Teladoc (teladoc.com) is involved with MPP in any capacity. Named launch partners publicly documented include Anthropic, OpenAI, Shopify, DoorDash, Ramp, Revolut, Nubank, Mastercard, Standard Chartered, and Visa — Teladoc appears in none of these lists. Teladoc is a telehealth platform with no observable overlap with the agent-to-agent payment infrastructure use cases MPP targets.
No evidence that teladoc.com has implemented NLWeb or exposes /ask or /mcp endpoints. The Microsoft NLWeb launch partners page and related coverage name no Teladoc involvement; a Teladoc-Microsoft press release (July 2023) concerns AI collaboration for clinical documentation, not NLWeb. No vendor-specific NLWeb adoption signals found.
Three searches found no evidence that teladoc.com has implemented or announced UCP. Search results returned only UCP-general coverage (Google, Shopify, Walmart, Etsy) and one incidental Teladoc sign-in page with no commerce/checkout context. Teladoc Health is a telehealth platform, not a retail merchant, making UCP adoption theoretically possible (e.g., for prescription or service checkout) but entirely unattested as of this check. Absence of evidence is not a vendor-specific denial, so not_found rather than confirmed_absent is the appropriate classification.
No evidence found of Teladoc (teladoc.com) implementing or planning WebMCP. The protocol is currently in early preview (Chrome 146 Canary, as of mid-2026) with a nascent ecosystem; named demo partners include a hotel chain demo site and CRM-sector early adopters (HubSpot, Salesforce). Teladoc appeared in none of the launch partner lists, EPP announcements, or ecosystem coverage found. Not confirmed_absent because no Teladoc-specific statement or deprecation notice exists — simply no evidence of engagement with this protocol.
No evidence that Teladoc (teladoc.com) is associated with x402 in any capacity. Named x402 launch collaborators include AWS, Anthropic, Circle, NEAR, Cloudflare, and Chainlink — all technology/infrastructure companies; no healthcare or telehealth vendors appear among them. Teladoc operates as a consumer-facing telehealth platform with no identified alignment with stablecoin micropayment infrastructure.
No evidence found of Teladoc Health building or listing an app on OpenAI's ChatGPT Apps platform via the Apps SDK. Teladoc's known AI partnerships involve Microsoft Azure OpenAI Service and Nuance DAX for clinical documentation — not a ChatGPT Apps SDK integration. OpenAI's own ChatGPT Health feature (powered by b.well, not Teladoc) is the closest adjacent surface, and Teladoc does not appear there either.
Partner-facing REST API and Mobile SDK enabling embedding of Teladoc Health telehealth services (general medical, behavioral health, expert opinion) into third-party apps and platforms; documentation is gated behind a credentialed partner account with access granted via email request to a dedicated partner contact
Teladoc Health operates a partner API and Mobile SDK (iOS/Android) documented at https://api-documentation.teladochealth.com/, gated behind a partner program requiring email-based access request. The documentation portal itself is publicly visible at a high level but full reference content requires a credentialed account. No separate consumer-facing or supply-side management API with distinct documented scope was found.
Direct HTTP fetches of teladoc.com/llms.txt, teladoc.com/AGENTS.md, teladoc.com/agents.md, and teladoc.com/.well-known/agent were all blocked by DNS resolution failure in this sandboxed environment, preventing direct verification. Web searches targeting site:teladoc.com for these files returned no results from the teladoc.com domain, and searches for Teladoc-specific agent discovery files yielded no external evidence of any such files being published. The inability to directly fetch the domain means this is borderline unable_to_verify, but the complete absence of any third-party references to these files (which would typically be indexed or cited if present) supports not_found as the more accurate status.
Summary
Has agent interface: partial
Contact Teladoc Health's partner program via the email request process documented at api-documentation.teladochealth.com to obtain credentialed access; once credentials are secured, audit the full partner API and Mobile SDK reference for any agent-callable endpoints, auth parameter specifics, and scope boundaries across service categories (general medical, behavioral health, expert opinion).
AgentContext
Verified discrepancies
Vendor claim: Teladoc Health implies broad availability of virtual care services including diagnosis, treatment, and prescription of medication across the United States, presenting itself as a comprehensive telehealth platform accessible to members.
What actually happens: Teladoc operates subject to state-by-state regulatory constraints that can make the service partially or fully unavailable in certain states, and doctors cannot guarantee a prescription will be written. Additionally, Teladoc will not prescribe any DEA-controlled substances or certain other drug categories — constraints that are not prominently surfaced before a user initiates a visit. Separately, as of January 2025, Teladoc became out-of-network for Florida Blue Medicare and myBlue plans, meaning members of those plans who believe they are covered may discover mid-transaction that the service is not available to them under their plan.
Agent guidance: Before initiating a Teladoc visit on behalf of a user, an agent should: (1) verify the user's state of residence is a supported state; (2) confirm their insurance plan still includes Teladoc as in-network (particularly for Florida Blue Medicare/myBlue members); (3) explicitly inform the user that prescriptions are not guaranteed and that controlled substances cannot be prescribed through Teladoc under any circumstances, so if the intended purpose involves those drug categories the visit will not fulfill the goal.
- Teladoc's own published prescription policy confirms providers do not issue prescriptions for any federally or state-controlled substances, but this restriction is not prominently disclosed at visit initiation.
- Teladoc FAQs (multiple member-plan documents) explicitly state the service 'may not be available in certain states' and 'does not guarantee that a prescription will be written,' disclosures buried in fine print rather than upfront.
- A Florida Blue provider notice confirms Teladoc is out-of-network for Florida Blue Medicare and myBlue plan members as of January 1, 2025, meaning members who attempt to access Teladoc expecting in-network coverage will find it unavailable mid-transaction.
Human handoff required for
Escalate to a human if the user is a Florida Blue Medicare or myBlue plan member attempting to book a Teladoc visit, because as of January 2025 Teladoc is out-of-network for those plans and the user may not discover this until mid-transaction — the agent cannot reliably confirm current in-network status on behalf of the user.
Escalate to a human if the user's stated purpose for the Teladoc visit is to obtain a DEA-controlled substance prescription or a drug category explicitly excluded by Teladoc's prescribing policy, because the platform cannot fulfill this goal under any circumstances and completing the visit booking would be a wasted transaction.
Escalate to a human if the user's state of residence cannot be confirmed as a state where Teladoc's requested service type is currently available, because state-by-state regulatory constraints can make specific services partially or fully unavailable and the agent cannot verify current state-level licensing status in real time.
Five categories were checked for Teladoc: (1) discrepancy_pricing — searched for hidden fees, junk fees, or advertised-vs-checkout price gaps; no qualifying finding was identified, with results dominated by unrelated securities and telemarketing litigation. (2) discrepancy_availability — searched for ghost inventory, bait-and-switch on appointment slots, or services advertised but not bookable; no systemic structural finding was identified, though a Florida Blue Medicare network change was noted. (3) discrepancy_identity — searched for merchant-of-record ambiguity, third-party liability deflection, or counterparty confusion; no finding was identified, as Teladoc acts as a clear contracting and dispute-handling party in its ToS and in BBB complaint responses. (4) discrepancy_policy — searched for gaps between stated cancellation/refund policies and actual enforcement; scattered individual complaints were found but no regulatory action or class action established a systemic, verified discrepancy. (5) discrepancy_undisclosed_constraint — a finding was identified: Teladoc's broad marketing of virtual care does not prominently disclose state-by-state availability limits, controlled-substance prescribing prohibitions, or the January 2025 Florida Blue Medicare out-of-network change, all of which can cause a transaction initiated on prior assumptions to fail mid-booking.