VOA Health

Voa is a Brazilian healthcare-technology company providing an AI clinical documentation and patient-monitoring assistant that embeds directly into electronic patient record (EHR/PEP) systems, used by 60,000+ physicians across 1M+ consultations. Voa exposes integration surfaces — an embeddable plugin, an iFrame widget, and a browser extension — plus a REST integration API and an RNDS API that submits finalized clinical records to Brazil's Rede Nacional de Dados em Saúde (national health data network) in FHIR R4 using ICP-Brasil certificate authentication. Backed by Prosus Ventures.

VOA Health publishes 2 API contracts indexed on the APIs.io network: Authentication API and RNDS API. Tagged areas include Company, Health, Healthcare, Clinical Documentation, and Electronic Health Records.

The VOA Health catalog on APIs.io includes 1 Spectral governance ruleset.

VOA Health’s developer surface includes documentation, API reference, getting-started guide, engineering blog, signup flow, support, authentication, and 17 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

32.1/100 thin ▬ flat Agent 24/100 agent aware Front door AI 1/6 silent saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

2 published contracts 2 Agent Skills

Company Health Healthcare Clinical Documentation Electronic Health Records FHIRRNDSArtificial Intelligence Brazil

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 32.1/100 · thin

Contract Quality 2.7 / 19

Developer Ergonomics 9.9 / 15

Access Clarity 3.2 / 15

Operational Transparency 0.0 / 10

Contract Governance 2.9 / 9

Discoverability 5.5 / 8

Regulatory Posture 2.4 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 24/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 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

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

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 applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

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

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/voa-health/"><img src="https://apis.io/badge/voa-health/card.svg" alt="VOA Health on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

8 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 14.5 — up to +21.4 composite points
Access Clarity scores 21.1 — up to +15.8 composite points
Operational Transparency scores 0.0 — up to +13.0 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

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 the provider profile at artifacts.apis.io/voa-health/apis.yml: open an issue on github.com/api-evangelist/voa-health to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

HL7 FHIR

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

OpenAPI

measured — observed by APIs.io (published)

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

VOA Health Authentication API

The Authentication API from VOA Health — 1 operation(s) for authentication.

VOA Health RNDS API

Submit, query, replace, and delete clinical records on the RNDS national bus.

Open Collections 2

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Voa Integration Identify Authentication API

OPEN COLLECTION

Voa Integration Identify Authentication RNDS API

OPEN COLLECTION

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

correct-or-remove-rnds-record

AGENT SKILL

submit-clinical-record-to-rnds

AGENT SKILL

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

VOA Health API Rules

57 rules · 54 errors 1 warnings 2 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Voa Health Rnds Overlay

3 actions · update · voa-health-rnds-openapi.yml

GENERATED

Security Posture 2

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

Voa Health Authentication

3 schemes

SECURITY

Voa Health Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

GettingStarted

SignUp

Sandbox

Documentation 3

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

OpenAPI

OpenAPI

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

X-MCPServerCandidate

X-MCPServerCandidate

WellKnown

WellKnown

AgentSkill

AgentSkill

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

ErrorCatalog

Conventions

Conformance

Lifecycle

Components

DataModel

Access & Security 3

Authentication, authorization, and security posture

Authentication

Authentication

Compliance

Compliance

DomainSecurity

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

Support

Support

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

Overlay

Overlay

Source (apis.yml)

aid: voa-health
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/voa-health.png
name: VOA Health
description: Voa is a Brazilian healthcare-technology company providing an AI clinical documentation and patient-monitoring
  assistant that embeds directly into electronic patient record (EHR/PEP) systems, used by 60,000+ physicians across 1M+ consultations.
  Voa exposes integration surfaces — an embeddable plugin, an iFrame widget, and a browser extension — plus a REST integration
  API and an RNDS API that submits finalized clinical records to Brazil's Rede Nacional de Dados em Saúde (national health
  data network) in FHIR R4 using ICP-Brasil certificate authentication. Backed by Prosus Ventures.
url: https://raw.githubusercontent.com/api-evangelist/voa-health/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- prosus-ventures
x-tier: profiled
x-tier-reason: enriched-from-docs
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-21'
x-docs-platform: gitbook
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-17
tags:
- Company
- Health
- Healthcare
- Clinical Documentation
- Electronic Health Records
- FHIR
- RNDS
- Artificial Intelligence
- Brazil
tags_raw:
- Company
- Health
- Healthcare
- Clinical Documentation
- EHR
- FHIR
- RNDS
- Artificial Intelligence
- Brazil
apis:
- aid: voa-health:voa-health-authentication-api
  name: VOA Health Authentication API
  description: The Authentication API from VOA Health — 1 operation(s) for authentication.
  humanURL: https://docs.voa.health/integracao/rnds
  baseURL: https://integration.voa.health/v1
  tags:
  - Authentication
  properties:
  - type: OpenAPI
    url: openapi/voa-health-authentication-api-openapi.yml
  - type: Documentation
    url: https://docs.voa.health/integracao/rnds
  - type: APIReference
    url: https://docs.voa.health/integracao/rnds/endpoints
  - type: Documentation
    url: https://docs.voa.health/integracao/iframe/autenticacao
- aid: voa-health:voa-health-rnds-api
  name: VOA Health RNDS API
  description: Submit, query, replace, and delete clinical records on the RNDS national bus.
  humanURL: https://docs.voa.health/integracao/rnds
  baseURL: https://integration.voa.health/v1
  tags:
  - RNDS
  properties:
  - type: OpenAPI
    url: openapi/voa-health-rnds-api-openapi.yml
  - type: Documentation
    url: https://docs.voa.health/integracao/rnds
  - type: APIReference
    url: https://docs.voa.health/integracao/rnds/endpoints
  - type: Documentation
    url: https://docs.voa.health/integracao/iframe/autenticacao
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
- FN: Voa Integration Team
  email: integration@voahealth.com
common:
- type: Website
  url: https://voa.health
- type: DeveloperPortal
  url: https://docs.voa.health
- type: Documentation
  url: https://docs.voa.health
- type: APIReference
  url: https://docs.voa.health/integracao/rnds/endpoints
- type: GettingStarted
  url: https://docs.voa.health/inicio/quickstart
- type: Blog
  url: https://voa.health/blog
- type: SignUp
  url: https://app.voa.health
- type: Support
  url: mailto:integration@voahealth.com
- type: OpenAPI
  url: openapi/_original/voa-health-rnds-openapi.yml
- type: Overlay
  url: overlays/voa-health-rnds-overlay.yaml
- type: Authentication
  url: authentication/voa-health-authentication.yml
- type: ErrorCatalog
  url: errors/voa-health-problem-types.yml
- type: Conventions
  url: conventions/voa-health-conventions.yml
- type: Conformance
  url: conformance/voa-health-conformance.yml
- type: Compliance
  url: conformance/voa-health-conformance.yml
- type: Lifecycle
  url: lifecycle/voa-health-lifecycle.yml
- type: LLMsTxt
  url: llms/voa-health-llms.txt
- type: Components
  url: components/voa-health-components.yml
- type: Sandbox
  url: sandbox/voa-health-sandbox.yml
- type: DataModel
  url: data-model/voa-health-data-model.yml
- type: X-MCPServerCandidate
  url: mcp/voa-health-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: WellKnown
  url: well-known/voa-health-well-known.yml
- type: AgentSkill
  url: skills/_index.yml
- type: DomainSecurity
  url: security/voa-health-domain-security.yml
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 18
  pass: local-v1

VOA Health API — frequently asked questions

Does VOA Health have an API?

Yes. APIs.io lists 2 APIs from VOA Health, including VOA Health Authentication API and VOA Health RNDS API.

Is there an OpenAPI specification for the VOA Health API?

Yes. APIs.io indexes 2 OpenAPI specifications for VOA Health, each linked for download from this page.

How do I authenticate with the VOA Health API?

VOA Health uses bearer-token authentication (3 schemes). The details are profiled on APIs.io as Voa Health Authentication.

Is the VOA Health API ready for AI agents?

VOA Health has a Kin Score of 32.1 out of 100 (thin) and an Agent Readiness score of 23.8 (agent-aware), scored by API Evangelist on 2026-11-06.

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/voa-health"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/voa-health/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.