AI agent integration — Alina Szaputko

AI agent integration — Alina Szaputko

AI assistants can discover Alina Szaputko’s professional profile, check current online consultation availability and help a client complete a booking through either of two supported integrations: a remote Model Context Protocol (MCP) server, or a provider-independent HTTP API described by an OpenAPI 3.1 specification. Both methods use the same Production booking workflow and require the client’s own confirmation before payment.

1. Connect through MCP

Remote MCP endpoint: https://booking-backend-kappa-drab.vercel.app/api/mcp

This option is for AI assistants and agent platforms that support connecting to a remote MCP server over Streamable HTTP. The server exposes five tools:

  • get_professional_profile — read the public professional profile, services, languages, price and booking terms
  • list_available_slots — read currently available online consultation slots
  • request_client_consent — send the client an email with the exact proposed appointment details and confirmation link
  • create_checkout_session — create a protected Stripe Checkout session after the client has completed the required confirmation
  • get_agent_booking_status — check the minimal payment and appointment fulfilment status

2. Connect through the direct HTTP API

This option is for agents that can make HTTP requests and read OpenAPI documentation but do not support MCP. It is provider-independent and uses the same secure booking workflow.

Service available for agent booking

  • Individual online psychological consultation
  • Duration: 60 minutes
  • Price: 160 PLN
  • Consultation languages: Polish and Russian
  • Online consultations: available worldwide
  • Appointment time zone: Europe/Warsaw
  • Booking horizon: up to 14 days ahead; at least 24 hours’ notice
  • Available appointment hours: Monday to Friday, 09:00–17:00 Europe/Warsaw, subject to live availability

In-person consultations in Wrocław may be arranged directly, but they are not bookable through the agent MCP or HTTP API. Agents must not offer in-person appointments as available through these endpoints.

How secure agent booking works

  • The agent retrieves the public professional profile and current free slots. Availability is indicative and does not reserve a time.
  • The agent collects only the details needed for the appointment: client name, email, chosen date and time, consultation language, and optionally a phone number.
  • The booking system emails the client the exact proposed appointment details, booking rules and privacy notice. The client must open the confirmation link, review the information and personally complete the required confirmations.
  • Only after the client’s confirmation can the workflow use a short-lived, single-use consent token bound to the booking details. A token cannot be reused for a different appointment.
  • The agent submits the confirmed details and token. The system checks availability again, creates an atomic temporary slot hold and opens a Stripe-hosted Checkout page.
  • The client pays directly on Stripe. The agent must never ask for or handle card numbers, CVCs or payment credentials.
  • The appointment is confirmed only after verified payment and successful creation of the Calendar event. The agent can check the final status through MCP or the status API.

Privacy and technical safeguards

  • Never request or submit symptoms, diagnoses, trauma history, therapy goals, treatment reasons or other clinical details through these integrations.
  • Public profile and availability responses contain professional information and free slots only; they do not expose calendar events or other clients’ details.
  • Booking writes require the email-confirmed, one-time consent process. Checkout is handled by Stripe’s hosted payment page.
  • The service uses server-side Production and Preview gates, separate MCP signing secrets, timestamp-checked MCP request signatures, rate limits, input validation, idempotent request identifiers and atomic slot holds.
  • Stripe webhook signatures are verified before payment fulfilment. A payment-pending state or Checkout URL is not proof that an appointment is confirmed.
  • Do not bypass the confirmation process, submit a Boolean consent flag or mark an appointment as booked before the status endpoint confirms both payment and fulfilment.

Human booking and policies

Clients can also book without an AI assistant through the standard online booking page. Please read the booking rules in Russian, booking rules in Polish and the booking privacy notice.

Кратко по-русски

AI-ассистенты могут находить профиль Алины Шапутько, проверять актуальные свободные слоты и помогать с записью двумя способами: через удалённый MCP-сервер или через прямой HTTP API с документацией OpenAPI. Доступна индивидуальная онлайн-консультация продолжительностью 60 минут, стоимость — 160 PLN; языки консультации — русский и польский. Онлайн-консультации доступны по всему миру. Для записи клиент должен лично подтвердить предложенные дату и время, ознакомиться с правилами и политикой конфиденциальности и завершить подтверждение по электронной почте. Оплата проходит непосредственно на защищённой странице Stripe. Запись считается подтверждённой только после успешной оплаты и создания события в календаре. MCP endpoint · OpenAPI.

Krótko po polsku

Asystenci AI mogą znaleźć profil Aliny Szaputko, sprawdzić aktualne wolne terminy i pomóc w rezerwacji na dwa sposoby: przez zdalny serwer MCP albo bezpośrednie HTTP API opisane w OpenAPI. Dostępna jest indywidualna konsultacja psychologiczna online: 60 minut, 160 PLN, w języku polskim lub rosyjskim. Konsultacje online są dostępne na całym świecie. Klient musi samodzielnie potwierdzić proponowany termin, zapoznać się z zasadami i polityką prywatności oraz ukończyć potwierdzenie e-mailowe. Płatność odbywa się bezpośrednio na bezpiecznej stronie Stripe. Termin jest potwierdzony dopiero po skutecznej płatności i utworzeniu wydarzenia w kalendarzu. Endpoint MCP · Dokumentacja OpenAPI.