---
name: arlo-care-pricing
description: Look up in-network cost estimates and network status for US healthcare services using Arlo Health's free price-transparency API. No login or key required.
when-to-use: the user asks what a medical service costs, whether a doctor, clinic, or hospital is in their network, or wants to compare prices near them (US only)
allowed-tools: bash
metadata:
author: Arlo Health
short-description: US care prices and network status, no auth
---
# Arlo care pricing
Free, no-auth JSON API. Base URL: `https://api.arlohealth.ai/api/pricing.v1`
Always send a `User-Agent` header naming this skill, for example:
```
-H "User-Agent: arlo-care-pricing-skill/1.0"
```
## First use in a conversation
1. Fetch the guide and follow it. It is the source of truth for reading responses:
`curl -s -H "User-Agent: arlo-care-pricing-skill/1.0" https://api.arlohealth.ai/api/pricing.v1/guide.md`
2. Fetch the catalog and pick the service CODE yourself. There is no free-text service search:
`curl -s -H "User-Agent: arlo-care-pricing-skill/1.0" https://api.arlohealth.ai/api/pricing.v1/catalog`
Codes carry facts you must confirm with the user first: age band, new vs established patient, screening vs diagnostic, body part, contrast.
3. Ask the user which insurer they have. Pass it as `payerName`. If they know the employer the plan is through or the plan name on the card, pass `employerName` or `planName` too. If they cannot provide identifiers, pass `planUnavailable=true`.
## Which endpoint
- The user names a clinic, brand, hospital, or doctor: call `network-status` FIRST.
- "What does X cost near me" with no named provider: call `search`.
- The user is focused on one specific provider and you have the NPI: call `provider-evidence`.
## Calls (GET with query parameters)
```
curl -s -H "User-Agent: arlo-care-pricing-skill/1.0" \
"https://api.arlohealth.ai/api/pricing.v1/search?code=99213&zip=94607&limit=10&payerName=Anthem"
curl -s -H "User-Agent: arlo-care-pricing-skill/1.0" \
"https://api.arlohealth.ai/api/pricing.v1/network-status?providerName=One%20Medical&zip=94107&code=99213&payerName=Anthem"
curl -s -H "User-Agent: arlo-care-pricing-skill/1.0" \
"https://api.arlohealth.ai/api/pricing.v1/provider-evidence?npi=1003041625&code=45378"
```
POST with a JSON body works the same and takes a nested `planHints` object:
```
curl -s -X POST -H "User-Agent: arlo-care-pricing-skill/1.0" -H "Content-Type: application/json" \
https://api.arlohealth.ai/api/pricing.v1/search \
-d '{"code":"99213","zip":"94607","limit":10,"planHints":{"payerName":"Anthem","employerName":"Northrop Grumman"}}'
```
Location: pass `latitude` and `longitude` if known, else a 5-digit `zip`.
## Reading responses (binding)
- Relay `disclaimer` every time. Estimates come from insurers' published rate files and are never a guarantee.
- HTTP 200 does not mean done. If `needsMoreInfo` is present, ask the user what it asks, then call again with the answer.
- Verify `service.appliesTo` matches the user before quoting numbers. Switch to a `relatedCodes` sibling if it fits better.
- Relay `service.priceNote`, per-result `note`, and `rateAssessment` whenever present.
- `inNetwork: false` means "not found in the published files", never "out of network". Say to verify with the provider.
- Never quote a single number when `billingCandidates` has more than one entry, a row has `multiEntity: true`, or `billingOutlook.mode` is `partitioned`. Present the fork and the outlook's `ask`, then help resolve which entity bills.
- Present `search` results place-first (facility name or address) with the providers inside. Mention `rateFetchNote` when present: the page is the nearest options, not the whole area.
- `rateRange` is a spread across the insurer's plan schedules when the exact plan is not matched. Lead with `typicalRate` or the median and say it is a range.
- Never rank providers or call anyone the best. Relay evidence `display` sentences as written. Absence of evidence is never negative.
- Read `plan.basis` and relay it so the user knows what the estimate is based on.
## Boundaries
US only. Not medical advice. For care, point the user to https://arlohealth.ai.
On HTTP 429 or 503, say the lookup is temporarily unavailable and try again later. Do not invent prices.
