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.

Hyro is profiled on the APIs.io network. Tagged areas include Company, Artificial Intelligence, Conversational AI, AI Agents, and Healthcare.

Hyro’s developer surface includes engineering blog and 11 more developer resources.

🌐 Visit website 📡 Source on GitHub

6.2/100 minimal ▬ flat Agent 3/100 human only Front door AI 6/6 dominant Full breakdown ↓
scored 2026-09-25 · rubric v0.23.0

0 APIs

Company Artificial Intelligence Conversational AI AI Agents Healthcare Patient Engagement Customer Communication Voice

Kin Score

Kin Score How this is scored →
scored 2026-09-25 · rubric v0.23.0

Composite quality — 6.2/100 · minimal

Contract Quality 0.0 / 21

Developer Ergonomics 0.4 / 17

Access Clarity 0.0 / 17

Operational Transparency 1.7 / 11

Contract Governance 0.0 / 10

Discoverability 4.1 / 9

Regulatory Posture 0.7 / 15

Agent readiness — 3/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 0 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Health regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/hyro: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Pricing Plans 1

Published pricing tiers and plan structures.

Hyro Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Hyro Rate Limits

0 limits

RATE LIMITS

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Hyro Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

WellKnownProbe

WellKnownProbe

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Lifecycle

Lifecycle

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

RateLimits

RateLimits

StatusPage

StatusPage

Commercial 1

Pricing, plans, and the legal terms of use

Plans

Plans

Company 3

The organization behind the API

LinkedIn

Blog

Blog

Website

Website

Other 3

Properties that don't map to a standard resource type

Successor

Successor

SecondaryMarket

SecondaryMarket

RegulatoryPosture

RegulatoryPosture

Source (apis.yml)

aid: hyro
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - none
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source: []
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/hyro.png
name: Hyro
description: 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.
url: https://raw.githubusercontent.com/api-evangelist/hyro/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- norwest-venture-partners
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- Artificial Intelligence
- Conversational AI
- AI Agents
- Healthcare
- Patient Engagement
- Customer Communication
- Voice
tags_raw:
- Company
- Artificial Intelligence
- Conversational AI
- AI Agents
- Healthcare
- Patient Engagement
- Customer Communications
- Voice
apis: []
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Successor
  url: https://www.hyro.ai/
- type: SecondaryMarket
  url: https://equityzen.com/company/airbudtechnologiesinc
- type: LinkedIn
  url: https://www.linkedin.com/company/hyroai
- type: Blog
  url: https://www.hyro.ai/blog/
- type: WellKnownProbe
  url: well-known/hyro-well-known.yml
- type: Plans
  url: plans/hyro-plans-pricing.yml
- type: RateLimits
  url: rate-limits/hyro-rate-limits.yml
- type: RegulatoryPosture
  url: regulatory/hyro-regulatory-posture.yml
- type: DomainSecurity
  url: security/hyro-domain-security.yml
- type: Lifecycle
  url: lifecycle/hyro-lifecycle.yml
- type: StatusPage
  name: Hyro AI Status
  url: https://status.hyro.ai
- type: Website
  url: https://hyro.ai
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/hyro"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/hyro/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/hyro/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.