How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Nabla website screenshot

Nabla

Nabla provides ambient AI for clinicians through its Copilot product, which generates clinical notes from patient encounters across more than 85,000 clinicians and 150+ health organizations. Nabla also publishes a public Core API that exposes the same underlying capabilities (medical transcription, structured note generation, FHIR-normalized data extraction, multilingual patient summaries, magic edit, custom dictionary, dot phrases, and dictation) to third-party telehealth platforms, EHRs, and voice-enabled applications. Authentication uses OAuth 2.0 client credentials for the Server API and JWT-based access tokens for the User API.

agent aware

Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.

Kin Score

API Evangelist profiles Nabla the way a machine reads it — 38 machine-readable artifacts across 1 API, 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 — Nabla scores 42.2/100 (developing), with a separate agent-readiness read of 20/100 (agent aware). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Nabla Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from Nabla'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/nabla/"
   title="Nabla on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/nabla.svg"
       alt="Nabla Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile Nabla

Each block below is one kind of artifact we hold for Nabla. 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 5

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.

Nabla Core API

The Nabla Core API transcribes medical encounters, generates structured clinical notes (for example SOAP), extracts FHIR-normalized data with ICD-10 and LOINC coding, produces m...

Nabla Copilot Server API

The Server API is intended for server-to-server interactions, allowing backend systems to manage Copilot users and resources via OAuth 2.0 client credentials. OAuth clients can ...

Nabla Copilot User API

The User API enables client-side applications to act on behalf of an individual user by exchanging server-issued access and refresh tokens to autonomously call the Nabla Core AP...

Nabla Authentication API

OAuth and JWT token endpoints.

Nabla Transcription API

Medical-grade speech-to-text endpoints.

Open Collections 4

Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.

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

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.

Nabla Plans Pricing

1 plans

PLANS

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.

Nabla Rate Limits

2 limits

RATE LIMITS

FinOps 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.

Nabla Finops

FINOPS

Features 11

The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.

Notable capabilities this provider offers.

Ambient AI Documentation

Automatic generation of clinical notes from patient encounters.

Medical Transcription

Medical-grade speech-to-text via real-time WebSocket, REST, and async endpoints for audio files up to 60 minutes.

Note Generation

Transforms transcripts into structured clinical notes (for example SOAP) with customization options.

Magic Edit

Refine generated notes using natural-language instructions for last-mile customization.

Patient Summaries

Patient-friendly post-visit instructions with multilingual support.

FHIR Data Extraction

Extraction of FHIR-compatible structured data with ICD-10 and LOINC coding.

Medical Dictation

Real-time transcription of dictated clinician speech.

Dot Phrases

Auto-detection of provider-defined macros that expand into structured note sections.

Custom Dictionary

Specialized terminology for improved accuracy in niche domains.

Feedback Reporting

Structured feedback APIs for measuring and improving generated content.

Multi-Platform Copilot

Copilot app available as web app, iOS, Android, and Chrome extension.

Scroll within the panel for all 11 ·

Security Posture 4

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.

Nabla Authentication

http · 1 scheme

SECURITY

Nabla Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Nabla Vulnerability Disclosure

disclosure policy published

SECURITY

Nabla Trust Center

SOC 2, ISO 27001, HIPAA, GDPR

SECURITY

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.

Nabla Agentic Access

5 operations · 5 acting

5 operations · 5 acting

AGENTIC

Use Cases 4

What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.

What developers build with this provider.

Outpatient Documentation

Ambient note generation for outpatient visits.

Telehealth Documentation

Integrated documentation for telehealth providers.

EHR Integration

Sync notes and structured data into major EHRs.

Voice-Enabled Applications

Foundation for third-party voice-enabled clinical tools.

Integrations 6

Pre-built integrations with other platforms tell you where this provider already fits in a stack.

Pre-built integrations with other platforms and tools.

Epic

EHR integration partner.

athenahealth

EHR integration partner.

Oracle Health

EHR integration partner.

NextGen

EHR integration partner.

Arya

EHR integration partner.

Greenway

EHR integration partner.

Resources

Every other property we hold for Nabla — 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.

Get Started 1

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Operate 3

Status, limits, changes, and where to get help

Other 4

Properties that don't map to a standard resource type

← All providers · Data indexed from github.com/api-evangelist/nabla · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of Nabla, 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.