Developers
Build and run telemedicine with your own agents.
Everything in Purple Label MD is programmable. Point your AI agents at our API, agent-ready docs, and agent pack, and they can stand up intake, visits, prescribing, pharmacy, payments, and analytics — then operate and extend it. This is the spine of the platform, not a side door — the same API our own storefronts and internal agents run on.
We provision sandbox tenants and API keys with your consult.
API reference
One programmable surface for every module.
REST endpoints for intake, visits, prescribing, pharmacy, payments, and analytics — with the contract guarantees that make a regulated platform safe to automate against.
- Published rate limits — no guessing what the platform will tolerate.
- Idempotency keys on mutating calls, with documented 409 conflict semantics.
- Cursor pagination and one consistent error envelope across every module.
- Versioned endpoints and events — semver, with a published changelog.
# A branded entry link — offering, prefill,
# and promo context carried into hosted intake
https://start.yourbrand.com/glp-1
?offering=weight-management
&promo=SPRING24
&prefill=<signed token>
# The journey comes back to you as events
GET /v1/orders/ord_9f3a.../status
200 OK
{ "status": "VISIT_SCHEDULED", "version": 3 }Illustrative — the live reference lives at docs.purplelabelmd.com. We provision sandboxes with your consult.
Agent-ready docs
Documentation your agents can act on.
Docs structured for AI agents to consume and execute against — not a PDF your team has to translate.
Built for machine consumption
- Machine-readable and example-rich — every endpoint shows a working call.
- Addressable: each resource, field, and error has a stable URL your agents can cite.
- Written to be consumed by an agent first, skimmed by a human second.
Connect agents directly
- Your agents will connect to the platform over the Model Context Protocol at launch.
- No scraping docs, no bespoke glue code — the tools will be typed and discoverable.
- Scoped to the same tokens and environments as the REST API.
MCP servers
Your agents, plugged straight into the platform.
Connect over the Model Context Protocol and skip the integration layer entirely. Ships at launch.
Prompt library
A starting playbook for every module.
Curated, customizable prompts that get your agents productive on day one, with MCP connectors following at launch — a playbook first, then a socket.
Fork, tailor, version
- A curated, customizable prompt for building and operating each module.
- Your agents’ starting playbook — fork it, tailor it to your brand, version it.
- Covers intake assembly, visit triage, fulfillment ops, reporting, and more.
Webhooks & events
Automate everything else.
Subscribe to platform events and let your agents and systems react in real time — with the delivery guarantees that let you stop worrying about missed events.
- HMAC-signed deliveries, with key rotation.
- Retries with backoff, a dead-letter queue, and replay.
- Per-client subscriptions, in thin or full payload modes.
Events include patient.qualified,order.created,visit.completed,rx.prescribed, andshipment.updated.
POST https://yourbrand.com/webhooks
X-PL-Signature: t=1789041600,v1=5f8a1c9e...
{
"event": "visit.completed",
"data": {
"visit_id": "vst_3p9d...",
"patient_id": "pat_77a1..."
}
}Illustrative payload.
Built to build on
Environments, tokens, and versioning.
The boring guarantees that make a platform safe to automate against.
Sandbox & production
Scoped tokens
Versioned API
Connect the rest of your stack
On infrastructure that's cleared the reviews
See under the hood
Get started