Head to head · Patient record retrieval · October 2026 research run

Metriport Medical API vs Redox

Redox scores 58.3 (C) on agent readiness against Metriport Medical API's 50.1 (D), and leads in 4 of 7 scored categories. Metriport Medical API leads on schema & documentation, agent ergonomics and maintenance & community. Both do patient record retrieval.

Best health record and wellness data APIs for AI agents · All 63 health comparisons

Which one, for what

Metriport Medical API D

Best 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 56
  • Agent ergonomics, 70 against 54
  • Maintenance & community, 74 against 31

Also in its favour

  • Open source

Watch for

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

Redox C

Best for Health software vendors integrating with many hospital EHRs and networks, and integration teams who want an agent to manage Redox configuration.

Ahead on

  • Reliability, 85 against 45
  • Security & auth, 78 against 41
  • Payments & pricing, 15 against 5

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

The MCP server loads 107 tools in one set, including write and delete tools with no confirmation step

Score by category

CategoryWeight this runMetriport Medical APIRedoxEdge
Reliability16%204585Redox +40
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26556Metriport Medical API +9
Agent ergonomics13%16.27054Metriport Medical API +16
Security & auth14%17.54178Redox +37
Payments & pricing10%12.5515Redox +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87431Metriport Medical API +43
Transparency & trust7%8.85659Redox +3
Negative events≤1500
TotalD 50.1/100C 58.3/100

Facts side by side

FactMetriport Medical APIRedox
KindHTTP APIHTTP API
VendorMetriport Inc.Redox, Inc.
Hosted endpointno (local only)https://api.redoxengine.com/mcp
TransportsHTTPHTTP
AuthAPI keyOAuth
PricingPaidPaid
x402nono
LicenceProprietary 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 MITProprietary service under Redox's Cloud Services Agreement, EULA and SLA (version 2016.1)
Tools exposednone107
Read-only variant documentednono
llms.txtyesno
Last release2026-09-28none
Terms last updated2024-01-012015-10-17
Privacy policy last updated2023-02-212023-01-18
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity793 stars, 28k npm/wknone

Verdicts

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.

Redox

Redox connects to EHRs and clinical networks behind a FHIR API, with signed-JWT OAuth keys, a 99.95 per cent SLA, a HackerOne bug bounty and a hosted MCP server for managing integrations. The MCP server exposes 107 tools at once with write and delete tools unconfirmed, OpenAPI files sit behind login, and the sandbox plan costs $15,000 a year.

Before you call either

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

Redox

  1. Name the environment in every MCP prompt and try configuration changes in staging first, as Redox advises
  2. Stay under 7,500 requests per IP per five minutes, and back off exponentially on 5XX
  3. Sign the token request with the private key whose public key is registered on the OAuth API key
  4. Ask an organisation owner to enable the MCP server before connecting a client
  5. Treat log payloads returned through MCP as PHI and as untrusted text

Questions

Which is better for AI agents, Metriport Medical API or Redox?

Redox scores 58.3 (C) on agent readiness against Metriport Medical API's 50.1 (D), and leads in 4 of 7 scored categories. Metriport Medical API leads on schema & documentation, agent ergonomics and maintenance & community.

Do Metriport Medical API and Redox need an API key?

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

Can an agent call Metriport Medical API and Redox without installing anything?

No hosted endpoint is listed for Metriport Medical API. Redox has a hosted endpoint at https://api.redoxengine.com/mcp.

Are Metriport Medical API and Redox open source?

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). No open-source release is listed for Redox.

Other comparisons with Metriport Medical API or Redox

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.