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.
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.
API Evangelist profiles Nabla the way a machine reads it — 35 machine-readable artifacts across 5 APIs, 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 45.3/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). 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.
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 1
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).
Nabla Core API
OPEN COLLECTIONPricing 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 six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Nabla Plans Pricing
PLANSRate 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
RATE LIMITSFinOps 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
FINOPSFeatures 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.
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.
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
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 7
Authentication, authorization, and security posture
Scroll within the panel for all 7 ·
Operate 3
Status, limits, changes, and where to get help
Company 5
The organization behind the API
Other 3
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