AgentCard object — a capabilities object, a declared protocolVersion, and a well-formed skills array.
An A2A client finds this agent by fetching the well-known path on the provider's own host. That is what makes an agent card different from every other agent artifact in this catalog: it is provider-published by construction — it cannot be derived, generated, or reconstructed on a provider's behalf.
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.
treatmentworkflowsbulkbyod-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.
byodworkflowsreciprocity
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.
reciprocityworkflowsrequery-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.
treatmentworkflowsretrieval-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.
retrieval-onlyworkflowsstandard-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.
treatmentworkflows2026-09-04 from https://docs.xcures.com/.well-known/agent-card.json,
HTTP 200. The body was saved verbatim and is the sole source for
everything on this page — no field is inferred.
View the captured card.
Providers change what they serve; if this card has moved or changed shape,
the provider profile carries the
current state as of the last build.
Work with this as data
Every agent card here is available over the APIs.io API and to AI agents over MCP. A2A Agent Cards is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.