Skip to content

GetMeDoc for AI agents

GetMeDoc is a concierge for booking medical appointments. It finds out who will see you and when — never why. It phones clinics on the patient’s behalf, in Slovak and Czech, and brings back real appointment offers.

How to connect

MCP (Streamable HTTP): https://app.example.com/mcp, with OAuth 2.1 sign-in on behalf of the patient.

Tool catalogue for fetch-only agents: https://app.example.com/.well-known/mcp.json; call a tool with POST https://app.example.com/mcp/tool/<name>.

A2A: agent card at https://app.example.com/.well-known/agent-card.json.

Simplest path: the ask-agent MCP tool hands the whole request to the GetMeDoc agent.

No integration: the link opens a GetMeDoc chat with the request already filled in — the person reads it and sends it themselves. https://app.example.com/chat?lang=en#q=<request>

Booking flow

  1. create-case opens one need for the patient.
  2. Intake: update-case saves each answer as the patient gives it; get-case is the source of truth for status.
  3. Sign-in: request-phone-code shows the phone-verification card to the patient.
  4. count-providers returns how many clinics can be approached (a number only).
  5. Payment: case-payment shows the payment card; only the patient pays.
  6. approve-case freezes the brief and starts outreach; GetMeDoc phones the clinics.
  7. Offers arrive; accept-offer books one, only after the patient explicitly chooses it.
  8. Anything clinical, insurance- or price-related: request-human.

Rules an agent must follow

  • Never diagnose, triage, judge urgency or decide eligibility for care.
  • Share only what a receptionist needs to book the appointment.
  • Only the patient pays, through the payment card in the app, with their consent. Never quote the fee.
  • Never invent an offer, a clinic or a result.
  • Hand clinical, insurance and pricing questions to a colleague with request-human.
  • Sign-in is the patient’s own phone verification. An agent never handles the verification code.