drchrono
drchrono, part of EverCommerce's EverHealth portfolio, is an all-in-one EHR, practice management and medical billing platform for independent US medical practices. It publishes two distinct machine-readable API surfaces. The proprietary REST v4 API (codename Hunt Valley) is an OAuth 2.0-secured contract of 170 paths and 329 operations covering patients, scheduling, clinical documentation, e-prescribing, labs, tasks, messaging and the full revenue cycle, published as a live OpenAPI 3.0 at https://app.drchrono.com/openapi-schema and complemented by a 27-event webhook surface. Alongside it drchrono runs a read-only, ONC-certified SMART on FHIR R4 server exposing 27 US Core resource types for USCDI interoperability, with SMART App Launch and OpenID Connect discovery, FHIR Bulk Data Export, and a public service base directory covering 105 practices. The two estates share no tokens, no scopes and no identifier space.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles drchrono the way a machine reads it — 177 machine-readable artifacts across 2 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 — drchrono scores 80.9/100 (exemplar), with a separate agent-readiness read of 35/100 (agent ready). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from drchrono's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/drchrono/"
title="drchrono on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/drchrono.svg"
alt="drchrono Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/drchrono/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/drchrono/"
title="drchrono on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/drchrono/card.svg"
alt="drchrono Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile drchrono
Each block below is one kind of artifact we hold for drchrono. 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 7
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.
drchrono Administrative API
Create and manage administrative resources
drchrono Audit API
Search Audit Logs
drchrono Availability API
The Availability API from drchrono — 1 operation(s) for availability.
drchrono Billing API
Create and manage billing resources
drchrono Clinical API
Create and manage clinical resources
drchrono Practice Management API
Create and manage practice management resources
drchrono SMART on FHIR R4 API
The ONC-certified SMART on FHIR R4 interoperability API for the DrChrono EHR. Read-only, 27 US Core resource types, FHIR 4.0.1, with a live CapabilityStatement, SMART App Launch...
Scroll within the panel for all 7 ·
Open Collections 7
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONDrChrono EHR REST Administrative API
OPEN COLLECTIONDrChrono EHR REST Administrative Audit API
OPEN COLLECTIONDrChrono EHR REST Administrative Availability API
OPEN COLLECTIONDrChrono EHR REST Administrative Billing API
OPEN COLLECTIONDrChrono EHR REST Administrative Clinical API
OPEN COLLECTIONDrChrono EHR REST Administrative Practice Management API
OPEN COLLECTIONScroll within the panel for all 7 ·
Arazzo Workflows 5
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
drChrono Appointment Scheduling
Read a patient record, book an appointment, then read the appointment back to confirm it was created.
ARAZZOdrChrono Chart Export
Pull a patient chart by reading the patient, listing problems and medications, and exporting a C-CDA document.
ARAZZOdrChrono Clinical Documentation
Document a patient visit by recording a problem, a medication, and a clinical note.
ARAZZOdrChrono Eligibility and Billing
Run the revenue cycle by checking insurance eligibility, reviewing day sheet charges, and adding a claim billing note.
ARAZZOdrChrono Patient Registration (Upsert)
Search for an existing patient by name and update it if found, otherwise create a new patient record.
ARAZZOPricing 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 things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Drchrono Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Drchrono Finops
FINOPSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
DrChrono EHR Webhooks
AsyncAPI description of the DrChrono EHR webhook surface, generated faithfully from the webhook reference DrChrono publishes at https://app.drchrono.com/api-docs/. Every event n...
ASYNCAPISemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Drchrono Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
drchrono API Rules
SPECTRALJSON Schema 77
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Appointment
JSON SCHEMAAppointmentProfile
JSON SCHEMAAppointmentTemplate
JSON SCHEMAAsyncResourceError
JSON SCHEMAAuditLog
JSON SCHEMABillingLineItem
JSON SCHEMABillingLineItemDeletion
JSON SCHEMABillingProfile
JSON SCHEMACarePlan
JSON SCHEMACareTeamMember
JSON SCHEMACashPayment
JSON SCHEMACashPaymentLog
JSON SCHEMAClaimBillingNotes
JSON SCHEMAClinicalNote
JSON SCHEMAConsentForm
JSON SCHEMACoverage
JSON SCHEMACustomAppointmentFieldType
JSON SCHEMACustomInsurancePlanName
JSON SCHEMACustomPatientFieldType
JSON SCHEMACustomVitalType
JSON SCHEMADoctor
JSON SCHEMADoctorFeeSchedule
JSON SCHEMADoctorMessage
JSON SCHEMADoctorOptions
JSON SCHEMAEOBObject
JSON SCHEMAFeeSchedule
JSON SCHEMAFeeScheduleItem
JSON SCHEMAImplantableDevice
JSON SCHEMAInsurance
JSON SCHEMAInventoryCategory
JSON SCHEMAInventoryVaccine
JSON SCHEMALabOrder
JSON SCHEMALabOrderDocument
JSON SCHEMALabResult
JSON SCHEMALabTest
JSON SCHEMALabVendorLocation
JSON SCHEMALineItemTransaction
JSON SCHEMAOffice
JSON SCHEMAPatient
JSON SCHEMAPatientAllergy
JSON SCHEMAPatientAmendment
JSON SCHEMAPatientAuthorization
JSON SCHEMAPatientCommunication
JSON SCHEMAPatientDrug
JSON SCHEMAPatientFlagType
JSON SCHEMAPatientIntervention
JSON SCHEMAPatientLabResultSet
JSON SCHEMAPatientMessage
JSON SCHEMAPatientPhysicalExam
JSON SCHEMAPatientProblem
JSON SCHEMAPatientRiskAssessment
JSON SCHEMAPatientVaccineRecord
JSON SCHEMAPhoneCallLog
JSON SCHEMAPrescriptionMessage
JSON SCHEMAProcedure
JSON SCHEMAReminderProfile
JSON SCHEMAScannedClinicalDocument
JSON SCHEMAScheduleBlock
JSON SCHEMASignedConsentForm
JSON SCHEMASignedConsentFormUpdate
JSON SCHEMASoapNoteCustomReport
JSON SCHEMASoapNoteLineItemFieldType
JSON SCHEMASoapNoteLineItemFieldValue
JSON SCHEMAStaff
JSON SCHEMATask
JSON SCHEMATaskCategory
JSON SCHEMATaskNote
JSON SCHEMATaskStatus
JSON SCHEMATaskTemplate
JSON SCHEMATelemedicineAppointment
JSON SCHEMATelemedicineAppointmentEventLog
JSON SCHEMAUserProfile
JSON SCHEMAUserProfilesGroup
JSON SCHEMAWorkDay
JSON SCHEMAWorkHours
JSON SCHEMAWorkSchedule
JSON SCHEMAYellowNotepad
JSON SCHEMAScroll within the panel for all 77 ·
Examples 69
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Appointment Example
EXAMPLEAppointmentprofile Example
EXAMPLEAppointmenttemplate Example
EXAMPLEBillinglineitem Example
EXAMPLEBillingprofile Example
EXAMPLECareplan Example
EXAMPLECareteammember Example
EXAMPLECashpayment Example
EXAMPLECashpaymentlog Example
EXAMPLEClaimbillingnotes Example
EXAMPLEClinicalnote Example
EXAMPLEConsentform Example
EXAMPLECoverage Example
EXAMPLECustomvitaltype Example
EXAMPLEDoctor Example
EXAMPLEDoctorfeeschedule Example
EXAMPLEDoctormessage Example
EXAMPLEDoctoroptions Example
EXAMPLEEobobject Example
EXAMPLEFeeschedule Example
EXAMPLEImplantabledevice Example
EXAMPLEInsurance Example
EXAMPLEInventorycategory Example
EXAMPLEInventoryvaccine Example
EXAMPLELaborder Example
EXAMPLELaborderdocument Example
EXAMPLELabresult Example
EXAMPLELabtest Example
EXAMPLELabvendorlocation Example
EXAMPLELineitemtransaction Example
EXAMPLEOffice Example
EXAMPLEPatient Example
EXAMPLEPatientallergy Example
EXAMPLEPatientamendment Example
EXAMPLEPatientcommunication Example
EXAMPLEPatientdrug Example
EXAMPLEPatientflagtype Example
EXAMPLEPatientintervention Example
EXAMPLEPatientlabresultset Example
EXAMPLEPatientmessage Example
EXAMPLEPatientphysicalexam Example
EXAMPLEPatientproblem Example
EXAMPLEPatientvaccinerecord Example
EXAMPLEPhonecalllog Example
EXAMPLEPrescriptionmessage Example
EXAMPLEProcedure Example
EXAMPLEReminderprofile Example
EXAMPLEScheduleblock Example
EXAMPLESignedconsentform Example
EXAMPLESoapnotecustomreport Example
EXAMPLEStaff Example
EXAMPLETask Example
EXAMPLETaskcategory Example
EXAMPLETasknote Example
EXAMPLETaskstatus Example
EXAMPLETasktemplate Example
EXAMPLEUserprofile Example
EXAMPLEUserprofilesgroup Example
EXAMPLEWorkschedule Example
EXAMPLEYellownotepad Example
EXAMPLEScroll within the panel for all 69 ·
Security Posture 3
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.
Scopes 2
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for drchrono — 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 5
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 9
Authentication, authorization, and security posture
Scroll within the panel for all 9 ·
Operate 5
Status, limits, changes, and where to get help
Commercial 6
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 4
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/drchrono · machine-readable index on apis.io
This is an independent, third-party profile of drchrono, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.