xCures API Hub bronze
docs.xcures.com
“xCures API Hub
a2a https://docs.xcures.com/a2a talk to it https://docs.xcures.com/.well-known/agent-card.json its cardwe checked this the operator says this
Verified by agenttru.st
Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.
- Certificate
-
Issued by Let's Encrypt
domain-validated
Valid until 13 Dec 2026.Control of the hostname was checked; nothing about who operates it.
- DANE / TLSA
- Not verified (TLSA query returned RCodeNameError)
- Discovery
- Well-known document
- First seen
- 15 Sep 2026
View verification details
- Assurance
- bronze Bronze — agent card fetched over HTTPS with a valid certificate
- Protocols
- A2A verified by handshake or card fetch, not merely advertised
- Hosted in
- 🇩🇪 DE · Amazon.com, Inc. (AS16509)
- Last checked
- 16h ago
What this agent says it can do
Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of docs.xcures.com controls every word below.
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.
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.
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.
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.
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.
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.
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Protocol
- a2a
- Version
- 0.0.1
- Extensions
-
https://modelcontextprotocol.ioModel Context Protocol server exposing the documentation tools and skills.A2A protocol extensions the card declares. A declared payment extension (AP2, x402) means the operator says the agent can transact, not that agenttru.st has seen it do so. - Card completeness
-
a2a.proto v1.0 requires eight top-level fields. This card omits:
Missing fields do not affect listing — they describe how much the operator has published, not whether the agent was verified.
View all card details
- Capabilities
- extensions pushNotifications streaming
- Agent card
- https://docs.xcures.com/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.