Hyro
Hyro is a responsible AI-powered conversational and agentic communications platform, best known for deploying AI assistants and voice/chat agents for large healthcare systems as well as other regulated enterprises. Its platform automates patient and customer engagement across web, SMS, and voice channels — handling tasks such as appointment management, IT help-desk requests, call routing, and answering high-volume repetitive questions — using a knowledge-graph-driven natural language engine positioned around explainability and control. Hyro is headquartered in New York and is backed by Norwest Venture Partners. At enrichment time Hyro exposes no public developer API or OpenAPI specification; its public technical surface consists of a customer product dashboard (docs.hyro.ai) and a live operational status page (status.hyro.ai). This profile was surfaced from the Norwest portfolio and enriched from verifiable public signals only.
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 Hyro the way a machine reads it — 1 machine-readable artifact, 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 — Hyro scores 9.4/100 (minimal), 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.
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 Hyro
Each block below is one kind of artifact we hold for Hyro. 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 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 Hyro — 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.
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/hyro · machine-readable index on apis.io