Loa Healthcare Pricing API

Source-labeled U.S. healthcare price transparency API and MCP server. Provides hospital and provider entity search, source-labeled price rows, cross-entity price comparison by CPT/HCPCS, and a reviewed update-submission workflow. Data comes from 6,000+ hospital Machine Readable Files under the federal Hospital Price Transparency Rule plus CMS NPI Registry and Loa-reviewed provider submissions.

Loa Healthcare Pricing API publishes 1 API on the APIs.io network: Loa Healthcare Pricing REST API. Tagged areas include healthcare, price transparency, medical pricing, hospitals, and providers.

16.4/100 emerging ▬ flat Agent 23/100 agent aware Full breakdown ↓
scored 2026-08-05 · rubric v0.9.1
2 APIs
healthcareprice transparencymedical pricinghospitalsprovidersprovider directoryhospital pricesCPTHCPCSMCPagent-nativeOpenAPIllms.txt

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-05 · rubric v0.9.1
Composite quality — 16.4/100 · emerging
Contract Quality 13.4 / 25
Developer Ergonomics 0.0 / 20
Commercial Clarity 0.0 / 20
Operational Transparency 0.0 / 13
Governance 0.0 / 12
Discoverability 5.9 / 10
Agent readiness — 23/100 · agent aware
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/loa-healthcare-pricing-api: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

Loa Healthcare Pricing REST API

Versioned REST API for searching hospital/provider entities, retrieving source-labeled price rows, comparing prices by CPT code, and submitting reviewed corrections. Public read...

Loa Healthcare Pricing MCP Server

Hosted/remote MCP server 'LOA Healthcare Pricing' v1.0.0 over Streamable HTTP with 12 tools for CPT search, procedure suggestions, provider/hospital search, pricing estimates, m...

Source (apis.yml)

apis.yml Raw ↑
name: Loa Healthcare Pricing API
description: Source-labeled U.S. healthcare price transparency API and MCP server. Provides hospital and provider entity search,
  source-labeled price rows, cross-entity price comparison by CPT/HCPCS, and a reviewed update-submission workflow. Data comes
  from 6,000+ hospital Machine Readable Files under the federal Hospital Price Transparency Rule plus CMS NPI Registry and
  Loa-reviewed provider submissions.
url: https://loa-healthcare-pricing-api.apievangelist.com/apis.yml
created: '2026-07-28'
modified: '2026-08-02'
specificationVersion: '0.21'
tags:
- healthcare
- price transparency
- medical pricing
- hospitals
- providers
- provider directory
- hospital prices
- CPT
- HCPCS
- MCP
- agent-native
- OpenAPI
- llms.txt
apis:
- name: Loa Healthcare Pricing REST API
  description: Versioned REST API for searching hospital/provider entities, retrieving source-labeled price rows, comparing
    prices by CPT code, and submitting reviewed corrections. Public reads require no key; optional metered provider API key
    via x-api-key header.
  humanURL: https://www.loacare.com/provider/docs
  baseURL: https://www.loacare.com/api/v1
  tags:
  - healthcare
  - price transparency
  - medical pricing
  - hospitals
  - providers
  - provider directory
  - hospital prices
  - CPT
  - HCPCS
  - MCP
  - agent-native
  - OpenAPI
  - llms.txt
  properties:
  - type: OpenAPI
    url: openapi/loa-healthcare-pricing-api-openapi.json
  - type: OpenAPI
    url: https://www.loacare.com/api/v1/openapi.json
  - type: Documentation
    url: https://www.loacare.com/provider/docs
  - type: APIsJSON
    url: https://www.loacare.com/apis.json
- name: Loa Healthcare Pricing MCP Server
  description: Hosted/remote MCP server 'LOA Healthcare Pricing' v1.0.0 over Streamable HTTP with 12 tools for CPT search,
    procedure suggestions, provider/hospital search, pricing estimates, market pricing, entity profiles/prices, price source
    explanation, and update submission. Discovery is public; tool calls require OAuth 2.0.
  humanURL: https://www.loacare.com/mcp
  baseURL: https://www.loacare.com/api/mcp
  tags:
  - healthcare
  - price transparency
  - medical pricing
  - hospitals
  - providers
  - provider directory
  - hospital prices
  - CPT
  - HCPCS
  - MCP
  - agent-native
  - OpenAPI
  - llms.txt
  properties:
  - type: MCP
    url: https://www.loacare.com/api/mcp
  - type: Documentation
    url: https://www.loacare.com/mcp
  - type: LLMSTxt
    url: https://www.loacare.com/llms.txt
maintainers:
- FN: Loa Engineering
  url: https://www.loacare.com/api-partnership
generated:
  by: apis.io/add
  model: claude-opus-4-8
  confidence: 95
  at: '2026-07-28T12:04:57.353Z'
x-evidence:
  verified: '2026-08-02'
  request: api-evangelist/loa-healthcare-pricing-api#1
  probes:
  - https://www.loacare.com/api/v1/openapi.json -> HTTP 200, OpenAPI 3.1.0, 6 paths / 6 ops / 19 schemas
  - https://www.loacare.com/apis.json -> HTTP 200, advertised example now uses q=
  - https://www.loacare.com/api/v1/entities/search?q=hospital&state=Texas&limit=1 -> HTTP 200, one Texas hospital
  resolved: The search-parameter mismatch flagged at profile generation — apis.json advertising query= while the OpenAPI defines
    q — was fixed by the provider and confirmed resolved. The stale note is removed from PROFILE.md.
  still_open: OpenAPI info.version is 0.1.0 while the document is OpenAPI 3.1.0. Left flagged; the provider did not claim
    to have changed it and it is still true.
  note: The OpenAPI is now held locally as well as referenced by URL. Advertised spec URLs across the catalog go stale, and
    a local copy is what the profile is actually built from.