zocdoc.com

No evidence found that Zocdoc has adopted or is listed as a partner for the Agent2Agent (A2A) protocol. Known A2A launch partners include Atlassian, Box, Intuit, PayPal, Salesforce, SAP, ServiceNow, and others — Zocdoc does not appear among them. Neither search returned any Zocdoc-specific A2A or Agent Communication Protocol reference.

No evidence found that Zocdoc has adopted or is piloting the Agentic Commerce Protocol. Known early ACP adopters include Checkout.com, and the protocol's commerce focus (physical product discovery and purchase) is structurally misaligned with Zocdoc's healthcare appointment-booking model. Not confirmed absent via any Zocdoc-specific statement; this is a not_found based on absence from all discoverable partner lists.

No evidence found of Zocdoc participating in AP2 (Agent Payments Protocol) as a launch partner or implementer. Known AP2 launch partners include Google, Mastercard, Visa, ManusAI, CVS Health, OpenAI, Amazon, and Okta — healthcare appointment booking platforms like Zocdoc do not appear on any published partner list. Zocdoc's AI-related work (its 'Zo' scheduling assistant) operates independently of AP2's cryptographic payment-consent framework.

Exposes Zocdoc's healthcare appointment booking API as an MCP server, enabling AI agents to search for provider availability, book appointments, and access healthcare directory data; scope is limited to the capabilities covered by the partner API (search, booking, scheduling management).

Zocdoc's official developer documentation at api-docs.zocdoc.com explicitly references an MCP server with 'Connect to Cursor' and 'Install MCP server on VS Code' links embedded directly in the API reference pages, confirming vendor-documented presence. Access requires a partner relationship (credentials are not self-serve). No deprecation or removal notices were found.

MPP (Machine Payments Protocol, co-authored by Stripe and Tempo) launched with named design partners including Anthropic, DoorDash, Mastercard, Nubank, OpenAI, Ramp, Revolut, Shopify, Standard Chartered, and Visa. Zocdoc does not appear among any published launch partners, design partners, or early adopters in any available source. No vendor-specific evidence of Zocdoc adopting or evaluating MPP was found.

No usable finding available for this protocol (no legitimate scan available within the candidate window).

No evidence found that Zocdoc has implemented or announced support for the Universal Commerce Protocol (UCP). UCP adoption results returned only retail and e-commerce merchants (Shopify, Google Merchant Center participants); Zocdoc's own developer and partner surfaces focus on healthcare appointment scheduling via its proprietary API and partner integrations (Yelp, Healthgrades, Google, Apple), none of which reference UCP. Zocdoc operates in healthcare scheduling, not retail commerce, making UCP adoption structurally unlikely but not ruled out by any vendor-specific statement. Status is not_found rather than confirmed_absent because no Zocdoc-specific deprecation or denial was found — only an absence of any mention.

No evidence that Zocdoc has implemented or announced WebMCP support. The protocol is a Chrome early-preview feature co-developed by Google and Microsoft; known adopters are developer-tooling and infrastructure vendors (e.g., Cloudflare), not healthcare booking platforms. Zocdoc's own developer surface is a partner-gated REST API for scheduling and insurance data, with no mention of WebMCP.

No evidence that Zocdoc (zocdoc.com) has adopted or announced support for the x402 stablecoin micropayment protocol. Known confirmed x402 launch partners include Coinbase, Cloudflare, Solana Foundation, and Stellar Foundation — none of the search results reference Zocdoc or any healthcare appointment-booking vendor in this context. Zocdoc's consumer-facing business model (insurance-based appointment booking) is structurally misaligned with the API micropayment use case x402 targets.

No usable finding available for this protocol (no legitimate scan available within the candidate window).

Unified REST API covering two distinct functional surfaces: (1) demand-side patient booking — search Zocdoc's provider network by specialty, insurance, and location; retrieve real-time timeslots; complete or redirect bookings; and (2) supply-side provider management — create and manage provider calendar availability, timeslots, and appointments on behalf of practices or EHRs. An Insurance API (retrieve/update insurance plan participation) is additionally available to select partners only. All surfaces share a single base URL and OpenAPI spec.

Zocdoc's proprietary REST API (branded 'Zocdoc for Developers') is publicly documented at api-docs.zocdoc.com with a downloadable OpenAPI spec, but access requires applying to become a Developer Partner via a contact form — no self-serve credential issuance. The supply-side calendar integration use case is primarily targeted at EHR vendors through a separate tiered partnership program at zocdoc.com/about/integrate/; the Insurance API subset is restricted to select partners beyond that.

Structured factual reference page about Zocdoc's mission, products, capabilities, and policies, explicitly intended for AI assistants and LLM indexers; not a machine-readable file like llms.txt but a publicly crawlable human/machine-readable HTML page self-declared for AI consumption.

Zocdoc publishes a dedicated page at https://www.zocdoc.com/about/ai-llm-info/ explicitly targeting AI assistants, LLM indexers, and knowledge systems — it is marked open for responsible AI indexing. No standard llms.txt, AGENTS.md, or /.well-known/agent file was found; direct fetch attempts to zocdoc.com and www.zocdoc.com for those paths returned connection failures (000), and no web search evidence of those files exists. The /about/ai-llm-info/ page is Zocdoc's own self-declared discovery surface, distinct from the conventional file-based standards but clearly intentional.