Headless healthcare transaction protocol

Build cash-pay healthcare flows without becoming the healthcare backend.

OpenDoc exposes provider search, service offers, cash-price resolution, Health Keys, booking state, consent, and proof-of-service through a protocol API your product can call directly.

The engine is live. Sandbox is open to everyone. Live mode opens with our first design partners.

Get a sandbox key Explore the API View protocol discovery
$ curl https://api.opendoc.com/protocol
{
  "service": "opendoc-protocol",
  "version": "1.0.0-headless",
  "tools": ["search", "list_offers", "commit"]
}

# /health is only uptime. /protocol is the map.

Status

What is live today, and what opens with first partners.

Everything labeled live is running in production right now — you can sign up and transact against it in minutes. Exactly one thing is not open yet: live mode. We say so plainly, and we gate it on purpose.

Live today — open to everyone

Sandbox on the production engine

Instant API keys from signup — no approval, no credit card. Search the real provider directory, then drive the full S0–S8 booking and payment state machine against a synthetic provider with simulated payments. TypeScript SDK, MCP server, SSE, and webhooks included.

Opening with first partners

Live mode

Real provider inventory, real-money transactions, and Stripe Connect payouts run behind live keys, granted per-partner. We are onboarding our first design partners now — if you want to ship real bookings, talk to us.

What lives where

Three surfaces, one protocol.

The website, developer portal, and docs are separate experiences. They all orbit the same production API at api.opendoc.com.

opendoc.com

Marketplace

Patient-facing search and booking. This is where consumers find providers, compare cash prices, and complete OpenDoc transactions.

dev.opendoc.com

Developer portal

Commercial and technical onboarding for platforms, agents, providers, and partners building against the OpenDoc protocol.

docs.opendoc.com

Reference docs

API reference, OpenAPI files, SDK notes, auth details, webhook contracts, and implementation guides.

Start with the API

The protocol backend is not /health.

/health exists so infrastructure can verify the service is alive. Product integrations start at /protocol, then call resource routes like search, providers, offers, bookings, and transactions.

GET /healthOperational health check for monitors and load balancers.
GET /protocolMachine-readable discovery: capabilities, tool names, route map, auth requirements.
GET /searchFind providers and services using OpenDoc routing.
GET /offersBrowse provider x service cash-price offers.
POST /transactions/*Declare intent, authorize, accept terms, and commit a transaction.

Build paths

Choose the integration lane.

Every lane starts in the open sandbox today. Live-mode access opens per-partner.

Agent developers

Resolve intent to care

Use the headless API to translate patient intent into bounded, cash-priced service options and route to available providers. Fully exercisable in sandbox today, end to end.

Provider groups

Publish offers

Claim providers, configure services and cash prices, publish availability, and accept proof-of-service workflows. We onboard our founding practices hand in hand — this lane opens with first partners.

Platform partners

Embed transactions

Bring OpenDoc search, scheduling, checkout, and Health Keys into existing patient journeys without rebuilding the backend. Build and demo in sandbox now; go live with the first partner wave.