Skip to main content
Brelio gives programs two doors to a clinic’s data. Both are built from the same operation catalogue, so every operation has the same name, rules, permissions and errors in both.

Connect your AI assistant

Two minutes: add the MCP server to your assistant, sign in, and ask about your clinic.

Make your first API call

Two minutes: create an API key and list your clinic’s services with curl.

​
What you can build

  • An assistant for the front desk. Ask «¿Qué huecos tiene Laia el jueves por la mañana?» and get real free slots from the agenda.
  • Online booking. Find free slots, book the patient, and reschedule or cancel when they ask.
  • Sync with your own systems. Keep a CRM, a call centre tool or a data warehouse in step with the clinic’s patients and appointments.
  • Automations. Connect Brelio to n8n, Make or your own scripts, and receive signed webhooks instead of polling.

​
What always holds

  • The same rules as the web app. Same permissions, same center visibility, same validation and the same plan limits.
  • Patient data is closed by default. The clinic decides which data areas integrations may use, and each credential needs its own acceptance before it touches patient data.
  • Changes never overwrite each other. Every record carries a version; you send it back as expectedVersion (concurrency).
  • Retries are safe. Every write takes an Idempotency-Key (idempotency).
  • Errors explain themselves. One JSON shape with a stable code and, when there is one, a hint (errors).
  • Everything is recorded. The clinic sees every connection and what it did, including refused attempts.
The API and MCP server are in early access. Calls from an organization without access answer 402 PLATFORM_PLAN_REQUIRED. The API itself, its error texts and the OpenAPI document are in English; these docs are in Spanish and English.

​
Machine-readable resources