dehaze
dehaze is a Munich-area (Fürstenfeldbruck, Germany) healthtech company, part of the Techstars Berlin cohort, building proprietary causal AI infrastructure that detects chronic and autoimmune disease earlier by identifying overlooked diagnoses, health risks, and inappropriate treatments. Its platform unifies and harmonizes diverse health data (lab results, medical imaging, genomics, clinical notes) into doctor-validated patient journeys, risk-profiles individuals against millions of health journeys and medical guidelines, and runs targeted AI follow-ups to improve treatment adherence for patients, payers, and providers. dehaze has analyzed over 250,000 patient lives across 300 million health events and 200+ AI algorithms, and raised €3.2M in 2026. dehaze publishes no first-party developer API; it exposes a Wix Site MCP endpoint and an llms.txt for agentic AI access to public site content.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles dehaze the way a machine reads it — 2 machine-readable artifacts, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — dehaze scores 8.5/100 (minimal), with a separate agent-readiness read of 12/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile dehaze
Each block below is one kind of artifact we hold for dehaze. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
dehaze-mcp.yml
MCP SERVERSecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for dehaze — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Access & Security 1
Authentication, authorization, and security posture
Company 4
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/dehaze · machine-readable index on apis.io