Jentic publishes the only available OpenAPI specification for Nabla Core Server API, keeping it validated and agent-ready. Nabla is an AI clinical assistant that turns ambient clinical conversations into structured notes, normalized clinical data, and patient instructions. The Core Server API is the server-side variant for backend integrations: it issues OAuth tokens, manages clinician users, and runs the core ambient operations such as listening to encounters, generating digests and notes, normalizing clinical data, and producing patient-facing instructions.
19 endpointsJentic publishes the only available OpenAPI specification for Nabla Core User API, keeping it validated and agent-ready. Nabla is an AI clinical assistant that produces structured notes, normalized clinical data, and patient instructions from ambient encounter audio. The Core User API is the client-side variant: it powers clinician-facing applications with operations for transcription, digest generation, normalization, patient instructions, dot phrases, custom dictionary expressions, and JWT refresh and logout. It uses an HTTP bearer token minted per clinician.
24 endpointsStep 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.