Xona Dental Gatewaybook.xonark.com

Use this gateway with an AI assistant

An assistant connected to Xona can search Canadian dental practices, send an appointment request to one, and — where a practice has connected its schedule — book a real open time, all without leaving the conversation.

POST https://book.xonark.com/mcp

Streamable HTTP. No account, no API key, no OAuth. Tool definitions: /mcp/llms.txt

Two routes, and the practice decides which

Call list_dental_practice_actions first. It marks the route a practice actually offers; a route it does not offer is not there to call.

Appointment request

Any listed practice with a working mailbox. Xona emails the request to the clinic; a person there answers it.

  1. start_dental_request with the patient's name and their own email. Xona emails them a six-digit code. Nothing has reached the clinic.
  2. The patient reads the code back, picks a service category, says when they are free, and agrees to the consent text the tool returned.
  3. confirm_dental_request sends it.

Ends as delivered, held, or failed — never as a confirmed appointment. The clinic replies to the patient.

Booking

A practice that claimed its page and connected its schedule to Xona. The time is written into the clinic's own book.

  1. list_xona_booking_services, then list_xona_booking_slots for one service, a week at a time.
  2. hold_xona_booking_slot takes the patient's email, mobile, name and date of birth together, holds that time and emails the patient a link. Tapping it texts the patient a second link; tapping that confirms their mobile. No code is read back in the conversation.
  3. confirm_xona_booking books it once the patient has tapped both links and agrees to the consent text; until then it says which link is waiting. Every step returns booking_steps: what is done, what the patient still has to tap, and when each link expires.
  4. At any step the patient can stop: abandon_xona_booking releases the time at once. Or they can finish in a browser: continue_url opens the practice's booking page on the held time.

Ends as a confirmed appointment in the clinic's book — or, where the practice confirms times itself, as a request the clinic answers. The outcome field says which. If Xona cannot tell whether the patient already has a chart there, it returns the practice's own booking page instead of guessing.

What the patient does themselves

Two things an assistant cannot do on the patient's behalf.

What leaves the conversation

Appointment booking, the same fields any booking takes. Nothing clinical.

Every tool this endpoint serves

Generated from the running server, so this list is what is actually there.

Reading the gateway without tools

Every public page has a Markdown twin at the same path with .md/index.md, a locality page, a profile. /llms.txt is the guide to all of it, and /openapi.json describes the same reads as REST. Pages a crawler should not take in bulk are listed in /robots.txt, and the terms of use say what use is permitted.

Search by place and condition

For an assistant that can only open a URL. The same question the search tool answers, as one GET.

Corrections and support

A practice's facts come from its own public website and from public directory records, each carrying the day it was read. Being listed is not a Xona membership. A practice can correct or claim its page, and anyone can reach a person, through contact. How patient data is handled is set out in Xonark's privacy policy.