> ## 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. # Integrate Hi Doctor into your patient experience > How a company integrates Hi Doctor with the MCP connector, the patient REST API or the Partner API, what stays with the doctor, and how to start. Companies can integrate Hi Doctor in three ways: the MCP connector for AI assistants, the patient REST API for their own app, and the Partner API for platforms that submit consultations for their users. In every case your product keeps the relationship with the person, and an EU-licensed doctor makes the medical decision. Last reviewed: 2026-11-04 [Hi Doctor operates across the whole European Union](https://docs.hi-doctor.ai/essentials/regions.md): residents of all 27 EU member states can use the service, and every consultation is reviewed by an EU-licensed doctor. > [card] [Discuss your integration](mailto:hello@hi-doctor.ai) > > Tell us what you want to build. Write to [hello@hi-doctor.ai](mailto:hello@hi-doctor.ai). ## What can you build on Hi Doctor? | Surface | Suited to | How access is granted | Start here | | - | - | - | - | | MCP connector | An AI assistant acting for one patient in a conversation | Each patient connects their own account through OAuth, limited by the scopes they approve | [Connect](https://docs.hi-doctor.ai/mcp/connect.md) | | Patient REST API | Your own app, acting for one signed-in patient | Patient access and refresh tokens, with `X-Brand-Slug: hi-doctor` | [API introduction](https://docs.hi-doctor.ai/api-reference/introduction.md) | | Partner API | A platform that collects the questionnaire in its own product and submits consultations | Server-side API keys, with test and live modes | [Partner API overview](https://docs.hi-doctor.ai/partners/overview.md) | Access to the Partner API is granted per partner agreement. The commercial side of a partnership is on [Partner with Hi Doctor](https://docs.hi-doctor.ai/partnerships/index.md), and the three surfaces are compared in detail on [Integration options](https://docs.hi-doctor.ai/businesses/integration-options.md). ## What does an integration look like in practice? A wellness app wants its in-app assistant to help members start a hair-loss consultation. The member connects their Hi Doctor account through the MCP connector, and the assistant walks them through the questionnaire one question at a time. The member approves the submission and pays on Stripe's page, and an EU-licensed doctor reviews the case. The assistant can then read the outcome and messages, within the permissions the member approved. ## What stays outside an integration? * **The medical decision.** A doctor assesses the consultation and decides whether treatment is appropriate. No integration can approve a consultation, issue a prescription or change a dose. * **Medicine.** Hi Doctor does not sell, stock or ship medicine. The patient obtains any prescribed medicine from a pharmacy, which charges separately for it. * **Other accounts.** A patient integration acts for one patient at a time. It gets no access to other patients and no company-wide access. ## Who is responsible for the health data you receive? Your integration can receive sensitive health information, so its purpose, privacy notices, data handling and legal basis need to be established before you use real patient data. OAuth permission does not by itself satisfy every requirement for processing health data. Read [Data and consent](https://docs.hi-doctor.ai/businesses/data-and-consent.md) before you design the flow. ## Frequently asked questions ### Which integration should we choose? Use the MCP connector for an AI assistant, the patient REST API for your own app acting for a signed-in patient, and the Partner API if your platform collects the questionnaire and submits consultations itself. ### Can an integration approve a consultation or prescribe? No. An EU-licensed doctor reviews every consultation and makes every medical decision. No integration can approve a consultation, issue a prescription or change a dose. ### Do patients need a Hi Doctor account? For the MCP connector and the patient REST API, yes: both act with the patient's own account and permissions. ### Which countries can an integration serve? Residents of all 27 EU member states can use the service. For the Partner API, the countries and categories your platform offers are set in your partner agreement. ### Does Hi Doctor supply the medicine? No. Hi Doctor does not sell, stock or ship medicine. The patient takes the prescription to a pharmacy, which dispenses it and charges its own price. ### How do we start? Write to [hello@hi-doctor.ai](mailto:hello@hi-doctor.ai) with what you want to build. For a patient integration you can also start straight away from the MCP connection guide or the REST API introduction. ## Next steps > [card] [Integration options](https://docs.hi-doctor.ai/businesses/integration-options.md) > > MCP connector, REST API or Partner API, side by side. > [card] [Data and consent](https://docs.hi-doctor.ai/businesses/data-and-consent.md) > > What you must establish before using patient data. > [card] [Partner with Hi Doctor](https://docs.hi-doctor.ai/partnerships/index.md) > > The partner arrangement for platforms. > [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.