Aidence
Aidence is a radiology AI company founded in Amsterdam in 2015 that builds clinical AI for the lung cancer pathway. Its flagship product, Veye Lung Nodules (now DeepHealth Lung), is a CE-marked AI solution that detects, classifies, quantifies, and measures growth of pulmonary nodules on chest CT scans, and is the AI of choice in NHS England's Targeted Lung Health Checks screening programme. Aidence was acquired by RadNet in 2022 and now operates under the DeepHealth brand; aidence.com redirects to deephealth.com/aidence. The product integrates with hospital systems over DICOM/PACS via the Veye Engine rather than a public developer REST API — no public API, developer portal, or SDKs are published. This profile captures the company's identity plus its probed security and disclosure posture.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Aidence the way a machine reads it — 3 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 — Aidence scores 21.1/100 (emerging), with a separate agent-readiness read of 7/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.
How we profile Aidence
Each block below is one kind of artifact we hold for Aidence. 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.
Security Posture 3
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 Aidence — 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 1
MCP servers, agent skills, and machine-readable catalogs
Access & Security 6
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/aidence · machine-readable index on apis.io