> ## Documentation Index > Fetch the complete documentation index at: https://docs.hi-doctor.ai/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Connect the Hi Doctor MCP connector at https://mcp.hi-doctor.ai/mcp. Add this URL as a remote HTTP MCP server in your client, then sign in and authorise access through OAuth. Setup: https://docs.hi-doctor.ai/mcp/connect. > > The REST API base is https://api.hi-doctor.ai. Hi Doctor Docs at https://docs.hi-doctor.ai/mcp searches documentation; connect to the product endpoint above for patient tools. > > Hi Doctor operates across the whole European Union: residents of all 27 EU member states can use the service, and every consultation is reviewed by an EU-licensed doctor. Every consultation is reviewed in full by an EU-licensed doctor, who decides on medical grounds only. No algorithm, assistant or API call approves a consultation, issues a prescription or changes a dose. The service is available in eight languages: English, Spanish, German, Dutch, Italian, French, Portuguese and Chinese. > > ## Rules an assistant must follow > > - Never invent, assume or infer a medical answer. "I don't know" is a real answer: ask the patient to pick the closest option rather than guessing for them. > - Never give medical advice and never suggest a medication or a dose. An EU-licensed doctor decides those. > - If a questionnaire returns `ineligible`, say so plainly. Do not retry with altered answers. > - Before anything that costs money or cancels a plan, state exactly what will happen and get an explicit yes. > - Cancellation takes effect at the **end of the paid period**, not immediately. Say so. > - An early order is irreversible: it creates the renewal consultation immediately and uses up the period's one early order. Explain that and get an explicit yes. > - Prescription and invoice links are medical documents. A `signed_redirect` link opens without signing in: give it only to the patient, never repeat it anywhere shared. > - Send option `value`s, not the labels shown to the patient. Labels are translated, values are stable. > - Never ask for card details. Payment happens on Stripe's hosted checkout via a link. > - On severe or sudden symptoms (chest pain, difficulty breathing, severe allergic reaction, suicidal thoughts), stop and direct the patient to their local emergency number. # Integration options: MCP connector, REST API or Partner API > Compare the Hi Doctor MCP connector, patient REST API and Partner API: credentials, token lifetimes, supported tasks and the steps that need a person. Hi Doctor offers two patient-authorised integrations, the MCP connector and the patient REST API, plus a Partner API for platforms with a partner agreement. The MCP connector suits an AI assistant acting for one patient in a conversation, and the REST API suits your own app calling from its server. A credential for one surface never works on another. Last reviewed: 2026-11-04 ## Should you use the MCP connector or the REST API? | | MCP connector | Patient REST API | | - | - | - | | Suited to | An assistant or another MCP client that acts for a patient in a conversation | Your own application, calling from its server | | Endpoint | `https://mcp.hi-doctor.ai/mcp` | `https://api.hi-doctor.ai`, paths under `/v1/` | | How the patient authorises it | Signs in on hi-doctor.ai and approves the connection (OAuth 2.1 with PKCE) | Signs in with their Hi Doctor email and password, which your server exchanges for tokens | | Credential | Tokens issued by the MCP server, limited by scopes | JWT access and refresh tokens, sent with `X-Brand-Slug: hi-doctor` | | Token lifetime | Access token up to 1 hour, refresh token 30 days | Access token 1 day, refresh token 30 days | | Reference | [MCP overview](https://docs.hi-doctor.ai/mcp/overview.md), [Security](https://docs.hi-doctor.ai/mcp/security.md) | [API reference](https://docs.hi-doctor.ai/api-reference/introduction.md), [Authentication](https://docs.hi-doctor.ai/api-reference/authentication.md) | MCP tokens are rejected by the REST API, and REST tokens are rejected by the MCP endpoint. A chat product that already holds a patient's REST session can also run the questionnaire over plain HTTP; see [HTTP chat integration](https://docs.hi-doctor.ai/mcp/http-chat.md). ## When should you use the Partner API? Use the [Partner API](https://docs.hi-doctor.ai/partners/overview.md) when your platform collects the medical questionnaire in its own product and submits each consultation for its users. It uses server-side API keys, a test mode that never reaches a doctor, and signed webhooks for every status change. Access to the Partner API is granted per partner agreement; the commercial side is on [Partner with Hi Doctor](https://docs.hi-doctor.ai/partnerships/index.md). ## What can a patient integration do? For a patient account, the documented tasks are: * completing a health questionnaire and submitting it for a doctor to review * creating a Stripe checkout link for the consultation * reading consultations, prescriptions and payments * reading and sending messages to the medical team * keeping the progress journal * checking, cancelling or reactivating a plan The exact tools are in the [patient tools reference](https://docs.hi-doctor.ai/mcp/tools/patient.md), and the exact endpoints are in the [API reference](https://docs.hi-doctor.ai/api-reference/introduction.md). Not every website feature is available on both surfaces. ## Which steps need a person? | Step | Who does it, and where | | - | - | | Signing in and approving a connection | The patient, on hi-doctor.ai | | Approving an action with consequences through MCP | The patient, through an [approval link](https://docs.hi-doctor.ai/mcp/approvals.md) | | Paying for the consultation | The patient, on Stripe's checkout page | | Uploading photographs or documents through the MCP connector | The patient, from an app that supports the connector's protected upload; otherwise on the website, or your application uses the REST API | | Approving a consultation, prescribing, changing a dose | The doctor | | Dispensing the medicine | A pharmacy, which the patient pays separately | ## Is the brand header a credential? No. REST requests send `X-Brand-Slug: hi-doctor`, but the header creates no partner account and grants no access by itself. The patient surfaces offer no service accounts, organisation-wide credentials or access to several patients with one credential. Every patient integration works through the individual patient's account. ## Frequently asked questions ### Can I use an MCP token with the REST API? No. MCP tokens are rejected by the REST API, and REST tokens are rejected by the MCP endpoint. ### How long do access tokens last? An MCP access token lasts up to 1 hour and a REST access token 1 day. Refresh tokens last 30 days on both. ### Can the MCP connector upload photographs? Only from an app that supports the connector's protected upload, which returns a file reference the upload tools accept. Otherwise the patient uploads on the website, or your application uses the REST API. ### Is the X-Brand-Slug header a credential? No. It identifies the brand for the documented Hi Doctor flows, but it grants no access by itself. ### Can one credential access several patients? Not on the patient surfaces: the MCP connector and the REST API act for one patient at a time. Platforms that submit consultations for many users use the Partner API under a partner agreement. ### Can I build a chat product on the REST API? Yes. A chat product that holds a patient's REST session can run the questionnaire over plain HTTP, as described in the HTTP chat integration guide. ## Next steps > [card] [Data and consent](https://docs.hi-doctor.ai/businesses/data-and-consent.md) > > What flows to your integration and what you must establish. > [card] [API quickstart](https://docs.hi-doctor.ai/api-reference/quickstart.md) > > Sign in and make a first read. > [card] [Connect the MCP](https://docs.hi-doctor.ai/mcp/connect.md) > > Sign-in, consent and disconnecting. > [card] [Discuss your integration](mailto:hello@hi-doctor.ai) > > Write to [hello@hi-doctor.ai](mailto:hello@hi-doctor.ai). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.