AIRe Link API
★ Only Publicly Available OpenAPI DocumentCommunicationsVideo Conferencingbearer24 EndpointsREST
For Agents
Initiate remote assistance video calls, generate QR-coded session links, and manage workers, devices, and webhooks for AIRe Link.
Use for: Start a remote assistance call with a contact, I want to create a QR code that launches an AIRe Link session, List recent calls for my account, Add a new worker to a team
Not supported: Does not handle outbound voice calls, SMS, or general team chat — use for QR-launched remote assistance video sessions and related worker management only.
Jentic publishes the only available OpenAPI specification for AIRe Link API, keeping it validated and agent-ready. AIRe Link is a remote assistance platform that connects field workers with experts via video calls and AR-style guidance, generally launched by sending a one-time link or QR code to the user. The API exposes 24 endpoints covering accounts, calls, contacts, devices, messages, QR codes, exports, webhooks, and team and worker management. Authentication is via bearer token.
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.
1
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 | sh2
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 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.
Capabilities
What an agent can do with AIRe Link API.
Initiate remote assistance calls and list active or historical sessions via /calls
Generate and manage QR codes that launch a session when scanned by a user
Manage workers, teams, and contacts who can be invited into a call
Maintain a registry of connected devices for fleet-style remote support
Create and read messages tied to a remote assistance session
Register webhooks for call, message, and worker lifecycle events
Export session data for compliance and reporting
Use Cases
Patterns agents use AIRe Link API for, with concrete tasks.
★ Field Worker Remote Assistance
Connect a remote expert to a field worker by sending a one-time link via SMS, email, or QR code. POST /calls creates a call session, POST /qr-codes generates a launch QR for printed materials or stickers on equipment, and POST /messages records guidance text exchanged during the session.
Create a call inviting contact c_99 with subject 'pump line 4 repair', generate a QR code linking to that call, and send the QR url to the worker's email
QR-Launched Equipment Support
Place QR codes on physical equipment so anyone can launch a support call by scanning. POST /qr-codes creates a code tied to an account and asset reference, GET /qr-codes lists active codes for a fleet, and the call generated from a scan appears in /calls with the originating QR code captured.
Generate a QR code for asset_serial=SN-7842 with a default subject of 'Generator service request', then list all calls launched from that QR in the last 30 days
Compliance Export and Webhook Audit
Subscribe to webhook events for every call and message, then run scheduled exports for retention. POST /webhooks registers an endpoint to receive call.started, call.ended, and message.created events, and POST /exports queues an export of call data over a date range for compliance archival.
Register a webhook at https://hooks.example.com/aire for call.ended events, then create an export of all calls between 2026-05-01 and 2026-05-31
AI Agent Remote Support Coordinator
An agent triaging an inbound issue can spin up an AIRe Link call, attach the right contact, and dispatch a QR code automatically — through Jentic the bearer token stays in the vault and the agent only handles scoped operations.
Search Jentic for 'create an aire link call', load the POST /calls schema, create a call with contact c_99 and subject 'urgent line stoppage', and return the join URL
Key Endpoints
24 endpoints — jentic publishes the only available openapi specification for aire link api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/calls
Create a remote assistance call
GET
/calls
List calls
POST
/qr-codes
Create a QR code that launches a session
GET
/qr-codes
List QR codes
POST
/contacts
Create a contact
POST
/webhooks
Register a webhook subscription
POST
/exports
Create an export of call or message data
POST
/calls
Create a remote assistance call
GET
/calls
List calls
POST
/qr-codes
Create a QR code that launches a session
GET
/qr-codes
List QR codes
POST
/contacts
Create a contact
POST
/webhooks
Register a webhook subscription
POST
/exports
Create an export of call or message data
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
AIRe Link bearer tokens are stored encrypted in the Jentic vault. Jentic injects the Authorization header on every call so the agent context never contains the raw token.
Intent-based discovery
Agents search Jentic by intent (e.g. 'create an aire link call') and Jentic returns the matching operation and schema, no doc browsing required.
Time to first call
Direct AIRe Link integration: 1-2 days for auth, contact provisioning, and webhook handling. Through Jentic: under 1 hour.
Related APIs
Alternatives and complements available in the Jentic catalogue.
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 at https://app.jentic.com/sign-up.
What authentication does the AIRe Link API use?
AIRe Link uses HTTP bearer token authentication. Jentic stores the bearer token encrypted in the vault and adds the Authorization header on each call, so the agent never handles the raw token.
Can I create a QR code that launches a call with the AIRe Link API?
Yes. POST /qr-codes creates a code that, when scanned, opens an AIRe Link session. The code can carry a default subject and contact, making it suitable for printing onto equipment or service kits.
What are the rate limits for the AIRe Link API?
The spec does not declare formal rate limits. Treat /calls and /qr-codes as user-driven endpoints used at human pace; for bulk operations, prefer /exports rather than looping list calls.
How do I start a remote assistance call with the AIRe Link API through Jentic?
Run pip install jentic, search Jentic for 'create aire link call', load the schema for POST /calls, then execute with the contact ID and subject. Jentic applies the bearer Authorization header automatically.
Can I export call history for compliance with the AIRe Link API?
Yes. POST /exports queues an export for a date range and resource type, and GET /exports lists previously generated exports so they can be downloaded for retention archives.
GET STARTED