xCures

xCures operates the Clinical Clarity Engine, an AI platform that retrieves, organizes and structures fragmented patient medical records into decision-ready clinical data. Founded in 2018 and headquartered in Oakland, California, the company connects to national health information networks (Carequality and TEFCA) to pull a patient's longitudinal record across every provider and care location, then applies LLM-based named-entity/relation extraction and retrieval-augmented checklist assertion to normalize it into FHIR R4 resources, OHDSI/OMOP-mapped vocabularies (SNOMED, LOINC, RxNorm) and HL7 mCODE oncology elements, with every field anchored to its source document. The xCures Public API exposes that engine over REST at partner.xcures.com — patient (Subject) registration, network Query dispatch and polling, document retrieval and reciprocity publishing, FHIR resource reads and bulk export, fifteen Clinical Concepts domains, AI Checklist evaluation and subject summaries — authenticated with OAuth 2.0 client-credentials bearer tokens scoped by a ProjectId header. Originally an oncology real-world-data platform, it expanded to all therapeutic areas and is sold as SaaS, embedded API connections and de-identified real-world datasets to providers, diagnostics companies, value-based-care organizations and channel partners.

xCures publishes 1 API on the APIs.io network: Public API. Tagged areas include Health, Healthcare, Medical Records, Interoperability, and FHIR.

The xCures catalog on APIs.io includes 1 event-driven AsyncAPI specification.

xCures’ developer surface includes documentation, API reference, getting-started guide, support, engineering blog, signup flow, changelog, and 30 more developer resources.

🌐 Visit website 📡 Source on GitHub

64.5/100 strong Agent 54/100 agent ready Full breakdown ↓
scored 2026-09-04 · rubric v0.18.3

1 APIs 1 MCP Servers

Health Healthcare Medical Records Interoperability FHIR OncologyReal World DataClinical Data Artificial Intelligence TEFCACarequalityPatient Data HITRUST HIPAA

Kin Score

Kin Score How this is scored →
scored 2026-09-04 · rubric v0.18.3

Composite quality — 64.5/100 · strong

Contract Quality 13.3 / 21

Developer Ergonomics 13.0 / 17

Access Clarity 8.5 / 17

Operational Transparency 8.1 / 11

Contract Governance 1.9 / 10

Discoverability 5.8 / 9

Regulatory Posture 7.9 / 15

Agent readiness — 54/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 6 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Health regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/xcures: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

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

xCures Public API

REST API for the xCures Clinical Clarity Engine. Register patients (Subjects), dispatch and poll queries against Carequality/TEFCA health information networks, retrieve and publ...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Rate Limits 1

Documented rate limits and quota policies.

Examples 1

Example request and response payloads for these APIs.

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

GettingStarted

SignUp

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

MCPServer

AgentSkill

WellKnown

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Conventions

Conformance

Lifecycle

ErrorCatalog

DataModel

Webhooks

Idempotency

Scroll for all 7

Build 5

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

Postman

ToolCrosswalk

Packages

Examples

Access & Security 4

Authentication, authorization, and security posture

TrustCenter

Compliance

Authentication

DomainSecurity

Operate 5

Status, limits, changes, and where to get help

Support

StatusPage

ChangeLog

RateLimits

Deprecation

Commercial 3

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Plans

Plans

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

AgentCard

AgentCard

Source (apis.yml)

aid: xcures
name: xCures
description: xCures operates the Clinical Clarity Engine, an AI platform that retrieves, organizes and structures fragmented
  patient medical records into decision-ready clinical data. Founded in 2018 and headquartered in Oakland, California, the
  company connects to national health information networks (Carequality and TEFCA) to pull a patient's longitudinal record
  across every provider and care location, then applies LLM-based named-entity/relation extraction and retrieval-augmented
  checklist assertion to normalize it into FHIR R4 resources, OHDSI/OMOP-mapped vocabularies (SNOMED, LOINC, RxNorm) and HL7
  mCODE oncology elements, with every field anchored to its source document. The xCures Public API exposes that engine over
  REST at partner.xcures.com — patient (Subject) registration, network Query dispatch and polling, document retrieval and
  reciprocity publishing, FHIR resource reads and bulk export, fifteen Clinical Concepts domains, AI Checklist evaluation
  and subject summaries — authenticated with OAuth 2.0 client-credentials bearer tokens scoped by a ProjectId header. Originally
  an oncology real-world-data platform, it expanded to all therapeutic areas and is sold as SaaS, embedded API connections
  and de-identified real-world datasets to providers, diagnostics companies, value-based-care organizations and channel partners.
image: https://xcures.com/wp-content/uploads/2026/06/default-image-sharing.png
url: https://raw.githubusercontent.com/api-evangelist/xcures/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.20'
created: '2026-09-04'
modified: '2026-09-04'
position: Producing
tags:
- Health
- Healthcare
- Medical Records
- Interoperability
- FHIR
- Oncology
- Real World Data
- Clinical Data
- Artificial Intelligence
- TEFCA
- Carequality
- Patient Data
- HITRUST
- HIPAA
tags_raw:
- health
- healthcare
- medical-records
- interoperability
- fhir
- oncology
- real-world-data
- clinical-data
- artificial-intelligence
- tefca
- carequality
- patient-data
- hitrust
- hipaa
apis:
- name: xCures Public API
  description: REST API for the xCures Clinical Clarity Engine. Register patients (Subjects), dispatch and poll queries against
    Carequality/TEFCA health information networks, retrieve and publish clinical documents (including reciprocity back to
    the network), read normalized FHIR R4 resources and a FHIR bulk export, search fifteen Clinical Concepts domains (conditions,
    medications, labs, biomarkers, imaging, procedures, allergies, vitals, encounters, demographics, coverage, family history,
    social history, surveys, radiation), evaluate AI Checklists, and fetch AI-generated subject summaries. OAuth 2.0 client-credentials
    bearer auth with a required ProjectId header on nearly every operation.
  humanURL: https://docs.xcures.com/apis/current
  baseURL: https://partner.xcures.com
  image: https://xcures.com/wp-content/uploads/2026/06/default-image-sharing.png
  tags:
  - Health
  - Healthcare
  - Medical Records
  - Interoperability
  - FHIR
  - Clinical Data
  - Patient Data
  properties:
  - type: OpenAPI
    url: openapi/xcures-patient-registry-api-openapi.yml
  - type: Documentation
    url: https://docs.xcures.com/api-introduction
  - type: APIReference
    url: https://docs.xcures.com/apis/current
  - type: GettingStarted
    url: https://docs.xcures.com/api-introduction
  - type: Authentication
    url: authentication/xcures-authentication.yml
  - type: Postman
    url: https://docs.xcures.com/downloads/xCures_SDK_Workflows.postman_collection.json
  - type: ChangeLog
    url: https://docs.xcures.com/changelog
  - type: Webhooks
    url: asyncapi/xcures-application-webhooks.yml
  - type: ErrorCatalog
    url: errors/xcures-problem-types.yml
  - type: RateLimits
    url: rate-limits/xcures-rate-limits.yml
  - type: DataModel
    url: data-model/xcures-data-model.yml
  - type: Overlay
    url: overlays/xcures-patient-registry-api-overlay.yaml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://xcures.com/
- type: DeveloperPortal
  url: https://docs.xcures.com/
- type: Documentation
  url: https://docs.xcures.com/api-introduction
- type: APIReference
  url: https://docs.xcures.com/apis/current
- type: GettingStarted
  url: https://docs.xcures.com/api-introduction
- type: Support
  url: https://docs.xcures.com/support
- type: Blog
  url: https://xcures.com/blog/
- type: GitHubOrganization
  url: https://github.com/xCures
- type: SignUp
  url: https://xcures.com/contact-us/
- type: TermsOfService
  url: https://xcures.com/terms-of-service/
- type: PrivacyPolicy
  url: https://xcures.com/privacy-security-notice/
- type: TrustCenter
  url: https://xcures.com/trust/
- type: Compliance
  url: https://xcures.com/trust/
- type: StatusPage
  url: https://status.xcures.com/
- type: Postman
  url: https://docs.xcures.com/downloads/xCures_SDK_Workflows.postman_collection.json
- type: LLMsTxt
  url: llms/xcures-llms.txt
- type: AgentCard
  url: a2a/xcures-a2a.yml
- type: MCPServer
  url: mcp/xcures-mcp.yml
- type: ToolCrosswalk
  url: mcp/xcures-tool-crosswalk.yml
- type: AgentSkill
  url: skills/_index.yml
- type: WellKnown
  url: well-known/xcures-well-known.yml
- type: Conventions
  url: conventions/xcures-conventions.yml
- type: Conformance
  url: conformance/xcures-conformance.yml
- type: Lifecycle
  url: lifecycle/xcures-lifecycle.yml
- type: ChangeLog
  url: changelog/xcures-changelog.yml
- type: Authentication
  url: authentication/xcures-authentication.yml
- type: DomainSecurity
  url: security/xcures-domain-security.yml
- type: Plans
  url: plans/xcures-plans-pricing.yml
- type: RateLimits
  url: rate-limits/xcures-rate-limits.yml
- type: Sandbox
  url: sandbox/xcures-sandbox.yml
- type: Packages
  url: packages/xcures-packages.yml
- type: ErrorCatalog
  url: errors/xcures-problem-types.yml
- type: DataModel
  url: data-model/xcures-data-model.yml
- type: Webhooks
  url: asyncapi/xcures-application-webhooks.yml
- type: Idempotency
  url: conventions/xcures-conventions.yml
- type: Deprecation
  url: lifecycle/xcures-lifecycle.yml
- type: Examples
  url: examples/_index.yml
x-enrichment:
  date: '2026-09-04'
  status: enriched
  artifacts_added: 37
  pass: local-v3

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/xcures"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/xcures/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/xcures/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

xCures

Kin Score

APIs 1

xCures Public API

MCP Servers 1

xCures Docs MCP Server

Pricing Plans 1

Xcures Plans Pricing

Rate Limits 1

Xcures Rate Limits

Event Specifications 1

Xcures Application Webhooks