Clnto API

Name: Clnto API
Brand: Clnto API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHealthcareEhr Emrbearer8 EndpointsREST

For Agents

Read and write patient records, schedule appointments, and pull clinical history through a compact set of healthcare endpoints secured by bearer tokens.

Install Jentic One Beta

Connect the Clnto API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Clnto API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 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 | sh

Step 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 instance

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

Capabilities

What an agent can do with Clnto API.

Retrieve a patient profile by patient identifier

List upcoming appointments for a clinic or provider

Book a new appointment slot tied to a patient and provider

GET STARTED

Start building with Clnto API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Clnto API for, with concrete tasks.

★ Patient Onboarding

Register new patients into the clinical system with structured demographic and contact data so that downstream scheduling, billing, and clinical record systems can attach to a single patient identifier. The Clnto API exposes the patients endpoint for creation and the patients/{patientId} endpoint for lookup, allowing onboarding flows to confirm new identifiers immediately. Typical integrations cover a few hundred new patients per clinic per month and complete in under a day with bearer-token auth.

Register a new patient with name, date of birth, and contact email, then read back the assigned patientId to confirm creation.

Appointment Booking

Schedule appointments for existing patients and list upcoming visits for a provider or clinic. The appointments endpoint supports both creating new bookings and listing existing ones, which lets reception and patient-portal flows surface availability and confirm slots in real time. Suitable for clinics handling a few hundred appointments per week without building a custom scheduling backend.

List all appointments for the next seven days and book a 30-minute follow-up for patient ID 12345 with the assigned provider.

Clinical Record Retrieval

Pull clinical records associated with a patient for use in care continuity, second-opinion workflows, or analytics pipelines. The records endpoint returns structured clinical data tied to a patient identifier, so downstream agents can summarise history, populate intake forms, or feed reporting dashboards. Integration is straightforward given the small endpoint surface and bearer-token auth.

Fetch all clinical records for patient ID 12345 and summarise the most recent diagnosis.

AI Agent Clinical Assistant

Allow AI agents to act on behalf of clinical staff by reading patient records, booking appointments, and updating demographics through Jentic. Agents discover Clnto operations by intent, load the relevant input schema, and execute the call without raw bearer tokens entering the model context. This pattern fits triage chatbots, voice-driven booking assistants, and admin copilots in small to mid-size clinics.

Search Jentic for the Clnto patient lookup operation, load the schema, and retrieve the record for patient ID 12345 using a scoped Jentic credential.

Key Endpoints

8 endpoints — jentic publishes the only available openapi specification for clnto api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/patients

List patients in the clinic system

POST

/patients

GET

/patients/{patientId}

Retrieve a single patient by ID

GET

/appointments

List appointments for the clinic

POST

/appointments

Book a new appointment

GET

/records

Retrieve clinical records

GET

/patients

List patients in the clinic system

POST

/patients

GET

/patients/{patientId}

Retrieve a single patient by ID

GET

/appointments

List appointments for the clinic

POST

/appointments

Book a new appointment

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Clnto bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context, which matters for HIPAA-aligned deployments.

Intent-based discovery

Agents search Jentic by intent such as 'look up a patient record', and Jentic returns the matching Clnto operation with its input schema, so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Clnto API through Jentic.

Why is there no official OpenAPI spec for Clnto API?

Clnto does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Clnto API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Clnto API use?

The Clnto API uses HTTP bearer token authentication. Every request must include an Authorization header with a bearer token issued by Clnto. Through Jentic, the bearer token is stored encrypted in your Jentic One instance and never enters the agent's context - agents receive scoped access at execution time only.

Can I book appointments through the Clnto API?

Yes. The /appointments endpoint accepts POST requests to create new bookings tied to a patient and provider, and GET requests to list existing appointments. Use it to drive booking flows, reschedule confirmations, and provider calendar views.

What are the rate limits for the Clnto API?

The OpenAPI spec does not declare explicit rate limits. Treat the API as a moderate-traffic clinical system: batch large reads, throttle automated workflows, and check Clnto's developer site at https://developers.clnto.com for the current published quota before going to production.

How do I retrieve a patient record through Jentic?

Search Jentic with the query 'look up a patient record', load the schema for the GET /patients/{patientId} operation, then execute with the patient identifier. Install the SDK with pip install jentic and call client.search, client.load, and client.execute in sequence.

Does the Clnto API support clinical record retrieval?

Yes. The /records endpoint returns clinical records linked to a patient identifier. It is the right entry point for care continuity flows, intake form pre-fill, and analytics pipelines that need patient history.

Can I limit what my agent is allowed to do with the Clnto API?

Yes. Because Jentic One is self-hosted, you write the rules that decide which Clnto operations your agent may call and which credential it uses. You can allow only read operations like GET /patients/{patientId} and GET /records while excluding POST /patients and POST /appointments, so the agent cannot register patients or book visits unless you add those operations. Since Clnto carries the patient id in the URL path, a rule can also pin the agent to a single patientId, letting it read that one patient's record and nothing else.

Clnto API

Connect the Clnto API to your agent

Capabilities

Start building with Clnto API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs