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 and 1 Spectral governance ruleset.

b.well’s developer surface includes engineering blog, documentation, API reference, getting-started guide, authentication, support, changelog, and 38 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

58.2/100 strong ▬ flat Agent 59/100 agent ready Front door AI 5/6 prominent Heartbeat 100/100 alive open core · MIT Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessSelf serve

2 published contracts 1 MCP Servers 5 Agent Skills

Company Health Healthcare Digital Health FHIR Health Data Interoperability Patient Access Health Records MCP

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 58.2/100 · strong

Contract Quality 9.3 / 16

Developer Ergonomics 9.7 / 13

Access Clarity 5.6 / 13

Operational Transparency 3.3 / 8

Contract Governance 2.5 / 8

Discoverability 4.9 / 7

Regulatory Posture 6.9 / 15

Open Source Surface 5.0 / 10

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 59/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 6 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Health regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Open Source Surface applies to this provider. This product is open source and we read its repository directly, so Open Source Surface carries 10 points of the composite. It is scored from what the repository actually publishes — a security policy, a contribution guide, a release history, a code of conduct — read live from the provider rather than inferred from our own catalog pointers. This facet adds; nothing was taken away to make room for it. An open-source project is not excused from the commercial facets, because exemption would strip it of the points it does earn. If we have the wrong repository, or this product is not open source, say so on your provider repo and we will drop the facet rather than have you publish against it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 65 points between them, because both conditional facets apply and carry 35 points together. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 65% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/b-well/"><img src="https://apis.io/badge/b-well/card.svg" alt="b.well on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Documented Reversibility +6 pts — a reversal operation in the contract, graded up when a window is documented too
Agentic Commerce Well-Known Document +5 pts — a parsing /.well-known/ucp.json or acp.json declaring a version and at least one service, OR (0.27) a live x402 payment challenge from _data/x402-adoption.json — `self` when its endpoints are on the provider's own domain, `platform` when they are on a vendor's
Dry-Run / Simulate Mode +4 pts — OpenAPI: destructive operations expose a dry_run / simulate / preview / validate_only parameter
Well-Known Catalog +4 pts — common[].type includes WellKnown, APICatalog, or api-catalog

1 more unmet check in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 43.4 — up to +11.3 composite points
Contract Quality scores 57.0 — up to +10.8 composite points
Contract Governance scores 31.8 — up to +8.2 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/b-well/apis.yml: open an issue on github.com/api-evangelist/b-well to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Certified Health IT (health IT accreditation and certification registers)	standard	47.2	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 6

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.

HL7 FHIR

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

Model Context Protocol (MCP)

measured — observed by APIs.io (verified)

OAuth 2.0 Protected Resource Metadata

measured — observed by APIs.io (verified)

Dynamic Client Registration

measured — observed by APIs.io (published)

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

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 4

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Client Webhook API

OPEN COLLECTION

bwell User Data Operations

OPEN COLLECTION

bwell User Data Operations Users API

OPEN COLLECTION

Client Webhook API

OPEN COLLECTION

MCP 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 SERVER

Agent Skills 5

Packaged agent skills for driving this provider's APIs from an AI assistant.

Answer a patient's insurance question

AGENT SKILL

Find a provider and book an appointment

AGENT SKILL

Connect a patient to a health data source

AGENT SKILL

Honor a user's data export or deletion request

AGENT SKILL

Retrieve a patient's health records

AGENT SKILL

b.well API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

B Well Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

B Well Rate Limits

0 limits

RATE LIMITS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

b.well

SLA

FinOps 1

Cost, billing, and metering signals for API financial operations.

B Well Finops

FINOPS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

B Well Webhooks

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

b.well API Rules

50 rules · 48 errors 1 warnings 1 info

SPECTRAL

OpenAPI 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

3 actions · documentation · b-well-client-webhook-api-openapi.json

DERIVED

B Well User Data Operations Overlay

4 actions · documentation · b-well-user-data-operations-openapi.json

DERIVED

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

B Well Authentication

oauth2/apiKey · 7 schemes

SECURITY

B Well Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

B Well Vulnerability Disclosure

security.txt · contact published

SECURITY

B Well Trust Center

HITRUST, NIST Cybersecurity Framework (CSF), HIPAA

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

B Well Scopes

4 scopes · authorizationCode/clientCredentials

4 scopes

SCOPES

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

B Well Agentic Access

3 operations · 3 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Login

Sandbox

Sandbox

Documentation 3

Reference material describing how the API behaves

ContributionGuide

ContributionGuide

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

WellKnown

LLMsTxt

MCPServer

AgentSkill

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Lifecycle

Conformance

ErrorCatalog

Conventions

Components

DataModel

Webhooks

Scroll for all 7

Build 4

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

Packages

SDKs

ToolCrosswalk

Access & Security 8

Authentication, authorization, and security posture

Authentication

OAuthScopes

SecurityTxt

Security

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

TrustCenter

TrustCenter

Compliance

Compliance

Scroll for all 8

Operate 5

Status, limits, changes, and where to get help

Releases

Support

StatusPage

ChangeLog

RateLimits

Commercial 4

Pricing, plans, and the legal terms of use

License

TermsOfService

PrivacyPolicy

Plans

Company 4

The organization behind the API

Blog

BlogRSS

Website

Blog

Other 1

Properties that don't map to a standard resource type

Overlay

Overlay

Source (apis.yml)

aid: b-well
name: b.well
description: 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.
url: https://raw.githubusercontent.com/api-evangelist/b-well/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
deliveryModel:
  model: open-core
  license: MIT
  open_source: true
  commercial: true
  callable_host: true
  label: Open core · an OSS project plus a commercial hosted product
  confidence: high
  source:
  - license
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  - scopes
  - rate-limits
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
specificationVersion: '0.23'
created: '2026-08-06'
modified: '2026-10-06'
image: https://www.icanbwell.com/wp-content/uploads/2023/01/bwell-logo.png
x-docs-platform: readme
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-09-19
tags:
- Company
- Health
- Healthcare
- Digital Health
- FHIR
- Health Data
- Interoperability
- Patient Access
- Health Records
- MCP
tags_raw:
- Company
- Health
- Healthcare
- Digital Health
- FHIR
- Health Data
- Interoperability
- Patient Access
- Health Records
- Model Context Protocol
apis:
- aid: b-well:application-apis
  name: b.well Application APIs
  description: 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 coordinate care workflows in an end-user OAuth context.
  humanURL: https://developer.bwell.com/docs/app-apis-overview
  baseURL: https://api.client-sandbox.icanbwell.com/v1
  tags:
  - Health Data
  - GraphQL
  - FHIR
  properties:
  - type: Documentation
    url: https://developer.bwell.com/docs/app-apis-overview
  - type: GraphQL
    url: https://api.client-sandbox.icanbwell.com/v1/graphql
  - type: Console
    url: https://icanbwell.github.io/graphql-doc-site/
  - type: Authentication
    url: https://developer.bwell.com/docs/end-user-auth
- aid: b-well:fhir-server
  name: b.well FHIR Server
  description: 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 retrieval, International Patient Summary generation,
    and paging vs streaming responses. Authenticated with OAuth 2.0 client credentials.
  humanURL: https://developer.bwell.com/docs/fhirserver-overview
  baseURL: https://fhir.icanbwell.com
  tags:
  - FHIR
  - Health Records
  - Interoperability
  properties:
  - type: Documentation
    url: https://developer.bwell.com/docs/fhirserver-overview
  - type: SourceCode
    url: https://github.com/icanbwell/fhir-server
  - type: WellKnown
    url: well-known/b-well-smart-configuration.json
- aid: b-well:health-sdk-for-ai-mcp
  name: b.well Health SDK for AI (MCP Server)
  description: 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, provider search, appointment scheduling and prescription
    transfer — to MCP-compatible LLM clients (OpenAI, Anthropic, Google). Every call runs in an authorized end-user context.
  humanURL: https://developer.bwell.com/docs/aisdk-overview
  baseURL: https://api.client-sandbox.icanbwell.com/mcp/
  tags:
  - MCP
  - Artificial Intelligence
  - Health Data
  tags_raw:
  - Model Context Protocol
  - AI
  - Health Data
  properties:
  - type: MCPServer
    url: mcp/b-well-mcp.yml
  - type: ToolCrosswalk
    url: mcp/b-well-tool-crosswalk.yml
  - type: Documentation
    url: https://developer.bwell.com/docs/aisdk-overview
- aid: b-well:b-well-users-api
  name: b.well Users API
  description: The Users API from b.well — 2 operation(s) for users.
  humanURL: https://developer.bwell.com/docs/app-apis-overview
  baseURL: https://api.client-sandbox.icanbwell.com/v1
  tags:
  - User
  tags_raw:
  - Users
  properties:
  - type: OpenAPI
    url: openapi/b-well-users-api-openapi.yml
  - type: APIReference
    url: https://developer.bwell.com/reference/post_users-id-data-exports
  - type: PostmanCollection
    url: collections/b-well-users-api.postman_collection.json
  - type: OpenCollection
    url: collections/b-well-users-api.opencollection.json
  - type: Webhooks
    url: asyncapi/b-well-webhooks.yml
- aid: b-well:b-well-webhook-api
  name: b.well Webhook API
  description: The Webhook API from b.well — 1 operation(s) for webhook.
  humanURL: https://developer.bwell.com/docs/app-apis-overview
  baseURL: https://api.client-sandbox.icanbwell.com/v1
  tags:
  - Webhook
  properties:
  - type: OpenAPI
    url: openapi/b-well-webhook-api-openapi.yml
  - type: APIReference
    url: https://developer.bwell.com/reference/post_users-id-data-exports
  - type: PostmanCollection
    url: collections/b-well-webhook-api.postman_collection.json
  - type: OpenCollection
    url: collections/b-well-webhook-api.opencollection.json
  - type: Webhooks
    url: asyncapi/b-well-webhooks.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- url: https://resources.icanbwell.com/resource-type/blog/
  type: Blog
- url: https://resources.icanbwell.com/feed/
  type: BlogRSS
- type: Overlay
  url: overlays/b-well-client-webhook-api-overlay.yaml
- type: Releases
  url: https://github.com/icanbwell/fhir-server/releases
- type: ContributionGuide
  url: https://github.com/icanbwell/fhir-server/blob/main/CONTRIBUTING.md
- type: License
  name: MIT
  url: https://github.com/icanbwell/fhir-server/blob/main/LICENSE
- type: AgenticAccess
  url: agentic-access/b-well-agentic-access.yml
- type: Website
  url: https://www.icanbwell.com/
- type: DeveloperPortal
  url: https://developer.bwell.com/
- type: Documentation
  url: https://developer.bwell.com/docs/welcome
- type: APIReference
  url: https://developer.bwell.com/reference/ts-sdk-apireference
- type: GettingStarted
  url: https://developer.bwell.com/docs/welcome
- type: Authentication
  url: authentication/b-well-authentication.yml
- type: OAuthScopes
  url: scopes/b-well-scopes.yml
- type: Support
  url: mailto:support@icanbwell.com
- type: Blog
  url: https://resources.icanbwell.com/
- type: GitHubOrganization
  url: https://github.com/icanbwell
- type: Login
  url: https://developer.bwell.com/login
- type: TermsOfService
  url: https://www.icanbwell.com/legal/terms-of-service/
- type: PrivacyPolicy
  url: https://www.icanbwell.com/legal/privacy-policy/
- type: StatusPage
  url: https://status.bwell.com
- type: ChangeLog
  url: changelog/b-well-changelog.yml
- type: Lifecycle
  url: lifecycle/b-well-lifecycle.yml
- type: Packages
  url: packages/b-well-packages.yml
- type: SDKs
  url: packages/b-well-packages.yml
- type: WellKnown
  url: well-known/b-well-well-known.yml
- type: SecurityTxt
  url: well-known/b-well-security.txt
- type: Security
  url: https://www.icanbwell.com/.well-known/security.txt
- type: VulnerabilityDisclosure
  url: security/b-well-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/b-well-domain-security.yml
- type: LLMsTxt
  url: llms/b-well-llms.txt
- type: MCPServer
  url: mcp/b-well-mcp.yml
- type: ToolCrosswalk
  url: mcp/b-well-tool-crosswalk.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Conformance
  url: conformance/b-well-conformance.yml
- type: ErrorCatalog
  url: errors/b-well-problem-types.yml
- type: Conventions
  url: conventions/b-well-conventions.yml
- type: Sandbox
  url: sandbox/b-well-sandbox.yml
- type: Components
  url: components/b-well-components.yml
- type: DataModel
  url: data-model/b-well-data-model.yml
- type: Webhooks
  url: asyncapi/b-well-webhooks.yml
- type: Plans
  url: plans/b-well-plans-pricing.yml
- type: RateLimits
  url: rate-limits/b-well-rate-limits.yml
- type: TrustCenter
  url: security/b-well-trust-center.yml
- type: Compliance
  url: security/b-well-trust-center.yml
x-enrichment:
  date: '2026-08-15'
  status: enriched
  artifacts_added: 3
  pass: local-v1

b.well API — frequently asked questions

Does b.well have an API?

Yes. APIs.io lists 5 APIs from b.well, including b.well Application APIs, b.well FHIR Server and b.well Health SDK for AI (MCP Server), and 2 more.

Is there an OpenAPI specification for the b.well API?

Yes. APIs.io indexes 2 OpenAPI specifications for b.well, each linked for download from this page.

How do I authenticate with the b.well API?

b.well documents its authentication (oauth2/apiKey · 7 schemes). The details are profiled on APIs.io as B Well Authentication.

Does b.well have an MCP server?

Yes. APIs.io lists 1 MCP server for b.well: Remote MCP server at api.client-sandbox.icanbwell.com over HTTP; 31 tools listed.

Is the b.well API ready for AI agents?

b.well has a Kin Score of 58.2 out of 100 (strong) and an Agent Readiness score of 58.6 (agent-ready), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/b-well"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/b-well/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/b-well/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.