Fasten Connect
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.
https://docs.connect.fastenhealth.com/
· transport HTTP+JSON
non-standard supportedInterfaces
Fastenhealth fastenhealth
Use when building patient-facing medical record access flows, integrating health data collection into applications, managing patient consent workflows, or requesting and processing FHIR-formatted health records from healthcare providers.
2026-08-14 from https://docs.connect.fastenhealth.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.