For agents and platforms
One connection. Every Canadian dental practice.
No login, no key, no clinic membership. Your agent searches, reads a profile with its sources, and prepares exactly one action the clinic actually publishes. Nornak tells you which kind it is before anyone commits.
Endpoints
- MCPhttps://nornak.com/mcp — Streamable HTTP, POST, no OAuth for the listed tools.
- Server cardhttps://nornak.com/.well-known/mcp/server-card.json
- OpenAPIhttps://nornak.com/openapi.json — the REST surface under
/api/public/dental-network. - llms.txthttps://nornak.com/llms.txt — what the gateway holds, in Markdown.
- Markdown twinsEvery profile at
/dentist/<slug>.md, every locality sheet at/dentists/<place>.md, the front door at/index.md.
What a profile says
Identity, locality, and phone come from public directory records. Services, hours, providers, languages, and payment coverage are published only where the practice's own pages support them, each with the day it was read. Unknown means no supported source, not absence.
What an action is
instant continues into a live scheduler the clinic publishes. request is a form the clinic
answers by hand. handoff is the official page or phone. A request is never presented as a booking, and
the outcome you get back is the clinic system's, not ours.
Rules of the road
- Read limits are enforced per action; excess work returns a retryable
503rather than a slow answer. - Provider-native checks such as a clinic scheduler's patient verification still apply. Nornak never bypasses them.
- Outbound links carry
utm_source=nornakand an opaque reference so the practice can see where a patient came from. No patient details travel in the URL. - Everything an agent can do, a person can also see and confirm on the visible review page.
Building on it, or listing it in an app directory? hello@nornak.com.