AIRe Link API

Name: AIRe Link API
Brand: AIRe Link API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHealthcareAppointment SchedulingapiKey324 EndpointsREST

For Agents

Manage remote clinical video calls, clients, contacts, devices, and structured care guides on the AIRe Link telehealth platform.

Install Jentic One Beta

Connect the AIRe Link API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AIRe Link 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 AIRe Link API.

Create and manage remote-care video calls and their participants via /calls

Look up and update client records on the AIRe Link platform through /clients

Manage clinician and partner contacts via /contacts

GET STARTED

Start building with AIRe Link API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for AIRe Link API, keeping it validated and agent-ready. AIRe Link is a remote-care and clinical-collaboration platform that lets healthcare providers run video calls, collect structured clinical guides, manage clients and contacts, and exchange files with patients and partner clinicians. The API surfaces 324 operations across accounts, calls, clients, contacts, devices, exports, file libraries, forms, guide templates, and webhooks, making it suitable for embedding remote-consultation flows into a wider EHR or care-coordination product. Authentication is via the X-API-Key header.

Use Cases

Patterns agents use AIRe Link API for, with concrete tasks.

★ Embedded remote consultation

Embed AIRe Link's video consultation flow inside a wider clinical product by creating a client through /clients, scheduling a call through /calls, and exposing the join link to both clinician and patient. The platform handles WebRTC plumbing, recording, and post-call notes; the embedding application keeps ownership of the appointment record. Suitable for telemedicine, remote diagnostics, and second-opinion services.

POST a new call via /calls referencing an existing client and a clinician contact, then return the call id and join URL.

Structured pre-consultation triage

Send a structured clinical guide to a patient before a consultation using /guide-templates and /guides, then receive the responses through /guide-data. The clinician arrives at the call with the patient's reported symptoms, vital signs, and consent already captured, shortening the call and feeding straight into the medical record. Particularly valuable for chronic-care and pre-surgical workflows.

Pick a guide template via /guide-templates, instantiate it for a client through /guides, then poll /guide-data until the patient submits responses.

Care coordination across partners

Coordinate care across a primary clinic and partner specialists by sharing client records and files via /contacts and /file-libraries. Webhooks notify each partner when a new file or call is created, so an agent can keep the partner clinic's record system in sync without manual handoff. Reduces faxing and email-attachment workflows still common in healthcare.

On a /file-libraries 'file added' webhook, fetch the file metadata and forward a copy via /files to the partner contact's library.

Agent integration via Jentic

Wire AIRe Link into a clinical assistant agent through Jentic. The agent searches for the right operation by intent (schedule a call, send a guide, fetch a contact) and Jentic returns the matching schema from across the 324 endpoints. The X-API-Key sits in your Jentic One instance, satisfying the basic confidentiality bar required for healthcare operational tooling.

Search Jentic for 'schedule a remote consultation', load /calls (POST), and execute it with client_id, contact_id, and scheduled_at.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/calls

List remote consultation calls

GET

/clients

List clients on the platform

GET

/contacts

List clinician and partner contacts

GET

/guides

List structured clinical guides

GET

/guide-templates

List available guide templates

GET

/file-libraries

List file libraries shared between clinicians and clients

GET

/devices

List connected devices

GET

/exports

List or trigger data exports

GET

/calls

List remote consultation calls

GET

/clients

List clients on the platform

GET

/contacts

List clinician and partner contacts

GET

/guides

List structured clinical guides

GET

/guide-templates

List available guide templates

GET

Why Jentic?

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

Credential isolation

Your AIRe Link X-API-Key is stored once, encrypted, by your own Jentic One instance and injected as the header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'schedule a remote video consultation', and Jentic returns the matching AIRe Link 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 AIRe Link API through Jentic.

Why is there no official OpenAPI spec for AIRe Link API?

AIRe Link does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AIRe Link 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 AIRe Link API use?

The AIRe Link API uses an API key passed in the X-API-Key header on every request. Keys are issued from your AIRe Link admin console and scoped per environment. Through Jentic the key is held in your Jentic One instance and injected at execution time.

Can I schedule a remote consultation through the AIRe Link API?

Yes. POST to /calls with the client_id, clinician contact_id, and scheduled_at to create a consultation. The response includes the call id and the join URLs for clinician and patient. GET /calls/{id} returns the call's state and any recordings or notes attached after it ends.

What are the rate limits for the AIRe Link API?

AIRe Link does not publish public rate limits in the OpenAPI metadata; in practice the platform is provisioned per tenant with limits in the low thousands of requests per minute. Agents should respect 429 responses with exponential backoff and avoid tight polling on high-cardinality endpoints like /guide-data.

How do I send a structured pre-consultation guide through Jentic?

Search Jentic for 'send AIRe Link guide to client', load the /guides POST operation, and execute it with template_id and client_id. The patient receives a notification, fills in the guide, and the responses become available on /guide-data for the same guide id.

Does the AIRe Link API support webhooks?

Yes. The API exposes webhook configuration so that a partner system can subscribe to events such as new calls, file uploads, and guide submissions. Use the webhook endpoints to register a callback URL; AIRe Link delivers signed JSON payloads for each subscribed event type.

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

Yes. Because you run Jentic One yourself, your own rules decide which AIRe Link operations and credentials the agent may use, so you can allow read-only calls like listing calls or clients while excluding everything else. The collection routes address records through query parameters and request bodies rather than ids in the path, so granting a listing operation does not expose write actions. Actions such as scheduling a consultation are separate operations that the agent can only call if you add them to the allowed set.