Mend
Mend is a HIPAA-compliant telehealth and patient engagement platform for mental and behavioral healthcare organizations, powering appointment scheduling, automated reminders, secure video visits, digital intake forms and consents, patient messaging, payments, and AI no-show prediction. Mend integrates with EHR and practice-management systems through a combination of HL7, SFTP, and an API served from api.mendfamily.com. That API exists and is used by Mend's own portal for session initialization and signaling, but its reference documentation is delivered through a login-gated customer knowledge base rather than a public developer portal, so Mend's programmatic surface is best characterized as partner- and customer-gated rather than openly self-serve.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Mend the way a machine reads it — 6 machine-readable artifacts across 4 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 — Mend scores 15.5/100 (emerging), 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 Mend
Each block below is one kind of artifact we hold for Mend. 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 4
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.
Mend Appointments and Scheduling API
Logical grouping for creating and managing appointments, provider availability, patient self-scheduling, rescheduling, and automated appointment reminders. Mend documents these ...
Mend Patients API
Logical grouping for creating and syncing patient records, demographics, and contact details between Mend and an external EHR or practice-management system. Mend performs this s...
Mend Video Visits API
Logical grouping for initializing secure video telemedicine sessions and the virtual waiting room. The real-time media itself runs over WebRTC via Vonage TokBox and OpenTok rela...
Mend Digital Forms and Intake API
Logical grouping for assigning digital intake forms, consents, and assessments to patients and returning their completed responses to the practice. Mend describes these digital ...
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 Mend — 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.
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 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/mend-health · machine-readable index on apis.io