Skip to main content
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: residents of all 27 EU member states can use the service, and every consultation is reviewed by an EU-licensed doctor.

Discuss your integration

Tell us what you want to build. Write to hello@hi-doctor.ai.

What can you build on Hi Doctor?

Access to the Partner API is granted per partner agreement. The commercial side of a partnership is on Partner with Hi Doctor, and the three surfaces are compared in detail on Integration options.

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

Integration options

MCP connector, REST API or Partner API, side by side.

Data and consent

What you must establish before using patient data.

Partner with Hi Doctor

The partner arrangement for platforms.

Discuss your integration