1upHealth

1upHealth is a US healthcare data interoperability company, founded in 2017 and headquartered in Boston, Massachusetts, that operates an HL7 FHIR-first health data platform for claims and clinical data acquisition, exchange, and compute. Built on a lakehouse architecture, the platform lets health plans, providers, and digital health developers ingest, normalize, store, and query patient and member data as FHIR, and ships modular solutions aligned to US federal interoperability mandates - Patient Access, Provider Access, Payer-to-Payer Data Exchange, Provider Directory, Formulary, and Electronic Prior Authorization (CMS Interoperability & Prior Authorization, CMS-0057-F). 1upHealth runs a managed, HIPAA-compliant FHIR REST API cloud server exposing FHIR R4 (4.0.1), STU3 (3.0.2), and DSTU2 (1.0.2) endpoints, each publishing a live CapabilityStatement, secured with SMART-on-FHIR OAuth 2.0. The company is HITRUST, SOC 2, and HIPAA aligned. Home market is the United States. Developer documentation is public at docs.1up.health, while provisioning API credentials and the developer console require an account (gated self-serve / partner onboarding).

1upHealth publishes 10 APIs on the APIs.io network. Tagged areas include Healthcare, United States, FHIR, HL7, and Interoperability.

The 1upHealth catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 JSON-LD context.

1upHealth’s developer surface includes documentation, engineering blog, support, signup flow, API reference, getting-started guide, authentication, and 38 more developer resources.

🌐 Visit website 📡 Source on GitHub

75.7/100 exemplar ▬ flat Agent 29/100 agent ready saas Full breakdown ↓
scored 2026-09-06 · rubric v0.19.0

AccessEnterprise

10 APIs

Healthcare United States FHIR HL7 Interoperability SMART on FHIR Payer Claims Patient Access Health Data

Kin Score

Kin Score How this is scored →
scored 2026-09-06 · rubric v0.19.0

Composite quality — 75.7/100 · exemplar

Contract Quality 12.5 / 21

Developer Ergonomics 11.2 / 17

Access Clarity 15.2 / 17

Operational Transparency 9.3 / 11

Contract Governance 1.9 / 10

Discoverability 6.9 / 9

Regulatory Posture 11.4 / 15

Agent readiness — 29/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 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 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

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.

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

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 github.com/api-evangelist/1uphealth: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 10

Individual APIs this provider publishes, each with its own machine-readable definition.

GraphQL 1

GraphQL schemas published by this provider.

Rate Limits 1

Documented rate limits and quota policies.

1Uphealth Rate Limits

4 limits

RATE LIMITS

FinOps 1

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

Scopes 1

OAuth scopes governing access to this provider's APIs.

1Uphealth Scopes

1 scope · clientCredentials/authorizationCode

1 scopes

SCOPES

Resources

Get Started 5

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperConsole

SignUp

GettingStarted

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

X-MCPServerCandidate

X-MCPServerCandidate

AgentSkill

AgentSkill

WellKnown

WellKnown

Design & Contract 9

Pagination, idempotency, versioning, errors, and events

Conventions

Idempotency

Conformance

ErrorCatalog

Lifecycle

Webhooks

JSONLDContext

Components

DataModel

Scroll for all 9

Build 5

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

Postman

GitHub

Packages

SDKs

Access & Security 7

Authentication, authorization, and security posture

TrustCenter

DomainSecurity

TrustCenter

Security

Authentication

OAuthScopes

Compliance

Scroll for all 7

Operate 4

Status, limits, changes, and where to get help

StatusPage

Support

ChangeLog

RateLimits

Commercial 4

Pricing, plans, and the legal terms of use

TermsOfService

PrivacyPolicy

Plans

FinOps

Company 4

The organization behind the API

Website

Website

Blog

Blog

LinkedIn

BlogRSS

BlogRSS

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

aid: 1uphealth
url: https://raw.githubusercontent.com/api-evangelist/1uphealth/refs/heads/main/apis.yml
name: 1upHealth
kind: company
description: 1upHealth is a US healthcare data interoperability company, founded in 2017 and headquartered in Boston, Massachusetts,
  that operates an HL7 FHIR-first health data platform for claims and clinical data acquisition, exchange, and compute. Built
  on a lakehouse architecture, the platform lets health plans, providers, and digital health developers ingest, normalize,
  store, and query patient and member data as FHIR, and ships modular solutions aligned to US federal interoperability mandates
  - Patient Access, Provider Access, Payer-to-Payer Data Exchange, Provider Directory, Formulary, and Electronic Prior Authorization
  (CMS Interoperability & Prior Authorization, CMS-0057-F). 1upHealth runs a managed, HIPAA-compliant FHIR REST API cloud
  server exposing FHIR R4 (4.0.1), STU3 (3.0.2), and DSTU2 (1.0.2) endpoints, each publishing a live CapabilityStatement,
  secured with SMART-on-FHIR OAuth 2.0. The company is HITRUST, SOC 2, and HIPAA aligned. Home market is the United States.
  Developer documentation is public at docs.1up.health, while provisioning API credentials and the developer console require
  an account (gated self-serve / partner onboarding).
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: enterprise
  onboarding: gated
  trial: false
  try_now: false
  public: false
  label: Enterprise · Gated developer console (public docs)
  confidence: high
  source:
  - authentication
  - documentation
  generated: '2026-07-24'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Healthcare
- United States
- FHIR
- HL7
- Interoperability
- SMART on FHIR
- Payer
- Claims
- Patient Access
- Health Data
created: '2026-07-24'
modified: '2026-08-14'
specificationVersion: '0.23'
apis:
- aid: 1uphealth:1uphealth-fhir-r4-api
  name: 1up FHIR API (R4)
  description: 1upHealth's managed HL7 FHIR R4 (4.0.1) REST API cloud server, exposing 144 FHIR resource types with SMART-on-FHIR
    OAuth 2.0 security. Publishes a live CapabilityStatement at /fhir/r4/metadata.
  humanURL: https://docs.1up.health/docs/fhir-info
  baseURL: https://api.1up.health/fhir/r4
  tags:
  - FHIR
  - Healthcare
  - Interoperability
  properties:
  - type: CapabilityStatement
    url: fhir/1uphealth-fhir-r4-capabilitystatement.json
  - type: Documentation
    url: https://docs.1up.health/docs/fhir-info
  - type: Authentication
    url: https://auth.1up.health/oauth2/authorize/system
- aid: 1uphealth:1uphealth-fhir-stu3-api
  name: 1up FHIR API (STU3)
  description: 1upHealth's managed HL7 FHIR STU3 (3.0.2) REST API cloud server, exposing 117 FHIR resource types. Publishes
    a live CapabilityStatement at /fhir/stu3/metadata.
  humanURL: https://docs.1up.health/docs/fhir-info
  baseURL: https://api.1up.health/fhir/stu3
  tags:
  - FHIR
  - Healthcare
  - Interoperability
  properties:
  - type: CapabilityStatement
    url: fhir/1uphealth-fhir-stu3-capabilitystatement.json
  - type: Documentation
    url: https://docs.1up.health/docs/fhir-info
- aid: 1uphealth:1uphealth-fhir-dstu2-api
  name: 1up FHIR API (DSTU2)
  description: 1upHealth's managed HL7 FHIR DSTU2 (1.0.2) REST API cloud server, exposing 94 FHIR resource types. Publishes
    a live Conformance statement at /fhir/dstu2/metadata.
  humanURL: https://docs.1up.health/docs/fhir-info
  baseURL: https://api.1up.health/fhir/dstu2
  tags:
  - FHIR
  - Healthcare
  - Interoperability
  properties:
  - type: CapabilityStatement
    url: fhir/1uphealth-fhir-dstu2-conformance.json
  - type: Documentation
    url: https://docs.1up.health/docs/fhir-info
- aid: 1uphealth:1uphealth-patient-access-api
  name: 1up Patient Access API
  description: CMS Patient Access solution delivering member clinical and claims data to patient-authorized third-party apps
    over FHIR, aligned to the CARIN Blue Button and US Core implementation guides.
  humanURL: https://docs.1up.health/docs/patient-access
  baseURL: https://api.1up.health/fhir/r4
  tags:
  - Patient Access
  - FHIR
  - Payer
  properties:
  - type: Documentation
    url: https://docs.1up.health/docs/patient-access
  - type: CapabilityStatement
    url: fhir/1uphealth-fhir-r4-capabilitystatement.json
- aid: 1uphealth:1uphealth-provider-access-api
  name: 1up Provider Access API
  description: CMS Provider Access solution enabling payers to share member data with in-network providers over FHIR, aligned
    to the Da Vinci implementation guides.
  humanURL: https://docs.1up.health/docs/provider-access
  baseURL: https://api.1up.health/fhir/r4
  tags:
  - Provider Access
  - FHIR
  - Payer
  properties:
  - type: Documentation
    url: https://docs.1up.health/docs/provider-access
  - type: CapabilityStatement
    url: fhir/1uphealth-fhir-r4-capabilitystatement.json
- aid: 1uphealth:1uphealth-payer-to-payer-api
  name: 1up Payer-to-Payer Data Exchange API
  description: CMS Payer-to-Payer Data Exchange solution for sharing a member's historical clinical and claims data between
    health plans over FHIR when a member changes payers.
  humanURL: https://docs.1up.health/docs/payer-to-payer
  baseURL: https://api.1up.health/fhir/r4
  tags:
  - Payer to Payer
  - FHIR
  - Payer
  properties:
  - type: Documentation
    url: https://docs.1up.health/docs/payer-to-payer
  - type: CapabilityStatement
    url: fhir/1uphealth-fhir-r4-capabilitystatement.json
- aid: 1uphealth:1uphealth-provider-directory-api
  name: 1up Provider Directory API
  description: Publicly accessible FHIR Provider Directory publishing accurate provider and network listings, aligned to the
    Da Vinci PDEX Plan-Net implementation guide.
  humanURL: https://docs.1up.health/docs/provider-directory
  baseURL: https://api.1up.health/fhir/r4
  tags:
  - Provider Directory
  - FHIR
  - Payer
  properties:
  - type: Documentation
    url: https://docs.1up.health/docs/provider-directory
  - type: CapabilityStatement
    url: fhir/1uphealth-fhir-r4-capabilitystatement.json
- aid: 1uphealth:1uphealth-epa-api
  name: 1up Electronic Prior Authorization API
  description: CMS-0057-F Electronic Prior Authorization solution automating prior authorization submission and decisioning
    over FHIR, aligned to the Da Vinci PAS / DTR / CRD implementation guides.
  humanURL: https://docs.1up.health/docs/epa
  baseURL: https://api.1up.health/fhir/r4
  tags:
  - Prior Authorization
  - FHIR
  - Payer
  properties:
  - type: Documentation
    url: https://docs.1up.health/docs/epa
  - type: CapabilityStatement
    url: fhir/1uphealth-fhir-r4-capabilitystatement.json
- aid: 1uphealth:1uphealth-patient-connect-api
  name: 1up Patient Connect
  description: Connectivity solution that acquires patient-authorized clinical records from a national network of EHR/provider
    and payer connections and normalizes them into the 1up FHIR data store.
  humanURL: https://docs.1up.health/docs/patient-connect
  baseURL: https://api.1up.health/fhir/r4
  tags:
  - Patient Connect
  - FHIR
  - Interoperability
  properties:
  - type: Documentation
    url: https://docs.1up.health/docs/patient-connect
- aid: 1uphealth:1uphealth-population-connect-api
  name: 1up Population Connect (Bulk FHIR)
  description: Population-scale connectivity and Bulk Data (Flat FHIR) export solution for acquiring and computing over large
    member/patient populations as FHIR.
  humanURL: https://docs.1up.health/docs/pop-connect
  baseURL: https://api.1up.health/fhir/r4
  tags:
  - Bulk FHIR
  - Population
  - Interoperability
  properties:
  - type: Documentation
    url: https://docs.1up.health/docs/pop-connect
common:
- type: TrustCenter
  url: security/1uphealth-trust-center.yml
- type: DomainSecurity
  url: security/1uphealth-domain-security.yml
- type: Website
  url: https://1up.health/
- type: DeveloperPortal
  url: https://docs.1up.health/
- type: Documentation
  url: https://docs.1up.health/
- type: DeveloperConsole
  url: https://developer.1up.health/
- type: Blog
  url: https://1up.health/blog/
- type: StatusPage
  url: https://status.1up.health/
- type: TrustCenter
  url: https://trust.1up.health/
- type: Security
  url: https://trust.1up.health/
- type: Support
  url: https://1uphealth.my.site.com/
- type: SignUp
  url: https://app.1up.health/login
- type: GitHubOrganization
  url: https://github.com/1uphealth
- type: TermsOfService
  url: https://1up.health/terms-of-service/
- type: PrivacyPolicy
  url: https://1up.health/privacy-policy/
- type: APIReference
  url: https://docs.1up.health/help-center/Content/en-US/api-references/rest-api-reference.html
- type: GettingStarted
  url: https://docs.1up.health/docs/get-started/faq
- type: Postman
  url: https://docs.1up.health/help-center/Content/en-US/get-started/quick-start/postman.html
- type: Authentication
  url: authentication/1uphealth-authentication.yml
- type: OAuthScopes
  url: scopes/1uphealth-scopes.yml
- type: Conventions
  url: conventions/1uphealth-conventions.yml
- type: Idempotency
  url: conventions/1uphealth-conventions.yml
- type: Conformance
  url: conformance/1uphealth-conformance.yml
- type: Compliance
  url: https://trust.1up.health/
- type: ErrorCatalog
  url: errors/1uphealth-problem-types.yml
- type: Lifecycle
  url: lifecycle/1uphealth-lifecycle.yml
- type: ChangeLog
  url: changelog/1uphealth-changelog.yml
- type: LLMsTxt
  url: llms/1uphealth-llms.txt
- type: X-MCPServerCandidate
  url: mcp/1uphealth-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: AgentSkill
  url: skills/_index.yml
- type: Sandbox
  url: sandbox/1uphealth-sandbox.yml
- type: Webhooks
  url: asyncapi/1uphealth-subscription-webhooks.yml
- type: WellKnown
  url: well-known/1uphealth-well-known.yml
- type: GitHub
  url: https://github.com/1uphealth
- type: LinkedIn
  url: https://www.linkedin.com/company/1uphealth/
- type: X
  url: https://x.com/1up_health
- type: BlogRSS
  url: https://1up.health/blog/feed/
- type: JSONLDContext
  url: json-ld/1uphealth-context.jsonld
- type: Plans
  url: plans/1uphealth-plans-pricing.yml
- type: RateLimits
  url: rate-limits/1uphealth-rate-limits.yml
- type: FinOps
  url: finops/1uphealth-finops.yml
- type: Packages
  url: packages/1uphealth-packages.yml
- type: SDKs
  url: packages/1uphealth-packages.yml
- type: Components
  url: components/1uphealth-components.yml
- type: DataModel
  url: data-model/1uphealth-data-model.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
x-merged-from:
- 1up-health
x-enrichment:
  date: '2026-08-14'
  status: enriched
  artifacts_added: 3
  pass: local-v1

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/1uphealth"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/1uphealth/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

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