Tools
Audio to JSON API
Submit any audio file. Get back a transcript with timestamps, duration, and metadata as structured JSON.
Try it below:
Turn audio files into structured JSON
Upload an audio file or submit a URL, get structured JSON back.
What is Exabase's audio to JSON API?
Submit an audio file to the Exabase Extract API and get structured JSON back. The response includes a full transcript, duration, MIME type, file size, a CDN-hosted thumbnail, and the transcript text split into searchable chunks with start and end timestamps. MP3, WAV, M4A, OGG, FLAC, and other major formats are supported.
The same POST /v2/extract endpoint accepts both file uploads and URLs pointing to hosted audio. Transcription and chunking happen on Exabase's infrastructure. No speech-to-text model to host, no FFmpeg, no GPU provisioning on your end.
What you get back
The response includes the audio duration, a full transcript, and the transcript split into chunks. Each chunk carries a timeStart and timeEnd in seconds, so you can map any piece of text back to the exact moment in the recording. You also get MIME type, file size, total chunk count, and a CDN-hosted thumbnail. The API reference has the complete response schema.
One multi-modal API
The same POST /v2/extract endpoint handles every content type Exabase supports. For audio, it transcribes and returns timestamped chunks. For video, it does the same with the addition of frame dimensions. For PDFs, it returns page count, author, title, and (for recognised document types like invoices, contracts, and resumes) structured field extraction. For images, it runs OCR. For web pages, it renders JavaScript and extracts the content.
The submission flow is identical across all types: one endpoint, one SDK method, one webhook configuration. You learn the pattern once and use it for everything. The Extract docs cover each content type in detail.
What you can build with it
The timestamped chunks are the same format used across the Exabase platform. Feed them into a RAG pipeline so your agent can cite the exact moment in a recording. Build searchable podcast archives where users find the right episode and the right segment. Process customer support calls and extract structured insights from the transcript. Index meeting recordings so your team can search spoken content by topic.
Store transcribed audio as Resources in a Base and the content becomes searchable through Deep Search at the chunk level. Workers can re-extract updated recordings on a schedule, keeping your audio index current without manual work.
Beyond transcription
The Extract API returns more than a transcript. You get structured metadata, a CDN-hosted thumbnail, and chunks you can index directly. Store the output as a Resource and it's searchable through Deep Search immediately. Extract key facts from the transcript into Memory so your agent retains what it heard between sessions. The Submitting Jobs guide at https://exabase.io/docs/developer-guide/extraction/submitting-jobs walks through the full flow.
How do I use it?
Get your API key
Free, no credit card:
Sign up at exabase.io and copy your API key from the dashboard.
Submit an audio file
Using the SDK (Node.js):
Get the result
Poll the job until state reaches completed, or skip polling entirely with webhooks.
One API call. No speech-to-text model, no FFmpeg, no GPU.
Why Exabase
Works with other Exabase features
Use cases
FAQs
What is Exabase?
Exabase is infrastructure for AI agents. It gives your agents memory, versioned file storage, AI deep search, and context automation through a set of APIs. Store what your agent learns, search inside any content type, and keep knowledge bases current automatically. Built for production use. Give your agent precise context and cut your token spend by up to 81%.
Who uses Exabase?
Developers and teams building AI agents, copilots, and RAG applications. If your agent needs to remember things between sessions, store and retrieve files, search across documents and media, or stay up to date without manual maintenance, Exabase handles that infrastructure so you can focus on your product.
How fast is transcription?
Processing time depends on the file length and format. Most audio files complete in seconds to a few minutes. Processing is asynchronous, so your application is not blocked while transcription runs.
What audio formats are supported?
MP3, WAV, M4A, OGG, FLAC, and other major audio formats. The API auto-detects the content type and processes accordingly.
Do I have to poll for results?
No. You can configure a webhook URL and Exabase will POST the full result to your server when processing completes. The webhooks guide covers setup.
What do transcript chunks look like?
Each chunk contains the transcript text, a sequence number, and timeStart / timeEnd values in seconds. You can map any piece of text back to the exact moment in the recording.
Can I submit a URL instead of uploading a file?
Yes. Pass a url field in the request body pointing to a publicly accessible audio file. Exabase fetches and processes it.
What happens if extraction fails?
The job state moves to failed. You can call the reprocess endpoint to retry without re-uploading the original file.
How long are files retained?
Stored files are retained for 1 day from job creation, then permanently deleted. Download or copy anything you need before the retention window expires.
Can I use the transcript with other Exabase features?
Yes. Store transcribed audio as a Resource in a Base and the content becomes searchable through Deep Search. Extract key facts into Memory so your agent retains what it heard. Workers can re-extract updated recordings on a schedule.
How is this different from the Audio Transcription tool?
The Audio Transcription page focuses on the transcript output specifically. Audio to JSON covers the full extraction response: metadata, duration, thumbnail, transcript, and chunks. Same underlying API, different emphasis.
Is there an SDK?
Yes. The @exabase/sdk package for Node.js/TypeScript handles file streaming, job polling, and chunk retrieval. Install with npm install @exabase/sdk. Or call the REST API directly from any language.
What other content types does Extract support?
PDFs, images (with OCR), video files (with transcription), web pages, and documents. The same POST /v2/extract endpoint handles all of them. See the PDF to JSON, Image to JSON, Video to JSON, and Website to JSON tool pages.