Gladia
Gladia is an AI audio infrastructure platform that offers speech-to-text transcription via both REST and WebSocket APIs, supporting asynchronous pre-recorded audio processing and real-time live transcription. The platform provides speaker diarization, automatic language detection across 100+ languages, word-level timestamps, and audio intelligence features powered by large language models. Authentication uses an API key passed via the x-gladia-key HTTP header against the base URL https://api.gladia.io/v2/. Gladia offers a free tier with 10 hours per month, metered paid plans starting at $0.61/hour for async and $0.75/hour for real-time, and custom enterprise pricing with zero data retention and SLA guarantees.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Gladia the way a machine reads it — 28 machine-readable artifacts across 9 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Gladia scores 61.1/100 (strong), with a separate agent-readiness read of 54/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Gladia
Each block below is one kind of artifact we hold for Gladia. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 9
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Gladia Live (Real-time) API
WebSocket API for real-time live audio transcription with sub-second latency, supporting multi-language detection, live speaker diarization, and streaming audio intelligence. In...
Gladia AudioToText API
The AudioToText API from Gladia — 1 operation(s) for audiototext.
Gladia File Management API
The File Management API from Gladia — 1 operation(s) for file management.
Gladia Job History API
The Job History API from Gladia — 1 operation(s) for job history.
Gladia Live V2 API
The Live V2 API from Gladia — 3 operation(s) for live v2.
Gladia OpenRouter API
The OpenRouter API from Gladia — 1 operation(s) for openrouter.
Gladia Pre-recorded V2 API
The Pre-recorded V2 API from Gladia — 3 operation(s) for pre-recorded v2.
Gladia Transcription V1 API
The Transcription V1 API from Gladia — 2 operation(s) for transcription v1.
Gladia Transcription V2 API
The Transcription V2 API from Gladia — 3 operation(s) for transcription v2.
Scroll within the panel for all 9 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Gladia Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Gladia Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Gladia Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Gladia Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Gladia API Rules
SPECTRALJSON Schema 5
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AudioUploadResponse
JSON SCHEMADiarizationConfigDTO
JSON SCHEMAInitPreRecordedTranscriptionResponse
JSON SCHEMAInitTranscriptionRequest
JSON SCHEMALiveEventPayload
JSON SCHEMAExamples 4
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Gladia Live Session Config
EXAMPLEGladia Upload Audio Url
EXAMPLESecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Gladia — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 7
Reference material describing how the API behaves
Scroll within the panel for all 7 ·
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/gladia · machine-readable index on apis.io