b.well
b.well Connected Health is a Baltimore-based digital health platform that unifies a person's fragmented medical, pharmacy, claims, wearable and lab data into a single FHIR-native longitudinal health record, then exposes that record to partner applications through a developer platform. The company operates a consumer-mediated health data network spanning millions of providers, health plans, HIEs/HINs, TEFCA QHINs and CMS-aligned networks, and licenses it to health systems, payers, employers and retail health brands who embed it in their own apps. Its developer surface is built around four Health SDKs (Web/TypeScript, Android/Kotlin, iOS/Swift and an AI SDK that speaks Model Context Protocol), a federated GraphQL gateway, REST endpoints for user data operations and webhooks, and a FHIR R4 server (the open-source Helix FHIR Server) supporting $everything and International Patient Summary retrieval. Authentication is OAuth 2.0 throughout — token exchange with OIDC for end-user context, client credentials for system-to-system access, and HMAC-SHA512 request signing on the user data operations API.
b.well publishes 5 API contracts indexed on the APIs.io network, including Users API, Webhook API, and 3 more. Tagged areas include Company, Health, Healthcare, Digital Health, and FHIR.
The b.well catalog on APIs.io includes 1 event-driven AsyncAPI specification.
b.well’s developer surface includes engineering blog, documentation, API reference, getting-started guide, authentication, support, changelog, and 38 more developer resources.
Kin Score
Standards implemented 1
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.
b.well Application APIs
Federated GraphQL gateway plus REST endpoints that let end-user applications read and write a person's health data, manage data-source connections, handle consent, and coordinat...
b.well FHIR Server
System-level FHIR R4 API over b.well's normalized clinical data store, built on the open-source Helix FHIR Server. Supports standard FHIR REST search, $everything bulk patient r...
b.well Health SDK for AI (MCP Server)
A b.well-hosted Model Context Protocol server that exposes a catalog of healthcare agents/tools — insurance coverage validation, FHIR record and lab retrieval, patient summaries...
b.well Users API
The Users API from b.well — 2 operation(s) for users.
b.well Webhook API
The Webhook API from b.well — 1 operation(s) for webhook.
Open Collections 5
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONClient Webhook API
OPEN COLLECTIONbwell User Data Operations
OPEN COLLECTIONbwell User Data Operations Users API
OPEN COLLECTIONClient Webhook API
OPEN COLLECTIONMCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
b.well MCP Server
Remote MCP server at api.client-sandbox.icanbwell.com over HTTP; 31 tools listed.
MCP SERVERPricing Plans 1
Published pricing tiers and plan structures.
B Well Plans Pricing
PLANSRate Limits 1
Documented rate limits and quota policies.
B Well Rate Limits
RATE LIMITSEvent Specifications 1
AsyncAPI definitions for this provider's event-driven and streaming APIs.
B Well Webhooks
ASYNCAPIOpenAPI Overlays 2
Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.
B Well Client Webhook Api Overlay
GENERATEDB Well User Data Operations Overlay
GENERATEDSecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Get Started 4
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 for all 7
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 8
Authentication, authorization, and security posture
Scroll for all 8
Operate 5
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 1
Properties that don't map to a standard resource type
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.