FindDoc
FindDoc provides a structured REST API and MCP access to Greater Toronto Area doctors, specialists, clinics, languages, availability signals, and data freshness. It complements the CPSO physician-registration source with additional data such as clinic reviews, language support, and real-time availability, offering best‑effort freshness reporting and encouraging users to confirm details directly with clinics.
FindDoc publishes 5 API contracts indexed on the APIs.io network, including Clinics API, Doctors API, Health API, and 2 more. Tagged areas include Healthcare, Doctors, Clinics, and Canada.
The FindDoc catalog on APIs.io includes 1 Spectral governance ruleset.
FindDoc’s developer surface includes authentication, documentation, API reference, getting-started guide, support, pricing, and 17 more developer resources.
Kin Score
Standards implemented 3
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
APIs 5
Individual APIs this provider publishes, each with its own machine-readable definition.
FindDoc Clinics API
Clinic search, detail, reviews, and signals.
FindDoc Doctors API
Doctor search and detail by CPSO number.
FindDoc Health API
Liveness and readiness.
FindDoc Metadata API
Supported specialties and languages.
FindDoc Specialists API
Specialist clinic search.
MCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
Spectral Rules 1
Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.
FindDoc API Rules
SPECTRALSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access (API Evangelist recommendations) 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 2
Properties that don't map to a standard resource type
Source (apis.yml)
FindDoc API — frequently asked questions
Does FindDoc have an API?
Yes. APIs.io lists 5 APIs from FindDoc, including FindDoc Clinics API, FindDoc Doctors API and FindDoc Health API, and 2 more.
Is there an OpenAPI specification for the FindDoc API?
Yes. APIs.io indexes 5 OpenAPI specifications for FindDoc, each linked for download from this page.
How do I authenticate with the FindDoc API?
FindDoc documents its authentication (2 schemes). The details are profiled on APIs.io as FindDoc Authentication.
Does FindDoc have an MCP server?
Yes. APIs.io lists 1 MCP server for FindDoc: Remote MCP server at www.finddoc.ca requiring an API key.
Is the FindDoc API ready for AI agents?
FindDoc has a Kin Score of 35.1 out of 100 (thin) and an Agent Readiness score of 36.1 (agent-ready), scored by API Evangelist on 2026-11-13.
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.