For developers & agents

Healthcare data built to be called by AI agents

Medical billing, coding and prior-auth are jobs agents are being handed right now — and every one of them needs real, deterministic data. Patientary exposes the exact lookups behind the site as a REST API and a hosted MCP server, so an agent resolves an NPI or validates a code instead of guessing one.

Quickstart

One key, one call

Get a key at /signup (free tier included, no card), then call any endpoint below.

request

curl "https://patientary.com/api/v1/npi/1245319599" \
  -H "Authorization: Bearer ptn_live_..."

response 200

{
  "request_id": "req_9f3ac1d0",
  "npi": {
    "npi": "1245319599",
    "type": "individual",
    "name": "...",
    "status": "active",
    "primaryTaxonomy": { "code": "207Q00000X", "desc": "Family Medicine" }
  },
  "disclaimer": "Patientary is an informational reference tool built on public data (CMS NPPES ..."
}

Built for agents

Six things an agent needs from an API

Single-key auth

One API key unlocks the REST API and the MCP server. No OAuth dance, no per-endpoint credentials — a bearer key you generate once in Settings.

Machine-readable docs

A full reference, a spec at /api/openapi, and a plain-text summary at /llms.txt so an agent can onboard itself without a human reading a page first.

Safe by default

Anonymous calls work for a dry run, throttled by IP. Every key is scoped to your plan's rate limit, so a misbehaving agent can't run up an unbounded bill.

Reliable & inspectable

Errors are always structured JSON, every response carries a request_id for tracing, and Pro+ plans get an exportable request log — a real audit trail of what your agent actually called.

Cited real sources

Every field traces back to the live CMS NPPES registry, the official CMS ICD-10-CM release, or the NUCC taxonomy — never a guess, and every response says so.

Usage-metered pricing

Cost scales with calls, not seats — see the plans & quotas.

REST API

Every endpoint

Base URL https://patientary.com/api/v1. Optional. Send `Authorization: Bearer ptn_live_…` for higher limits. Anonymous calls are rate-limited by IP. JSON. Every response includes `request_id` and `disclaimer`; errors are `{ error: { code, message } }`.

GET

/api/v1/npi/{npi}

Look up a single provider by NPI number (live CMS NPPES data).

curl https://patientary.com/api/v1/npi/1245319599
GET

/api/v1/npi

Search the NPPES registry by name, organization, taxonomy or location.

curl "https://patientary.com/api/v1/npi?last_name=smith&state=CA&taxonomy=cardiology"
GET

/api/v1/icd10/{code}

Get one ICD-10-CM code with chapter, billable status, parent and children.

curl https://patientary.com/api/v1/icd10/E11.9
GET

/api/v1/icd10

Search ICD-10-CM by code prefix or clinical description.

curl "https://patientary.com/api/v1/icd10?q=type%202%20diabetes&billable=1"
GET

/api/v1/taxonomy

Look up or search NUCC provider-taxonomy (specialty) codes.

curl "https://patientary.com/api/v1/taxonomy?q=family%20medicine"
POST

/api/v1/validate

Pro+

Batch-validate NPIs and ICD-10 codes in one call (claim scrubbing).

curl -X POST https://patientary.com/api/v1/validate -H "Content-Type: application/json" -d '{"npis":["1245319599"],"icd10":["E11.9","Z00.00"]}'

Patientary is an informational reference tool built on public data (CMS NPPES and the official ICD-10-CM release). It is not medical, coding, legal or billing advice, and code assignment is the responsibility of a qualified professional. Always verify against the primary source before you bill or file.

Full API reference MCP server setup

Usage-metered pricing

The free tier is real — 3,000 calls/mo is enough to build and test against. Pro and Scale sell throughput: batch validation, crosswalks, monitoring and a production MCP quota.

See plans & quotas