Files
OmniRoute/docs/reference
Diego Rodrigues de Sa e Souza 9b5415a414 feat: add Gladia as an async speech-to-text provider (#6657) (#7603)
* feat(providers): add Gladia as an async speech-to-text provider (#6657)

Adds Gladia's async pre-recorded transcription API (upload → POST
/v2/pre-recorded → poll result_url) following the existing
AssemblyAI/Kie.ai async-STT pattern:

- New `gladia` entry in AUDIO_TRANSCRIPTION_PROVIDERS
  (open-sse/config/audioRegistry.ts), authenticated via the
  `x-gladia-key` custom header.
- New `handleGladiaTranscription()` handler
  (open-sse/handlers/audioTranscription.ts) wired into the
  format dispatch table.
- New `x-gladia-key` case in `buildAuthHeaders()`
  (open-sse/config/registryUtils.ts).
- Registered `gladia` in AUDIO_ONLY_PROVIDERS
  (src/shared/constants/providers/audio.ts) so it appears in the
  auto-generated provider catalog; regenerated
  docs/reference/PROVIDER_REFERENCE.md (250 -> 251 providers) and
  synced the plain-text provider counts in README.md, AGENTS.md,
  and CLAUDE.md.

Real-time/streaming transcription is explicitly out of scope for
this change — OmniRoute has no WebSocket audio-ingestion layer
today; only the async/pre-recorded path (which covers every other
async STT provider already wired in) is implemented.

Tests: 5 new node:test cases in
tests/unit/audio-transcription-handler.test.ts covering the
upload→submit→poll happy path, a terminal Gladia error, and a
missing result_url guard, plus a buildAuthHeaders case in
tests/unit/registry-utils.test.ts for the new x-gladia-key header.

* chore(providers): sync provider counts to 253 + fix base-red APIKEY partition count 168→169 (#6657)

Rebasing gladia onto the advanced release surfaced two count drifts the
RUN_ALL suite trips on: (1) docs provider count is now 253 (multiple
providers merged since this branch was cut); (2) providers-constants-split
already expects 168 but the release has 169 APIKEY entries — a pre-existing
base-red from an earlier provider merge that didn't update the test. Gladia
is STT (adds no APIKEY entry), so 169 is the correct value; aligning it here
also un-reds the release. All 4 partition/dedup checks still enforced.
2026-07-17 11:45:00 -03:00
..
2026-07-04 13:00:30 -03:00
2026-06-29 08:40:06 -03:00
2026-07-13 09:12:40 -03:00
2026-07-13 09:12:40 -03:00
2026-07-13 09:12:40 -03:00