Iris Telehealth
Iris Telehealth is an Austin, Texas telepsychiatry company, founded in 2013, that delivers virtual behavioral health care to healthcare organizations rather than direct to consumers. It contracts psychiatrists, psychiatric nurse practitioners, LCSWs and LPCs to hospitals and health systems, community mental health centers, community health centers and FQHCs, and Certified Community Behavioral Health Clinics, covering pediatric through geriatric populations and low-acuity therapy through high-acuity psychiatry. Its service lines are Virtual Clinic (comprehensive care and behavioral health integration), On-Demand Services (24/7 emergency department psychiatry support), Scheduled Services (matched provider staffing), Bridge Clinic, and Iris Insights, an AI-enabled behavioral health analytics platform covering risk optimization, capacity management, a behavioral health command center and revenue cycle analytics. The company reports over 430 clinicians and over 210 partner organizations, and has been accredited by the Joint Commission for behavioral health care since 2019, earning recertification since. Its delivery model is deliberately technology-agnostic: Iris clinicians work inside each partner's existing EMR/EHR and e-prescribing tools over HIPAA-compliant video, so the integration burden sits with the partner's systems. Iris Telehealth publishes no public developer program, API documentation, SDKs, or machine-readable API contract, and operates no public GitHub organization.
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 Iris Telehealth 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 — Iris Telehealth scores 12.9/100 (emerging), with a separate agent-readiness read of 0/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.
Why this profile is thin
Iris Telehealth sells clinician hours and a managed analytics service, not software an integrator can call: its own model is technology-agnostic — Iris psychiatrists work inside the partner health system's existing EHR — so the only API in the workflow belongs to the partner's Epic or Cerner instance, and the 69-page marketing site has no developer, docs, or API page at all, while the one API-shaped hostname it does publish, api.iristelehealth.com, resolves in DNS to 18.118.52.125 but refuses every connection on both 443 and 80 from the public internet.
This is an honest zero, not a gap in our research. Iris Telehealth does not appear to expose an API, so there is nothing here for us to index and nothing for them to fix.
What we probed
https://api.iristelehealth.com/→ HTTP 0https://iristelehealth.com/openapi.json→ HTTP 404https://iristelehealth.com/swagger.json→ HTTP 404https://iristelehealth.com/api-docs→ HTTP 404https://iristelehealth.com/graphql→ HTTP 404https://iristelehealth.com/llms.txt→ HTTP 404https://iristelehealth.com/.well-known/agent-card.json→ HTTP 404https://iristelehealth.com/.well-known/agent.json→ HTTP 404https://iristelehealth.com/.well-known/security.txt→ HTTP 404https://iristelehealth.com/.well-known/api-catalog→ HTTP 404https://iristelehealth.com/page-sitemap.xml→ HTTP 200https://iristelehealth.com/wp-json/→ HTTP 200
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-08-24 · rubric v0.12.1
Put this on your own site. The badge is drawn live from Iris Telehealth's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/iris-telehealth/"
title="Iris Telehealth on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/iris-telehealth.svg"
alt="Iris Telehealth Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/iris-telehealth/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/iris-telehealth/"
title="Iris Telehealth on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/iris-telehealth/card.svg"
alt="Iris Telehealth Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Iris Telehealth
Each block below is one kind of artifact we hold for Iris Telehealth. 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.
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 things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Security 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 Iris Telehealth — 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
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Access & Security 2
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 5
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/iris-telehealth · machine-readable index on apis.io
This is an independent, third-party profile of Iris Telehealth, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.