Metriport Medical API vs Validic Inform

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.

Validic Inform

Graded on the Inform REST and Streaming APIs. An agent can create a free developer account through a sign-up API, with only an emailed code needing a person's inbox, and llms.txt plus agent guides document every step. The organisation token travels in the URL query string, the free tier holds synthetic data only, and production access needs an Enterprise contract.

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

Validic Inform

1. Show the developer the free-tier terms and wait for acceptance before calling POST /auth/register
2. Send Authorization: <id_token> to sign-up calls, but pass the organisation token as ?token= on Inform calls
3. Use the customer uid in URLs, never Validic's internal id, which returns a silent 404
4. Keep date ranges to 30 days or less and page month by month for backfills
5. Unwrap data on list responses and treat an empty array as normal on a new account