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 11 API contracts indexed on the APIs.io network, including Application API, Checklist API, Clinical Concepts API, and 8 more. Tagged areas include Health, Healthcare, Medical Records, Interoperability, and FHIR.

The xCures catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

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

🌐 Visit website 📡 Profile data on GitHub

62.5/100 strong ▬ flat Agent 60/100 agent ready Front door AI 3/6 light Heartbeat 100/100 alive Full breakdown ↓
scored 2026-11-02 · rubric v0.26.0 · Show this score on your site →

1 published contract 1 MCP Servers 6 Agent Skills

Health Healthcare Medical Records Interoperability FHIR Oncology Real-World Data Clinical Data Artificial Intelligence TEFCA Carequality Patient Data HITRUST HIPAA A2A

Kin Score

Kin Score How this is scored →
scored 2026-11-02 · rubric v0.26.0

Composite quality — 62.5/100 · strong

Contract Quality 10.9 / 19

Developer Ergonomics 11.4 / 15

Access Clarity 7.5 / 15

Operational Transparency 6.9 / 10

Contract Governance 2.9 / 9

Discoverability 5.6 / 8

Regulatory Posture 4.6 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 60/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

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

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.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

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

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/xcures/"><img src="https://apis.io/badge/xcures/card.svg" alt="xCures on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Documented Reversibility +6 pts — a reversal operation in the contract, graded up when a window is documented too
Agentic Commerce Well-Known Document +5 pts — a parsing /.well-known/ucp.json or acp.json declaring a version and at least one service — `self` when its endpoints are on the provider's own domain, `platform` when they are on a vendor's
Dry-Run / Simulate Mode +4 pts — OpenAPI: destructive operations expose a dry_run / simulate / preview / validate_only parameter
Well-Known Catalog +4 pts — common[].type includes WellKnown, APICatalog, or api-catalog

1 more unmet check in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 58.2 — up to +10.5 composite points
Access Clarity scores 50.0 — up to +10.0 composite points
Contract Governance scores 31.8 — up to +8.2 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

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 the provider profile at artifacts.apis.io/xcures/apis.yml: open an issue on github.com/api-evangelist/xcures to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Life Sciences (Biotech and Pharma R&D)	undeclared	-	-	1
Certified Health IT (health IT accreditation and certification registers)	undeclared	-	-	1
FHIR Implementation Guides (HL7 FHIR package and IG publishers)	undeclared	-	-	1

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 8

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Agent2Agent

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

HL7 FHIR

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

Model Context Protocol (MCP)

measured — observed by APIs.io (verified)

Agent Skills

measured — observed by APIs.io (published)

OAuth 2.0 Protected Resource Metadata

measured — observed by APIs.io (verified)

Dynamic Client Registration

measured — observed by APIs.io (published)

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

APIs 11

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

xCures Application API

Account creation (e.g., identity proofing, eConsent) that is required for a patient to progress on the xCures Platform.

xCures Checklist API

AI-powered feature leveraging xCures’ targeted data extraction/processing to populate validated, customizable question/answer-style items. Responses can be highly flexible and e...

xCures Clinical Concepts API

Clinical concepts is a proprietary xCures higher-level, flattened, filtered, opinionated view of medical record information, structured around FHIR guidelines.

xCures Document API

Patient records retrieved by the xCures platform and/or loaded by platform users.

xCures FHIR API

**F**ast **H**ealthcare **I**nteroperability **R**esource is an international data model specification developed by HL7 International to enable healthcare data exchange and inte...

xCures Project API

A configured workspace on the xCures Platform. Use this endpoint to discover the projectId value(s) required by other API calls, without needing to log into the portal.

xCures Query API

A specified, approved request for patient records across the network (e.g., via Carequality/TEFCA to support treatment activities, via TEFCA for IAS queries) with an associated ...

xCures Reciprocity Template API

Reciprocity or "Responder" workflows refer to the process of sharing clinical documentation housed within your system with other organizations/providers, when participating in h...

xCures Subject API

An individual patient created on the xCures Platform.

xCures Summary API

The AI-generated summary of a patient’s overall records and condition(s).

xCures O Auth API

All API requests to xCures must provide an access token, retrieved via the standard OAuth authorization flow below.

Scroll for all 11

MCP Servers 1

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

xCures Docs MCP Server

A remote MCP server xCures runs on its own documentation host as part of the Redocly Realm API Hub. It exposes the documentation corpus and the six published Agent Skills as MCP...

MCP SERVER

Agent Skills 6

Packaged agent skills for driving this provider's APIs from an AI assistant.

bulk-patient-onboarding

AGENT SKILL

byod-ingestion

AGENT SKILL

reciprocity

AGENT SKILL

requery-patient

AGENT SKILL

retrieval-only

AGENT SKILL

standard-treatment-workflow

AGENT SKILL

Pricing Plans 1

Published pricing tiers and plan structures.

Xcures Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Xcures Rate Limits

1 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Xcures Finops

FINOPS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Xcures Application Webhooks

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

xCures API Rules

59 rules · 47 errors 8 warnings 4 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Xcures Patient Registry Api Overlay

11 actions · update · xcures-patient-registry-api-openapi.yml

DERIVED

Examples 1

Example request and response payloads for these APIs.

Xcures Workflow Playbook.Postman_Collection

3 fields

EXAMPLE

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Xcures Authentication

http/oauth2 · 2 schemes

SECURITY

Xcures Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Xcures Trust Center

trust center published

SECURITY

Resources

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 6

Status, limits, changes, and where to get help

Support

StatusPage

ChangeLog

RateLimits

Deprecation

Contact

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 2

Properties that don't map to a standard resource type

Overlay

Overlay

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.
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - rate-limits
  - security
  - sandbox
  generated: '2026-11-02'
  method: derived
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
x-docs-platform: redocly
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-17
tags:
- Health
- Healthcare
- Medical Records
- Interoperability
- FHIR
- Oncology
- Real-World Data
- Clinical Data
- Artificial Intelligence
- TEFCA
- Carequality
- Patient Data
- HITRUST
- HIPAA
- A2A
tags_raw:
- health
- healthcare
- medical-records
- interoperability
- fhir
- oncology
- real-world-data
- clinical-data
- artificial-intelligence
- tefca
- carequality
- patient-data
- hitrust
- hipaa
- A2A
apis:
- aid: xcures:xcures-application-api
  name: xCures Application API
  description: Account creation (e.g., identity proofing, eConsent) that is required for a patient to progress on the xCures
    Platform.
  humanURL: https://docs.xcures.com/apis/current
  baseURL: https://partner.xcures.com
  tags:
  - Application
  properties:
  - type: OpenAPI
    url: openapi/xcures-application-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
- aid: xcures:xcures-checklist-api
  name: xCures Checklist API
  description: AI-powered feature leveraging xCures’ targeted data extraction/processing to populate validated, customizable
    question/answer-style items. Responses can be highly flexible and every item returns a justification, supporting documents,
    and structured data to guide decisions in real time.
  humanURL: https://docs.xcures.com/apis/current
  baseURL: https://partner.xcures.com
  tags:
  - Checklist
  properties:
  - type: OpenAPI
    url: openapi/xcures-checklist-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
- aid: xcures:xcures-clinical-concepts-api
  name: xCures Clinical Concepts API
  description: Clinical concepts is a proprietary xCures higher-level, flattened, filtered, opinionated view of medical record
    information, structured around FHIR guidelines.
  humanURL: https://docs.xcures.com/apis/current
  baseURL: https://partner.xcures.com
  tags:
  - Clinical Concepts
  properties:
  - type: OpenAPI
    url: openapi/xcures-clinical-concepts-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
- aid: xcures:xcures-document-api
  name: xCures Document API
  description: Patient records retrieved by the xCures platform and/or loaded by platform users.
  humanURL: https://docs.xcures.com/apis/current
  baseURL: https://partner.xcures.com
  tags:
  - Documents
  tags_raw:
  - Document
  properties:
  - type: OpenAPI
    url: openapi/xcures-document-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
- aid: xcures:xcures-fhir-api
  name: xCures FHIR API
  description: '**F**ast **H**ealthcare **I**nteroperability **R**esource is an international data model specification developed
    by HL7 International to enable healthcare data exchange and interoperability between different systems.'
  humanURL: https://docs.xcures.com/apis/current
  baseURL: https://partner.xcures.com
  tags:
  - FHIR
  properties:
  - type: OpenAPI
    url: openapi/xcures-fhir-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
- aid: xcures:xcures-project-api
  name: xCures Project API
  description: A configured workspace on the xCures Platform. Use this endpoint to discover the projectId value(s) required
    by other API calls, without needing to log into the portal.
  humanURL: https://docs.xcures.com/apis/current
  baseURL: https://partner.xcures.com
  tags:
  - Project
  properties:
  - type: OpenAPI
    url: openapi/xcures-project-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
- aid: xcures:xcures-query-api
  name: xCures Query API
  description: A specified, approved request for patient records across the network (e.g., via Carequality/TEFCA to support
    treatment activities, via TEFCA for IAS queries) with an associated status (e.g., “completed”).
  humanURL: https://docs.xcures.com/apis/current
  baseURL: https://partner.xcures.com
  tags:
  - Query
  properties:
  - type: OpenAPI
    url: openapi/xcures-query-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
- aid: xcures:xcures-reciprocity-template-api
  name: xCures Reciprocity Template API
  description: Reciprocity or "Responder" workflows refer to the process of sharing clinical documentation housed within your
    system with other organizations/providers, when participating in health data exchange networks (e.g., Carequality, TEFCA).
  humanURL: https://docs.xcures.com/apis/current
  baseURL: https://partner.xcures.com
  tags:
  - Reciprocity Template
  properties:
  - type: OpenAPI
    url: openapi/xcures-reciprocity-template-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
- aid: xcures:xcures-subject-api
  name: xCures Subject API
  description: An individual patient created on the xCures Platform.
  humanURL: https://docs.xcures.com/apis/current
  baseURL: https://partner.xcures.com
  tags:
  - Subject
  properties:
  - type: OpenAPI
    url: openapi/xcures-subject-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
- aid: xcures:xcures-summary-api
  name: xCures Summary API
  description: The AI-generated summary of a patient’s overall records and condition(s).
  humanURL: https://docs.xcures.com/apis/current
  baseURL: https://partner.xcures.com
  tags:
  - Summary
  properties:
  - type: OpenAPI
    url: openapi/xcures-summary-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
- aid: xcures:xcures-oauth-api
  name: xCures O Auth API
  description: All API requests to xCures must provide an access token, retrieved via the standard OAuth authorization flow
    below.
  humanURL: https://docs.xcures.com/apis/current
  baseURL: https://partner.xcures.com
  tags:
  - OAuth
  - Authentication
  tags_raw:
  - OAuth
  - Authentication
  properties:
  - type: OpenAPI
    url: openapi/xcures-oauth-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
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Overlay
  url: overlays/xcures-patient-registry-api-overlay.yaml
- 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
- type: Contact
  url: mailto:help@xcures.com
x-enrichment:
  date: '2026-09-04'
  status: enriched
  artifacts_added: 37
  pass: local-v3
x-a2a:
  verified: true
  probed: '2026-09-26'
  url: https://docs.xcures.com/.well-known/agent-card.json
  grade: conformant
  protocol_version: 0.3.0
  control: 404

xCures API — frequently asked questions

Does xCures have an API?

Yes. APIs.io lists 11 APIs from xCures, including xCures Application API, xCures Checklist API and xCures Clinical Concepts API, and 8 more.

Is there an OpenAPI specification for the xCures API?

Yes. APIs.io indexes 11 OpenAPI specifications for xCures, each linked for download from this page.

How do I authenticate with the xCures API?

xCures documents its authentication (http/oauth2 · 2 schemes). The details are profiled on APIs.io as Xcures Authentication.

Does xCures have an MCP server?

Yes. APIs.io lists 1 MCP server for xCures: A remote MCP server xCures runs on its own documentation host as part of the Redocly Realm API Hub. It exposes the documentation corpus and the six published Agent Skills as MCP tools. It is a documen

Is the xCures API ready for AI agents?

xCures has a Kin Score of 62.5 out of 100 (strong) and an Agent Readiness score of 59.5 (agent-ready), scored by API Evangelist on 2026-11-02.

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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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