Marketplace
Patient-facing search and booking. This is where consumers find providers, compare cash prices, and complete OpenDoc transactions.
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.
$ 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.
{
"service": "opendoc-protocol",
"version": "1.0.0-headless",
"tools": ["search", "list_offers", "commit"]
}
# /health is only uptime. /protocol is the map.
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.
Developer portal
Commercial and technical onboarding for platforms, agents, providers, and partners building against the OpenDoc protocol.
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.
Resolve intent to care
Use the headless API to translate patient intent into bounded, cash-priced service options and route to available providers.
Publish offers
Claim providers, configure services and cash prices, publish availability, and accept proof-of-service workflows.
Embed transactions
Bring OpenDoc search, scheduling, checkout, and Health Keys into existing patient journeys without rebuilding the backend.