# 1upHealth vs Metriport Medical API

> Metriport Medical scores 50.1 (D) to 1upHealth's 46.8 (D) for patient record retrieval. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/1uphealth-vs-metriport
- Markdown: https://www.anchorterminal.com/compare/1uphealth-vs-metriport.md (~2,400 tokens)
- Slim: https://www.anchorterminal.com/compare/1uphealth-vs-metriport.min.md (~680 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/1uphealth-vs-metriport.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-14

Metriport Medical API scores 50.1 (D) on agent readiness against 1upHealth's 46.8 (D), and leads in 3 of 7 scored categories. 1upHealth leads on reliability, security & auth, payments & pricing and transparency & trust. Both do patient record retrieval.

- 1upHealth: grade D, 46.8/100, rank #903 of 1076. Markdown https://www.anchorterminal.com/tools/1uphealth.md · JSON https://www.anchorterminal.com/api/v1/tools/1uphealth.json
- Metriport Medical API: grade D, 50.1/100, rank #833 of 1076. Markdown https://www.anchorterminal.com/tools/metriport.md · JSON https://www.anchorterminal.com/api/v1/tools/metriport.json
- Best health record and wellness data APIs for AI agents: https://www.anchorterminal.com/best/health-data/index.md
- All 63 health comparisons: https://www.anchorterminal.com/compare/health-data/index.md

## Which one, for what

### 1upHealth (D)

Good for: Consumer and care apps that read a member's health plan claims and clinical data under the CMS rules, and payers meeting those rules.

Ahead on:
- Reliability, 52 against 45
- Security & auth, 63 against 41
- Payments & pricing, 20 against 5
- Transparency & trust, 72 against 56

Watch for: No rate limits, 429 handling or error formats documented

### Metriport Medical API (D)

Good for: US care providers and digital health companies that need a patient's network records as FHIR with webhooks.

Ahead on:
- Schema & documentation, 65 against 50
- Agent ergonomics, 70 against 32
- Maintenance & community, 74 against 37

Also in its favour:
- Open source

Watch for: Every API key has full access, including destructive operations, with no scopes


## Score by category

| Category | Weight | 1upHealth | Metriport Medical API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 52 | 45 | 1upHealth +7 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 50 | 65 | Metriport Medical API +15 |
| Agent ergonomics | 13% (16.2 this run) | 32 | 70 | Metriport Medical API +38 |
| Security & auth | 14% (17.5 this run) | 63 | 41 | 1upHealth +22 |
| Payments & pricing | 10% (12.5 this run) | 20 | 5 | 1upHealth +15 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 37 | 74 | Metriport Medical API +37 |
| Transparency & trust | 7% (8.8 this run) | 72 | 56 | 1upHealth +16 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **46.8 · D** | **50.1 · D** | |

## Facts side by side

| Fact | 1upHealth | Metriport Medical API |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | 1upHealth, Inc. | Metriport Inc. |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | HTTP | HTTP |
| Auth | OAuth | API key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | Proprietary service under 1upHealth's Terms of Service (effective 1 August 2024) | Proprietary hosted service under Metriport's terms of use. The source in metriport/metriport is AGPLv3, with an enterprise directory under its own licence, and the @metriport/api-sdk package on npm is MIT |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | none | 2026-09-28 |
| Terms last updated | no date given | 2024-01-01 |
| Privacy policy last updated | 2026-06-25 | 2023-02-21 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 793 stars, 28k npm/wk |

## Verdicts

**1upHealth.** Self-serve Dev Portal sandbox clients and a demo health plan let an app test the CMS Patient Access, Provider Access and Payer-to-Payer FHIR APIs, backed by HITRUST and SOC 2 Type 2. No rate limits, error formats or dated releases are documented, and the Patient Access OAuth step needs the member in a browser.

**Metriport Medical API.** One network query pulls a patient's records from HIEs, pharmacies and labs and returns deduplicated FHIR, with per-operation rate limits, RFC 7807 errors and AGPLv3 source. Each API key has full access with no scopes, there are no public prices, and the sandbox opens only after Metriport approves the account.

## Before you call either

### 1upHealth

1. Hand the Patient Access sign-in to the member, who must authorise in the health plan's auth app
2. Exchange the authorisation code within five minutes, and refresh before the 15-minute token expires
3. Email payer-patient-access@1up.health with the client ID to get the app synced to the demo environment
4. Expect only claims and coverage resources from some payers, and read /r4/metadata first

### Metriport Medical API

1. Check the `errors` array after Start Network Query. It returns 2XX even when some sources fail
2. Wait for `network-query.*` webhooks or poll Get Network Query Status before reading consolidated data, which is cached from the last query
3. Send the resource's `eTag` in `If-Match` on updates to avoid overwriting newer data
4. Keep patient creates under 15 a minute and network queries under 20 a minute per source
5. In sandbox, create patients whose first name matches a pre-defined persona to get example records

## Questions

### Which is better for AI agents, 1upHealth or Metriport Medical API?

Metriport Medical API scores 50.1 (D) on agent readiness against 1upHealth's 46.8 (D), and leads in 3 of 7 scored categories. 1upHealth leads on reliability, security & auth, payments & pricing and transparency & trust.

### Do 1upHealth and Metriport Medical API need an API key?

1upHealth uses an OAuth sign-in. Metriport Medical API needs an API key.

### Can an agent call 1upHealth and Metriport Medical API without installing anything?

No hosted endpoint is listed for 1upHealth. No hosted endpoint is listed for Metriport Medical API.

### Are 1upHealth and Metriport Medical API open source?

No open-source release is listed for 1upHealth. Metriport Medical API is open source (Proprietary hosted service under Metriport's terms of use. The source in metriport/metriport is AGPLv3, with an enterprise directory under its own licence, and the @metriport/api-sdk package on npm is MIT).


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/1uphealth-vs-metriport.json, and with the fewest tokens: https://www.anchorterminal.com/compare/1uphealth-vs-metriport.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "1uphealth", "b": "metriport"}`. From a terminal: `anchor compare 1uphealth metriport`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/1uphealth.json and https://www.anchorterminal.com/api/v1/tools/metriport.json

## Other comparisons with 1upHealth or Metriport Medical API

- [1upHealth vs ROOK](https://www.anchorterminal.com/compare/1uphealth-vs-rook.md)
- [1upHealth vs Terra API](https://www.anchorterminal.com/compare/1uphealth-vs-terra.md)
- [Aidbox vs Metriport Medical API](https://www.anchorterminal.com/compare/aidbox-vs-metriport.md)
- [Medplum vs Metriport Medical API](https://www.anchorterminal.com/compare/medplum-vs-metriport.md)
- [Metriport Medical API vs ROOK](https://www.anchorterminal.com/compare/metriport-vs-rook.md)
- [Metriport Medical API vs Terra API](https://www.anchorterminal.com/compare/metriport-vs-terra.md)
- [1upHealth vs Aidbox](https://www.anchorterminal.com/compare/1uphealth-vs-aidbox.md)
- [1upHealth vs Health Gorilla](https://www.anchorterminal.com/compare/1uphealth-vs-health-gorilla.md)
- [1upHealth vs Medblocks](https://www.anchorterminal.com/compare/1uphealth-vs-medblocks.md)
- [1upHealth vs Medplum](https://www.anchorterminal.com/compare/1uphealth-vs-medplum.md)
- [1upHealth vs Particle Health](https://www.anchorterminal.com/compare/1uphealth-vs-particle-health.md)
- [1upHealth vs Redox](https://www.anchorterminal.com/compare/1uphealth-vs-redox.md)
- [1upHealth vs Zus Health](https://www.anchorterminal.com/compare/1uphealth-vs-zus-health.md)
- [Health Gorilla vs Metriport Medical API](https://www.anchorterminal.com/compare/health-gorilla-vs-metriport.md)
- [Medblocks vs Metriport Medical API](https://www.anchorterminal.com/compare/medblocks-vs-metriport.md)
- [Metriport Medical API vs Particle Health](https://www.anchorterminal.com/compare/metriport-vs-particle-health.md)
- [Metriport Medical API vs Redox](https://www.anchorterminal.com/compare/metriport-vs-redox.md)
- [Metriport Medical API vs Zus Health](https://www.anchorterminal.com/compare/metriport-vs-zus-health.md)
- [1upHealth vs Validic Inform](https://www.anchorterminal.com/compare/1uphealth-vs-validic.md)
- [Metriport Medical API vs Validic Inform](https://www.anchorterminal.com/compare/metriport-vs-validic.md)