KLOUDY / FHIR
Medical data stays on FHIR.
Medical lane uses FHIR, not KLDY. Hospitals keep FHIR. Kloudy speaks it so a bot can narrow records before a tool call. Non-medical sites do not pretend to be FHIR.
Product overview. Public-page reading and KLDY preparation are available here. The connector, account actions and native apps described below are not connected to this site.
Less setup. More useful work.
For IDEs and bots: one CLI, one MCP, tools appear when needed.
Find with SEO/GEO, read FHIR for medical data or KLDY for other information, then select one scoped Toolbox tool when action is needed.
Passive local reads use no model calls. Narrowing 100 candidate definitions to 10 would mean 90% fewer definition fetches in that example; this is an illustration, not measured token savings.
Read public capabilities
Paste a public FHIR metadata endpoint URL into Kloudy to read a CapabilityStatement. The browser shows software, FHIR version, declared resource types and interactions. It does not render narrative HTML, retrieve patient records, validate full FHIR conformance or grant access to any declared action. Clinical resources and Bundles are rejected by this reader.