Skip to main content
POST
Public-data evidence about one provider (by NPI)

Authorizations

Authorization
string
header
required

Optional. An Arlo account token adds linked-coverage plan matching and family-member patientId. Anonymous calls resolve the plan from planHints only.

Body

application/json

Public-data evidence about ONE specific provider: Medicare-derived experience, facility outcome context (facility-level, never the clinician's own outcome), Medicare payment anchors, or an explained absence. Use only once the conversation is focused on one provider.

npi
string
required

The provider's 10-digit NPI. Resolve it first via network-status (name search) or from search results.

code
string

Optional catalog code to scope evidence to one service.

Response

Evidence card payload

provider
object
service
object

Echo of the resolved service. VERIFY appliesTo against the actual patient before relaying any number.

signals
object[]

Pre-gated evidence signals from public CMS data. Relay each signal's 'display' sentence as written; never compress into ranking or 'best doctor' language; never treat absence as negative (non-Medicare practices legitimately lack data). An 'exclusion' signal (federal OIG exclusion list) is a legal-status safety notice: always relay it plainly.

medicareAnchors
object[]

What Medicare actually paid this provider per service. Reference points from public data, not fair-price claims and not the patient's price.

signalDefinitions
object
methodology
string
corrections
string
disclaimer
string

ALWAYS convey to the patient: estimates come from the insurer's published data and are not a price guarantee.

needsMoreInfo
object[]

Asks to relay to the patient. Answering them improves the estimate (ranges become the plan's exact rates). Each ask names the field, why it matters, and how to obtain it.