> ## 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.

# Hi Doctor for AI agents: MCP connector and REST API

> How AI agents use Hi Doctor: the product MCP connector, the docs search MCP and the patient REST API, with ten safety rules.

AI agents work with Hi Doctor through the product MCP connector at `https://mcp.hi-doctor.ai/mcp` or the patient REST API at `https://api.hi-doctor.ai`. Both act only with the patient's own sign-in and approved permissions, and an EU-licensed doctor makes every medical decision. Start with the agent quickstart, then follow the ten safety rules on this page.

Last reviewed: 2026-11-04

## What is Hi Doctor?

Hi Doctor is an online medical consultation service. 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. The full country list is on [countries](https://docs.hi-doctor.ai/essentials/regions.md). Some treatments are limited to specific countries by local rules.

Every consultation is reviewed in full by an EU-licensed doctor, who decides on medical grounds only. The full statement is on [safety](https://docs.hi-doctor.ai/essentials/safety.md). If the doctor prescribes, the patient receives a prescription they can use at a pharmacy: an electronic prescription where the pharmacy's country supports it, otherwise a signed prescription document. [How it works](https://docs.hi-doctor.ai/essentials/how-it-works.md) describes the whole path.

## Which interface should an agent use?

| Interface | Endpoint | Use it for |
| - | - | - |
| Hi Doctor product MCP | `https://mcp.hi-doctor.ai/mcp` | An assistant acting for one signed-in patient. Tools depend on the scopes the patient approves. |
| Hi Doctor docs search MCP | `https://docs.hi-doctor.ai/mcp` | Searching the public documentation. It has no access to any patient account. |
| Patient REST API | `https://api.hi-doctor.ai` | Your own application, with a patient JWT access token and the `X-Brand-Slug: hi-doctor` header. |

MCP OAuth tokens and REST JWTs are different credentials: never send one to the other interface. If you are new to MCP, read [what MCP is](https://docs.hi-doctor.ai/ai/what-is-mcp.md). To compare the two for a product, read [integration options](https://docs.hi-doctor.ai/businesses/integration-options.md).

## How does an agent start?

1. Read the public [connection instructions](https://docs.hi-doctor.ai/mcp/connect.md) and complete the patient's sign-in and consent.
2. List the tools the connection offers. The catalog depends on the approved scopes.
3. Make the smallest read that answers the patient's request, for example the profile.

The [agent quickstart](https://docs.hi-doctor.ai/ai/quickstart.md) walks through this path and the questionnaire sequence. For application code, use the [REST quickstart](https://docs.hi-doctor.ai/api-reference/quickstart.md). Never ask a patient to paste a password, verification code or token into chat.

## Where must a person act?

Some steps belong to the patient or the doctor and can never be done by an agent.

| Step | Who acts and what the agent does |
| - | - |
| Account setup | The patient verifies their email and completes any identity step through the supported flow. |
| Sign-in and consent | The patient signs in and approves permissions. The integrator separately sets up the lawful basis and safeguards for health data. |
| Questionnaire | The patient gives truthful answers and confirms the read-back before submission. |
| Photographs and documents | The patient takes the photograph or scan. An app that supports the connector's protected upload can send it through the upload tools; otherwise the patient uploads on the website. See [workflows](https://docs.hi-doctor.ai/mcp/workflows.md). |
| Approval link | The patient opens the link, signs in on Hi Doctor and approves or declines the exact action. See [approval links](https://docs.hi-doctor.ai/mcp/approvals.md). |
| Payment | The patient pays on Stripe's hosted page. A payment link is not a receipt. |
| Medical review | An EU-licensed doctor reviews the consultation and makes the medical decision. Review happens after submission, not during the chat. |
| Pharmacy | The patient collects any prescribed medicine from a pharmacy, which charges for it. Hi Doctor does not sell or ship medicine. |

A submitted questionnaire or a checkout link does not mean treatment has been approved.

## Safety rules

* 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.

## Key terms

| Term | Meaning |
| - | - |
| Skill | The [capability skill](https://docs.hi-doctor.ai/skill.md): a public instruction file an agent can load. It describes the workflow and rules and grants no access or permissions. |
| Scope | One permission the patient approves at sign-in, such as reading the profile. See [permissions](https://docs.hi-doctor.ai/mcp/permissions.md). |
| Approval link | An `approval_url` a tool returns before a consequential action. The patient approves the exact action on Hi Doctor before the agent commits it. |
| `signed_redirect` | A delivery mode for document links. The link opens without signing in, so treat it as confidential. An `authenticated_url` link needs the patient's own session instead. |
| `Idempotency-Key` | A key sent with a write so a retry runs the write at most once. See [safe retries](https://docs.hi-doctor.ai/api-reference/idempotency.md). |

## How should an agent recover and handle sensitive data?

If a write times out, its outcome is uncertain. On the endpoints that document it, resend the same `Idempotency-Key` or look the key up before doing anything else; the write then runs at most once. Elsewhere, read the current state with a documented safe operation, or ask support before repeating it. See the [error and retry guide](https://docs.hi-doctor.ai/api-reference/errors.md).

Authorised responses can contain health records or document links that the integrator and its model provider can see. Use only the data needed for the task, and keep it out of shared logs and unrelated prompts. OAuth consent alone does not meet every requirement for processing health data. Read [MCP security](https://docs.hi-doctor.ai/mcp/security.md) and [data and consent](https://docs.hi-doctor.ai/businesses/data-and-consent.md).

## Machine-readable resources

* [Task index](https://docs.hi-doctor.ai/llms.txt): small entry point with links to the main guides.
* [Integration context](https://docs.hi-doctor.ai/llms-full.txt): selected English integration guidance, without the health library or blog.
* [Capability skill](https://docs.hi-doctor.ai/skill.md): prerequisites, workflow and safety instructions. It grants no permissions.
* [Public OpenAPI specification](https://docs.hi-doctor.ai/api-reference/openapi.json): request and response details.
* [API changelog](https://docs.hi-doctor.ai/api-reference/changelog.md) and [MCP changelog](https://docs.hi-doctor.ai/mcp/changelog.md): changes to each interface.

## Frequently asked questions

### Can an AI agent prescribe medicine through Hi Doctor?

No. 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.

### Which countries can patients use Hi Doctor from?

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.

### What is the difference between the product MCP and the docs search MCP?

The product MCP acts on one patient's account after that patient signs in and approves permissions. The docs search MCP only searches public documentation and cannot read or change any account.

### Does installing the Hi Doctor skill give an agent access to an account?

No. The skill is a set of instructions. Access comes only from the patient's own sign-in and the permissions they approve.

### Can an agent submit a questionnaire or cancel a plan on its own?

No. Consequential tools return an approval link first. The patient signs in on Hi Doctor and approves the exact action, and only then can the agent commit it.

### What should an agent do when a questionnaire returns ineligible?

Tell the patient plainly and explain the message the tool returned. Do not change the answers and submit again.

### Can an agent pay for a consultation?

No. The patient opens a payment link and pays on Stripe's hosted page. An agent never asks for or handles card details.

### Should an agent use MCP or the REST API?

Use the product MCP when an AI assistant acts for a patient in a chat. Use the REST API when you build your own application with its own screens and token handling.

## Next steps

* [Agent quickstart](https://docs.hi-doctor.ai/ai/quickstart.md): connect, list tools, read the profile and guide a questionnaire.
* [What is MCP?](https://docs.hi-doctor.ai/ai/what-is-mcp.md): the protocol behind the Hi Doctor connector, in plain terms.
* [Workflows](https://docs.hi-doctor.ai/mcp/workflows.md): patient tasks step by step, including approval links.
* [Approval links](https://docs.hi-doctor.ai/mcp/approvals.md): how a patient approves an action before it runs.

For a business integration beyond the documented patient flows, [discuss your requirements](mailto:hello@hi-doctor.ai).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.