Pearl
Pearl is a dental AI computer-vision company whose FDA-cleared products - Second Opinion (real-time pathology and restorative detection on 2D and 3D dental radiographs), Practice Intelligence (clinical and operational analytics over full practice-management-system data), and Precheck (AI insurance claim review) - are delivered by embedding Pearl's cloud AI into third-party imaging and practice management software rather than through a public, self-serve developer API. Pearl integrates natively with 40+ imaging/PMS platforms (DEXIS, Carestream, Planmeca Romexis, Dentsply Sirona Sidexis, Apteryx XVWeb, MiPACS, Open Dental, Dentrix, Eaglesoft, Curve, Denticon, Software of Excellence EXACT) and is an authorized vendor in the Henry Schein One API Exchange. There is no publicly documented, self-signup Pearl developer API, SDK, or OpenAPI reference; API access is partner/OEM-gated and arranged through Pearl's integrations and sales teams. The API surfaces below are modeled from Pearl's public product descriptions and integration architecture, not from published Pearl API reference documentation.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Pearl the way a machine reads it — 5 machine-readable artifacts across 3 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Pearl scores 12.7/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Pearl
Each block below is one kind of artifact we hold for Pearl. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 3
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Pearl Second Opinion Image Analysis API
Partner/OEM-gated cloud AI surface behind Second Opinion. When an imaging partner uploads a bitewing, periapical, panoramic, or CBCT radiograph, Pearl's cloud computer-vision se...
Pearl Practice Intelligence Analytics API
Practice Intelligence pairs Pearl's diagnostic AI with full practice-management-system data to surface clinical quality, financial performance, appointment compliance, case acce...
Pearl PMS Integration Exchange API
The integration/enablement layer through which Pearl is provisioned inside third-party imaging and practice management systems - including as an authorized vendor in the Henry S...
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Pearl — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Access & Security 1
Authentication, authorization, and security posture
Commercial 1
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/pearl-dental · machine-readable index on apis.io