Metriport

Metriport is an open-source, universal API for healthcare data. The Medical API exchanges patient medical records across the CommonWell and Carequality networks and returns consolidated FHIR R4 data, while the Devices API hydrates activity, biometrics, nutrition, and sleep data from consumer wearables and mHealth apps. Companies can use the hosted Metriport cloud or self-host the open-source code to avoid vendor lock-in.

Metriport publishes 7 API contracts indexed on the APIs.io network, including Consolidated API, Devices Data API, Document API, and 4 more. Tagged areas include Healthcare, Medical Records, FHIR, Health Data, and Wearables.

The Metriport catalog on APIs.io includes 1 event-driven AsyncAPI specification, 1 JSON-LD context, and 1 Spectral governance ruleset.

Metriport’s developer surface includes authentication, documentation, engineering blog, sandbox, getting-started guide, API reference, support, and 40 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

63.9/100 strong ▬ flat Agent 33/100 agent ready Front door AI 4/6 moderate Heartbeat 83/100 alive Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessPaid

1 published contract 1 MCP Servers 4 Agent Skills

Healthcare Medical Records FHIR Health Data Wearables Open Source A2A

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Health Information Management

BC-2900

ConsolidatedDocument

POST /medical/v1/patient/{id}/consolidated/query POST /medical/v1/document/query

Kin Score

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

Composite quality — 63.9/100 · strong

Contract Quality 13.1 / 19

Developer Ergonomics 10.7 / 15

Access Clarity 5.5 / 15

Operational Transparency 5.9 / 10

Contract Governance 3.2 / 9

Discoverability 5.7 / 8

Regulatory Posture 4.8 / 15

Create-or-Update Ergonomics 2.8 / 10

Agent readiness — 33/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 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

Pagination 0 / 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.

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 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% 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/metriport/"><img src="https://apis.io/badge/metriport/card.svg" alt="Metriport 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
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
Documented Reversibility +6 pts — a reversal operation in the contract, graded up when a window is documented too

6 more unmet checks in the Agent Readiness table above.

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

Access Clarity scores 36.8 — up to +12.6 composite points
Contract Governance scores 35.6 — up to +7.7 composite points
Contract Quality scores 69.9 — up to +7.5 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/metriport/apis.yml: open an issue on github.com/api-evangelist/metriport 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
Healthcare (FHIR)	standard	44.1	-	1
Health and Wellness (consumer health, fitness, wearables)	standard	44.1	-	1
FHIR Implementation Guides (HL7 FHIR package and IG publishers)	standard	44.1	-	1

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 5

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.

Agent2Agent

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

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 (platform)

Agent Skills

measured — observed by APIs.io (published)

OpenAPI

measured — observed by APIs.io (published)

APIs 7

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

Metriport Consolidated API

Medical API consolidated FHIR data.

Metriport Devices Data API

Devices API normalized health data.

Metriport Document API

Medical API clinical document query and retrieval.

Metriport Facility API

Medical API facility management.

Metriport Patient API

Medical API patient management.

Metriport Settings API

Account settings and webhooks.

Metriport User API

Devices API user and connect management.

Arazzo Workflows 4

Multi-step API workflows described with the Arazzo specification.

Metriport Consolidated FHIR Query

Register a patient, start a consolidated FHIR R4 query for the requested resources, poll until conversion completes, then count the consolidated data.

ARAZZO

Metriport Patient Document Retrieval

Register a patient, trigger an IHE document query across the networks, poll until retrieval completes, list the resulting documents, and obtain a signed download URL.

ARAZZO

Metriport Patient Matching

Create a facility, register a patient under it, then run an MPI demographic match to resolve an existing patient record.

ARAZZO

Metriport Wearables Connect

Create a devices user, mint a Connect Widget session token, then pull the user's activity and biometrics data from connected wearables.

ARAZZO

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Metriport MCP Server

Metriport serves a remote MCP endpoint from its documentation host. A tools/list POST returns HTTP 200 anonymously with three real tools and their inputSchemas — captured verbat...

Rate limits

Patient Create: 15 requests
Patient Update: 15 requests
Document Query Start (Legacy): 20 requests

All 10 limits →

Pricing Plans 1

Published pricing tiers and plan structures.

Metriport Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Metriport Rate Limits

10 limits

RATE LIMITS

Service Levels 1

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

Metriport

SLA

FinOps 1

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

Metriport Finops

FINOPS

Event Specifications 1

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

Metriport Webhooks

ASYNCAPI

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Metriport Context

11 classes · 46 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Metriport API Rules

15 rules · 12 errors 1 warnings 2 info

SPECTRAL

OpenAPI Overlays 7

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.

Metriport Consolidated Api Overlay

2 actions · update · metriport-consolidated-api-openapi.yml

DERIVED

Metriport Devices Data Api Overlay

9 properties

JSON SCHEMA

Settings

4 properties

JSON SCHEMA

Scroll for all 10

Security Posture 4

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

Metriport Authentication

apiKey · 1 scheme

SECURITY

Metriport Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Metriport Vulnerability Disclosure

Hackerone

SECURITY

Metriport Trust Center

SOC 2 Type II, HIPAA

SECURITY

Agentic Access 1

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

Metriport Agentic Access

30 operations · 13 acting · 1 human-in-the-loop

30 operations · 13 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

Sandbox

DeveloperPortal

GettingStarted

SignUp

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

WellKnown

MCPServer

AgentSkill

LLMsTxt

Design & Contract 11

Pagination, idempotency, versioning, errors, and events

Spectral

JSONLD

Vocabulary

Conformance

ErrorCatalog

Lifecycle

Conventions

Components

DataModel

Webhooks

Scroll for all 11

Build 6

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

Packages

SDKs

ToolCrosswalk

Postman

SourceCode

Access & Security 6

Authentication, authorization, and security posture

DomainSecurity

Authentication

Compliance

TrustCenter

VulnerabilityDisclosure

VulnerabilityDisclosure

Security

Security

Operate 3

Status, limits, changes, and where to get help

RateLimits

RateLimits

StatusPage

StatusPage

Support

Support

Commercial 3

Pricing, plans, and the legal terms of use

FinOps

FinOps

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 4

The organization behind the API

Newsroom

Newsroom

LinkedIn

Website

Website

Blog

Blog

Other 4

Properties that don't map to a standard resource type

Hosts

Vendors

CapabilityMap

AgentCard

Source (apis.yml)

aid: metriport
url: https://raw.githubusercontent.com/api-evangelist/metriport/refs/heads/main/apis.yml
name: Metriport
kind: company
description: Metriport is an open-source, universal API for healthcare data. The Medical API exchanges patient medical records
  across the CommonWell and Carequality networks and returns consolidated FHIR R4 data, while the Devices API hydrates activity,
  biometrics, nutrition, and sleep data from consumer wearables and mHealth apps. Companies can use the hosted Metriport cloud
  or self-host the open-source code to avoid vendor lock-in.
deliveryModel:
  model: unknown
  license_evidence:
    repo: metriport/metriport
    spdx: NOASSERTION
    stars: 784
  open_source: unknown
  commercial: true
  callable_host: true
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - openapi
  - pricing
  - repository-unlicensed
  generated: '2026-09-25'
  method: derived
accessModel:
  pricing: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: high
  source:
  - finops
  - authentication
  - rate-limits
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/metriport.png
x-docs-platform: mintlify
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-04
x-docs-hosting: vercel
tags:
- Healthcare
- Medical Records
- FHIR
- Health Data
- Wearables
- Open Source
- A2A
tags_raw:
- Healthcare
- Medical Records
- FHIR
- Health Data
- Wearables
- Open Source
- Open-Source
- A2A
created: '2026-06-21'
modified: '2026-08-14'
specificationVersion: '0.23'
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
common:
- type: Spectral
  url: rules/metriport-rules.yml
- type: JSONLD
  url: json-ld/metriport-context.jsonld
- type: Vocabulary
  url: vocabulary/metriport-vocabulary.yml
- type: Hosts
  url: hosts/metriport-hosts.yml
- type: Vendors
  url: vendors/metriport-vendors.yml
- type: Newsroom
  url: https://www.metriport.com/news
- type: CapabilityMap
  url: capabilities/metriport-capability-edges.yml
  name: Metriport Business Capability Map
- type: AgenticAccess
  url: agentic-access/metriport-agentic-access.yml
- type: DomainSecurity
  url: security/metriport-domain-security.yml
- type: Authentication
  url: authentication/metriport-authentication.yml
- type: GitHubOrganization
  url: https://github.com/metriport
- type: LinkedIn
  url: https://www.linkedin.com/company/metriport
- type: Website
  url: https://www.metriport.com
- type: Documentation
  url: https://docs.metriport.com
- type: RateLimits
  url: rate-limits/metriport-rate-limits.yml
- type: FinOps
  url: finops/metriport-finops.yml
- type: ArazzoWorkflows
  workflows:
  - url: arazzo/metriport-consolidated-fhir-query-workflow.yml
    name: Metriport Consolidated FHIR Query
    summary: Register a patient, start a consolidated FHIR R4 query for the requested resources, poll until conversion completes,
      then count the consolidated data.
  - url: arazzo/metriport-patient-document-retrieval-workflow.yml
    name: Metriport Patient Document Retrieval
    summary: Register a patient, trigger an IHE document query across the networks, poll until retrieval completes, list the
      resulting documents, and obtain a signed download URL.
  - url: arazzo/metriport-patient-matching-workflow.yml
    name: Metriport Patient Matching
    summary: Create a facility, register a patient under it, then run an MPI demographic match to resolve an existing patient
      record.
  - url: arazzo/metriport-wearables-connect-workflow.yml
    name: Metriport Wearables Connect
    summary: Create a devices user, mint a Connect Widget session token, then pull the user's activity and biometrics data
      from connected wearables.
- url: https://www.metriport.com/blog
  type: Blog
- type: Packages
  url: packages/metriport-packages.yml
- type: SDKs
  url: packages/metriport-packages.yml
- type: WellKnown
  url: well-known/metriport-well-known.yml
- type: MCPServer
  url: mcp/metriport-mcp.yml
- type: ToolCrosswalk
  url: mcp/metriport-tool-crosswalk.yml
- type: AgentCard
  url: a2a/metriport-a2a.yml
- type: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/metriport-llms.txt
- type: Conformance
  url: conformance/metriport-conformance.yml
- type: Compliance
  url: security/metriport-trust-center.yml
- type: TrustCenter
  url: security/metriport-trust-center.yml
- type: VulnerabilityDisclosure
  url: security/metriport-vulnerability-disclosure.yml
- type: Security
  url: security/metriport-vulnerability-disclosure.yml
- type: ErrorCatalog
  url: errors/metriport-problem-types.yml
- type: Lifecycle
  url: lifecycle/metriport-lifecycle.yml
- type: Conventions
  url: conventions/metriport-conventions.yml
- type: Sandbox
  url: sandbox/metriport-sandbox.yml
- type: Components
  url: components/metriport-components.yml
- type: DataModel
  url: data-model/metriport-data-model.yml
- type: Webhooks
  url: asyncapi/metriport-webhooks.yml
- type: StatusPage
  url: https://status.metriport.com
- type: DeveloperPortal
  url: https://dash.metriport.com/developers
- type: GettingStarted
  url: https://docs.metriport.com/medical-api/getting-started/quickstart
- type: APIReference
  url: https://docs.metriport.com/medical-api/api-reference/patient/create-patient
- type: Support
  url: https://www.metriport.com/contact-us
- type: SignUp
  url: https://dash.metriport.com
- type: TermsOfService
  url: https://www.metriport.com/terms
- type: PrivacyPolicy
  url: https://www.metriport.com/privacy-policy
- type: Postman
  url: https://www.postman.com/metriport/metriport-api/folder/7zl228v/medical
- type: SourceCode
  url: https://github.com/metriport/metriport
apis:
- aid: metriport:metriport-consolidated-api
  name: Metriport Consolidated API
  description: Medical API consolidated FHIR data.
  humanURL: https://docs.metriport.com/medical-api/api-reference/patient/create-patient
  baseURL: https://api.metriport.com/medical/v1
  tags:
  - Consolidated
  properties:
  - type: OpenAPI
    url: openapi/metriport-consolidated-api-openapi.yml
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/patient/create-patient
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/patient/create-patient
  - type: PostmanCollection
    url: collections/metriport.postman_collection.json
  - type: OpenCollection
    url: collections/metriport.opencollection.json
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/facility/create-facility
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/facility/create-facility
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/document/list-documents
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/document/list-documents
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/fhir/consolidated-data-query-post
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/fhir/consolidated-data-query-post
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/settings/get-settings
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/settings/get-settings
  - type: Overlay
    url: overlays/metriport-consolidated-api-overlay.yaml
  - type: JSONSchema
    url: json-schema/metriport-consolidated-query-schema.json
- aid: metriport:metriport-devices-data-api
  name: Metriport Devices Data API
  description: Devices API normalized health data.
  humanURL: https://docs.metriport.com/medical-api/api-reference/patient/create-patient
  baseURL: https://api.metriport.com/medical/v1
  tags:
  - Devices Data
  properties:
  - type: OpenAPI
    url: openapi/metriport-devices-data-api-openapi.yml
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/patient/create-patient
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/patient/create-patient
  - type: PostmanCollection
    url: collections/metriport.postman_collection.json
  - type: OpenCollection
    url: collections/metriport.opencollection.json
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/facility/create-facility
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/facility/create-facility
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/document/list-documents
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/document/list-documents
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/fhir/consolidated-data-query-post
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/fhir/consolidated-data-query-post
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/settings/get-settings
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/settings/get-settings
  - type: Overlay
    url: overlays/metriport-devices-data-api-overlay.yaml
  - type: JSONSchema
    url: json-schema/metriport-devices-data-schema.json
- aid: metriport:metriport-document-api
  name: Metriport Document API
  description: Medical API clinical document query and retrieval.
  humanURL: https://docs.metriport.com/medical-api/api-reference/patient/create-patient
  baseURL: https://api.metriport.com/medical/v1
  tags:
  - Documents
  tags_raw:
  - Document
  properties:
  - type: OpenAPI
    url: openapi/metriport-document-api-openapi.yml
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/patient/create-patient
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/patient/create-patient
  - type: PostmanCollection
    url: collections/metriport.postman_collection.json
  - type: OpenCollection
    url: collections/metriport.opencollection.json
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/facility/create-facility
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/facility/create-facility
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/document/list-documents
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/document/list-documents
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/fhir/consolidated-data-query-post
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/fhir/consolidated-data-query-post
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/settings/get-settings
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/settings/get-settings
  - type: Overlay
    url: overlays/metriport-document-api-overlay.yaml
  - type: JSONSchema
    url: json-schema/metriport-document-reference-schema.json
  - type: JSONSchema
    url: json-schema/metriport-document-query-schema.json
- aid: metriport:metriport-facility-api
  name: Metriport Facility API
  description: Medical API facility management.
  humanURL: https://docs.metriport.com/medical-api/api-reference/patient/create-patient
  baseURL: https://api.metriport.com/medical/v1
  tags:
  - Facilities
  tags_raw:
  - Facility
  properties:
  - type: OpenAPI
    url: openapi/metriport-facility-api-openapi.yml
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/patient/create-patient
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/patient/create-patient
  - type: PostmanCollection
    url: collections/metriport.postman_collection.json
  - type: OpenCollection
    url: collections/metriport.opencollection.json
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/facility/create-facility
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/facility/create-facility
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/document/list-documents
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/document/list-documents
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/fhir/consolidated-data-query-post
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/fhir/consolidated-data-query-post
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/settings/get-settings
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/settings/get-settings
  - type: Overlay
    url: overlays/metriport-facility-api-overlay.yaml
  - type: JSONSchema
    url: json-schema/metriport-base-facility-schema.json
  - type: JSONSchema
    url: json-schema/metriport-facility-schema.json
- aid: metriport:metriport-patient-api
  name: Metriport Patient API
  description: Medical API patient management.
  humanURL: https://docs.metriport.com/medical-api/api-reference/patient/create-patient
  baseURL: https://api.metriport.com/medical/v1
  tags:
  - Patients
  tags_raw:
  - Patient
  properties:
  - type: OpenAPI
    url: openapi/metriport-patient-api-openapi.yml
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/patient/create-patient
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/patient/create-patient
  - type: PostmanCollection
    url: collections/metriport.postman_collection.json
  - type: OpenCollection
    url: collections/metriport.opencollection.json
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/facility/create-facility
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/facility/create-facility
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/document/list-documents
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/document/list-documents
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/fhir/consolidated-data-query-post
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/fhir/consolidated-data-query-post
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/settings/get-settings
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/settings/get-settings
  - type: Overlay
    url: overlays/metriport-patient-api-overlay.yaml
  - type: JSONSchema
    url: json-schema/metriport-base-patient-schema.json
  - type: JSONSchema
    url: json-schema/metriport-patient-schema.json
- aid: metriport:metriport-settings-api
  name: Metriport Settings API
  description: Account settings and webhooks.
  humanURL: https://docs.metriport.com/medical-api/api-reference/patient/create-patient
  baseURL: https://api.metriport.com/medical/v1
  tags:
  - Settings
  properties:
  - type: OpenAPI
    url: openapi/metriport-settings-api-openapi.yml
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/patient/create-patient
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/patient/create-patient
  - type: PostmanCollection
    url: collections/metriport.postman_collection.json
  - type: OpenCollection
    url: collections/metriport.opencollection.json
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/facility/create-facility
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/facility/create-facility
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/document/list-documents
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/document/list-documents
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/fhir/consolidated-data-query-post
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/fhir/consolidated-data-query-post
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/settings/get-settings
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/settings/get-settings
  - type: Overlay
    url: overlays/metriport-settings-api-overlay.yaml
  - type: JSONSchema
    url: json-schema/metriport-settings-schema.json
- aid: metriport:metriport-user-api
  name: Metriport User API
  description: Devices API user and connect management.
  humanURL: https://docs.metriport.com/medical-api/api-reference/patient/create-patient
  baseURL: https://api.metriport.com/medical/v1
  tags:
  - User
  properties:
  - type: OpenAPI
    url: openapi/metriport-user-api-openapi.yml
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/patient/create-patient
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/patient/create-patient
  - type: PostmanCollection
    url: collections/metriport.postman_collection.json
  - type: OpenCollection
    url: collections/metriport.opencollection.json
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/facility/create-facility
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/facility/create-facility
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/document/list-documents
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/document/list-documents
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/fhir/consolidated-data-query-post
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/fhir/consolidated-data-query-post
  - type: Documentation
    url: https://docs.metriport.com/medical-api/api-reference/settings/get-settings
  - type: APIReference
    url: https://docs.metriport.com/medical-api/api-reference/settings/get-settings
  - type: Overlay
    url: overlays/metriport-user-api-overlay.yaml
  - type: JSONSchema
    url: json-schema/metriport-devices-user-schema.json
x-a2a:
  verified: true
  probed: '2026-09-26'
  url: https://docs.metriport.com/.well-known/agent-card.json
  grade: conformant
  protocol_version: '0.3'
  control: 404
x-enrichment:
  date: '2026-10-12'
  status: enriched
  artifacts_added: 3
  pass: local-v5

Metriport API — frequently asked questions

Does Metriport have an API?

Yes. APIs.io lists 7 APIs from Metriport, including Metriport Consolidated API, Metriport Devices Data API and Metriport Document API, and 4 more.

Is there an OpenAPI specification for the Metriport API?

Yes. APIs.io indexes 7 OpenAPI specifications for Metriport, each linked for download from this page.

How do I authenticate with the Metriport API?

Metriport uses bearer-token authentication (apiKey · 1 scheme). The details are profiled on APIs.io as Metriport Authentication.

Does Metriport have an MCP server?

Yes. APIs.io lists 1 MCP server for Metriport: Metriport serves a remote MCP endpoint from its documentation host. A tools/list POST returns HTTP 200 anonymously with three real tools and their inputSchemas — captured verbatim in metriport-mcp-too

Is the Metriport API ready for AI agents?

Metriport has a Kin Score of 63.9 out of 100 (strong) and an Agent Readiness score of 33.0 (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/metriport"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/metriport/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.