Welldoc
Welldoc is a Columbia, Maryland digital health company whose FDA-cleared, AI-driven cardiometabolic care platform — best known through its BlueStar digital therapeutic for type 1 and type 2 diabetes — delivers personalized, real-time coaching and clinical decision support across 30+ chronic conditions including diabetes, hypertension, weight management and complex comorbid cardiometabolic disease. The platform ingests data from 400+ connected devices and data sources (blood glucose meters, CGMs, pharmacies, labs, activity trackers) and is sold to health plans, health systems, employers, life science companies, DMEs and medtech partners rather than to developers. Welldoc markets SDK and API access as a partnering option — "we offer our capabilities, AI models, and data integration through your interface via SDK and API" — but publishes no developer portal, API reference, or machine-readable contract; access is negotiated through a demo/partnering conversation.
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 Welldoc the way a machine reads it — 5 machine-readable artifacts, 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 — Welldoc scores 23.9/100 (emerging), with a separate agent-readiness read of 3/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.
Why this profile is thin
Welldoc markets SDK and API access on /platform/partnering — "we offer our capabilities, AI models, and data integration through your interface via SDK and API" — but its entire 367-URL sitemap contains no developer portal, API reference or spec, and every technical page terminates in a Get-a-Demo form.
An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is Welldoc's to change: publishing the reference and a machine-readable spec at a public URL, while keeping key issuance behind whatever gate they like, would let an integrator evaluate the API before committing to a call.
What we probed
https://www.welldoc.com/platform/partnering→ HTTP 200https://www.welldoc.com/platform/solutions→ HTTP 200https://developer.welldoc.com/→ HTTP 0https://api.welldoc.com/→ HTTP 0https://www.welldoc.com/openapi.json→ HTTP 404https://helpdesk.welldoc.com/support/solutions→ HTTP 302
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-04 · rubric v0.18.3
Put this on your own site. The badge is drawn live from Welldoc'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/welldoc/"
title="Welldoc on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/welldoc.svg"
alt="Welldoc Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/welldoc/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/welldoc/"
title="Welldoc on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/welldoc/card.svg"
alt="Welldoc 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 Welldoc
Each block below is one kind of artifact we hold for Welldoc. 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.
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 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.
Welldoc Rate Limits
RATE LIMITSSecurity 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.
Welldoc Trust Center
HITRUST r2, SOC 2 Type 2, MDSAP / ISO 13485, HIPAA, GDPR, FDA 510(k), CE Mark, Health Canada, DiMe Seal
SECURITYResources
Every other property we hold for Welldoc — 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
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Access & Security 5
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 8
The organization behind the API
Scroll within the panel for all 8 ·
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/welldoc · machine-readable index on apis.io
This is an independent, third-party profile of Welldoc, 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.