Introduction

neolife is the fulfillment rail for telehealth. One API to take an approved order and route it to any compounding pharmacy, with a licensed provider in the loop, tamper-evident compliance on every order, and automatic failover when a pharmacy can't fill.

You keep your storefront, your patients, and your pharmacy relationships. neolife sits on top as the order system of record and the routing layer — so switching or adding a pharmacy is a config change, not a migration.

What you can build#

• Submit orders to a pharmacy from your own app, storefront, or agent — one request, idempotent by design.
• Gate every order behind a compliant intake questionnaire and a licensed provider's approval.
• Route across pharmacies with per-connection policies and single-hop failover.
• Track fulfillment end to end — status, shipment, tracking — over PHI-free webhooks and events.
• Automate with agents through a first-class MCP server and typed SDKs.

How it fits together#

Status, shipment, and tracking flow back to you over PHI-free webhooks and events — ids and status only, never patient data.

The two rules worth knowing up front#

1. A licensed provider approves every clinical order. There is no path that ships a compounded drug without provider approval — this is enforced server-side, not in your integration.
2. PHI never rides in webhooks or events. Callbacks carry ids and status only; you hydrate patient data over authenticated, access-controlled GETs. This keeps your webhook infrastructure out of scope for PHI. See The PHI boundary.

Next steps#

• Quickstart — get an API key and submit your first order.
• Authentication — API keys, sandbox vs. live.
• Idempotency — safe retries for a fulfillment rail.
• API reference — the full REST surface.