Install Jentic One Beta

Connect the Gladia API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Gladia 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgladia.io%2Fgladia" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgladia.io%2Fgladia" | 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 Gladia API.

Submit a hosted audio URL for asynchronous transcription via POST /v2/pre-recorded

Upload an audio file directly to Gladia via POST /v2/upload before submitting it

Poll a transcription job for completion via GET /v2/pre-recorded/{id}

Retrieve the original audio file used for a transcription via GET /v2/pre-recorded/{id}/file

Generate translation, summary, sentiment, and speaker diarisation alongside the transcript

GET STARTED

Start building with Gladia API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Gladia API for, with concrete tasks.

★ Meeting Recording Transcription

Transcribe Zoom, Google Meet, or in-person meeting recordings into searchable text with speaker labels. Upload the file via POST /v2/upload, submit the returned audio URL to POST /v2/pre-recorded with diarization=true and summarization=true, and poll GET /v2/pre-recorded/{id} until status is done to retrieve the transcript and per-speaker summary.

Upload meeting.mp4 via /v2/upload, call /v2/pre-recorded with the returned URL plus diarization=true and summarization=true, poll the job, and return the final transcript

Podcast Translation Pipeline

Translate podcast episodes into a target language for international distribution. Submit each episode URL to POST /v2/pre-recorded with translation enabled and the desired target_language, then read the translated transcript and original transcript side by side from the result payload.

Submit https://example.com/ep12.mp3 to /v2/pre-recorded with translation=true target_language=es, poll the job, return the Spanish transcript

Live Captioning for Webinars

Provide live captions for a webinar by opening a streaming session with POST /v2/live and connecting an audio source. The endpoint returns a session token that the client uses to stream PCM audio over WebSocket, receiving partial and final transcript chunks back in real time for on-screen display.

Open a /v2/live session with language=en and encoding=wav, return the websocket_url and session token to the client for audio streaming

AI Agent Voice Memo Capture

Use Jentic to let an AI agent transcribe ad-hoc voice memos a user uploads via chat. The agent issues an intent like 'transcribe an audio file', Jentic resolves POST /v2/upload then POST /v2/pre-recorded, executes both with the API key from the vault, and returns the polished transcript plus summary.

Through Jentic, upload memo.m4a, submit the resulting URL with summarization=true, poll until done, and return transcript and summary

Key Endpoints

6 endpoints — the gladia api provides speech-to-text and audio intelligence over both pre-recorded audio files and live streams.

METHOD

PATH

DESCRIPTION

POST

/v2/pre-recorded

Submit a pre-recorded audio URL for transcription

GET

/v2/pre-recorded/{id}

Poll a transcription job for results

GET

/v2/pre-recorded/{id}/file

Retrieve the original audio file for a job

POST

/v2/upload

Upload an audio file to Gladia hosting

POST

/v2/live

Open a live transcription session and return a websocket token

POST

/v2/pre-recorded

Submit a pre-recorded audio URL for transcription

GET

/v2/pre-recorded/{id}

Poll a transcription job for results

GET

/v2/pre-recorded/{id}/file

Retrieve the original audio file for a job

POST

/v2/upload

Upload an audio file to Gladia hosting

POST

/v2/live

Open a live transcription session and return a websocket token

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Gladia by hand means learning its x-gladia-key header auth and juggling the upload, pre-recorded, and live transcription steps yourself. Through Jentic you install once, import the Gladia API from the API Directory, store the key once, and your agent calls it.

Permission scoping

Gladia takes the audio target in the request body and returns a transcription id in the path, so scope the agent to the operations it needs, such as submitting a pre-recorded transcription and reading its result. You choose that operation set, so it transcribes and fetches without gaining unrelated calls unless you add them.

Credential isolation

Your Gladia key 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.

Intent-based discovery

Agents search Jentic by intent such as 'transcribe an audio file' or 'run live transcription', and Jentic returns the matching Gladia operation with its input schema so the agent calls the right endpoint with the correct diarisation and translation flags without browsing the reference docs.

FAQs

Specific to using Gladia API through Jentic.

What authentication does the Gladia API use?

Gladia uses an x-gladia-key API key sent as a request header. Generate the key from the Gladia dashboard. Through Jentic the key is stored encrypted in your Jentic One instance and the raw value never enters the agent's prompt context.

Can I transcribe an audio file with the Gladia API?

Yes. Either upload the file via POST /v2/upload to receive a hosted URL, or pass an existing URL directly to POST /v2/pre-recorded with optional flags such as diarization, translation, and summarization. Poll GET /v2/pre-recorded/{id} until status=done to read the transcript.

What are the rate limits for the Gladia API?

Gladia rate-limits by plan: the free tier allows up to 10 hours of pre-recorded transcription per month and lower concurrency on /v2/live, while paid plans raise both quotas. Concurrent jobs are also capped per workspace; check the dashboard usage panel for the live counter.

How do I run live transcription through Jentic with Gladia?

Search Jentic for 'start a live transcription session', load POST /v2/live, and execute with language and encoding. The response returns a websocket URL and session token that your client connects to for streaming PCM audio and receiving transcript chunks.

Does the Gladia API support speaker diarisation and translation?

Yes. Pass diarization=true on POST /v2/pre-recorded to label each speaker (speaker_0, speaker_1, etc.) and translation=true with target_language to return both the original and translated transcript in the result payload. Both can be combined on a single job.

What audio formats does Gladia accept?

Gladia accepts common formats including mp3, mp4, m4a, wav, flac, ogg, and webm for pre-recorded jobs, and PCM-encoded audio over WebSocket for live sessions. The /v2/upload endpoint streams the raw bytes; large files are supported but uploads time out after a few minutes if connection is slow.

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

Yes. Because you self-host Jentic One, your own rules decide which Gladia operations and credentials the agent may use, so you can grant only the calls it needs. For example, you can allow POST /v2/pre-recorded to submit a transcription and GET /v2/pre-recorded/{id} to read the result, while withholding POST /v2/upload, POST /v2/live, or GET /v2/pre-recorded/{id}/file. The agent transcribes and fetches within that set and gains no unrelated calls unless you add them.

Gladia API

Name: Gladia API
Brand: Gladia API
Availability: InStock

Official vendor OpenAPI document · agent-readyAI/MLSpeechapiKey6 EndpointsREST

For Agents

Transcribe pre-recorded audio files and live audio streams with optional translation, summarisation, and speaker diarisation via Gladia.

Use for: Transcribe a hosted audio file URL with Gladia, Upload an audio file to Gladia for transcription, Get the result of a Gladia transcription job, Start a live transcription session with Gladia

Not supported: Does not handle text-to-speech, voice cloning, or audio generation - use for transcribing and analysing speech audio only.

The Gladia API provides speech-to-text and audio intelligence over both pre-recorded audio files and live streams. Agents can submit a hosted audio URL or an uploaded file for transcription, then poll a job ID to retrieve the transcript along with optional translation, summarisation, sentiment analysis, and speaker diarisation. A live endpoint exposes a session-token flow for streaming audio in real time. Authentication is an x-gladia-key API key.

Jentic One on Github View OpenAPI Document

Connect the Gladia API to your agent

Capabilities

Start building with Gladia API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Gladia API