Intelerad
Intelerad Medical Systems is an enterprise medical imaging company whose platform spans diagnostic PACS (IntelePACS), the InteleViewer / zero-footprint web viewer, a vendor-neutral archive (VNA), and the cloud image-exchange platform InteleShare - the product formed after Intelerad acquired Ambra Health (Ambra Image Exchange) in 2021. The InteleShare / Ambra platform exposes a documented public "v3 Services" REST-like API plus a Storage API for programmatically managing DICOM studies, patients, orders, reports, HL7 message flows, routing, and multi-tenant namespaces. Integration is built on medical-imaging interoperability standards - DICOM and DICOMweb (WADO / QIDO / STOW), HL7 v2 (ORM, ORU, ADT), and FHIR - with a Gateway that routes DICOM and HL7 between on-premise systems and the cloud, plus EHR/RIS integrations (Epic, Cerner, Athena). Core PACS/RIS APIs are partner- and contract-gated; the InteleShare / Ambra v3 API is the publicly documented developer surface.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Intelerad the way a machine reads it — 16 machine-readable artifacts across 9 APIs, 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 — Intelerad scores 37.3/100 (thin), with a separate agent-readiness read of 48/100 (agent ready). 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 Intelerad
Each block below is one kind of artifact we hold for Intelerad. 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.
APIs 9
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Intelerad HL7 API
The HL7 API from Intelerad — 1 operation(s) for hl7.
Intelerad Namespace API
The Namespace API from Intelerad — 1 operation(s) for namespace.
Intelerad Order API
The Order API from Intelerad — 2 operation(s) for order.
Intelerad Patient API
The Patient API from Intelerad — 2 operation(s) for patient.
Intelerad Report API
The Report API from Intelerad — 1 operation(s) for report.
Intelerad Session API
The Session API from Intelerad — 2 operation(s) for session.
Intelerad Storage API
The Storage API from Intelerad — 1 operation(s) for storage.
Intelerad Study API
The Study API from Intelerad — 4 operation(s) for study.
Intelerad Webhook API
The Webhook API from Intelerad — 1 operation(s) for webhook.
Scroll within the panel for all 9 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Intelerad Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Intelerad Finops
FINOPSSecurity 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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Intelerad — 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.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Access & Security 3
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/intelerad · machine-readable index on apis.io