3Scribe API

Name: 3Scribe API
Brand: 3Scribe API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAI/MLSpeechapiKey4 EndpointsREST

For Agents

Submit audio for transcription, poll for job status, retrieve transcripts, and delete completed jobs using a simple API-key flow.

Install Jentic One Beta

Connect the 3Scribe API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the 3Scribe 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

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 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 3Scribe API.

Submit a new transcription job for an audio file or URL via POST /transcribe

List all transcription jobs in the authenticated 3Scribe account

Retrieve a specific transcription job by ID, including its status and transcript output

GET STARTED

Start building with 3Scribe API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use 3Scribe API for, with concrete tasks.

★ Customer Call Transcription

Send recorded customer support or sales calls to 3Scribe for transcription so the resulting text can be summarised, searched, or fed into a CRM. POST /transcribe creates the job, GET /jobs/{jobId} polls until status is complete, and the response carries the transcript ready for downstream processing.

Submit the audio file at https://example.com/calls/12345.mp3 to POST /transcribe, poll GET /jobs/{jobId} every 30 seconds until status is complete, and return the transcript text.

Podcast Episode Transcription

Transcribe podcast or video audio at episode upload time so the content can be indexed, surfaced in show notes, or repurposed into blog posts. The single-call POST /transcribe accepts an audio source, and downstream code polls the job until the transcript is available.

Create a 3Scribe transcription job for episode 47, wait until the job status is complete, and write the transcript to the episode's CMS record.

Job Cleanup and Retention

Periodically prune transcription jobs that are older than the retention policy. List jobs via GET /jobs, filter completed jobs older than the cutoff, and call DELETE /jobs/{jobId} on each. This keeps account usage tidy and avoids hitting account-level limits.

List all transcription jobs, identify those older than 90 days with status complete, and delete each via DELETE /jobs/{jobId}.

Agent-Driven Transcription

Let an AI agent submit audio for transcription and wait on the result through Jentic. The agent searches by intent, loads the schema for /transcribe, supplies the audio source, and polls /jobs/{jobId} - credentials remain isolated in Jentic's vault.

Through Jentic, search 'transcribe audio', load the 3Scribe POST /transcribe schema, submit the supplied audio URL, and poll until the transcript is returned.

Key Endpoints

4 endpoints — jentic publishes the only available openapi specification for 3scribe api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/transcribe

Create a new transcription job

GET

/jobs

List transcription jobs

GET

/jobs/{jobId}

Get a specific transcription job

DELETE

/jobs/{jobId}

Delete a transcription job

POST

/transcribe

Create a new transcription job

GET

/jobs

List transcription jobs

GET

/jobs/{jobId}

Get a specific transcription job

DELETE

/jobs/{jobId}

Delete a transcription job

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your 3Scribe API 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 'get the status of a transcription job', and Jentic returns the matching 3Scribe operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using 3Scribe API through Jentic.

Why is there no official OpenAPI spec for 3Scribe API?

3Scribe publishes a developer reference at developers.3scri.be but no OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call 3Scribe API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the 3Scribe API use?

Each request must carry an APIKey header issued by 3Scribe. Through Jentic, the API key is stored encrypted in the vault and injected into the APIKey header at execution, so agents never see the raw secret.

How do I submit audio for transcription?

Call POST /transcribe with the audio source the API expects (typically a URL or upload reference). The endpoint returns a job ID - poll GET /jobs/{jobId} until the status indicates completion to retrieve the transcript.

How do I delete a finished transcription job?

Send DELETE /jobs/{jobId} with the job's identifier. This is useful for retention policies - list jobs first via GET /jobs, then delete the ones older than your retention threshold.

How do I transcribe an audio file with 3Scribe through Jentic?

Run pip install jentic, then search 'transcribe audio', load the 3Scribe /transcribe operation, supply the audio source, and execute. Run it through Jentic One, the self-hosted execution layer to receive an agent API key for execution.

Is transcription synchronous or asynchronous?

It is asynchronous. POST /transcribe returns a job that begins processing in the background; clients poll GET /jobs/{jobId} until the job's status indicates the transcript is ready. Plan retry and timeout handling around poll intervals rather than expecting an immediate transcript on submit.

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

Yes. Because you run Jentic One yourself, your own rules decide which 3Scribe operations and credentials your agent may use. Since the job id sits in the URL path for both reads and deletes, you can allow your agent to submit jobs with POST /transcribe and read its own jobs with GET /jobs and GET /jobs/{jobId} while leaving out DELETE /jobs/{jobId}. Deletion is only available to the agent if you explicitly add it to the operations it may call.

3Scribe API

Connect the 3Scribe API to your agent

Capabilities

Start building with 3Scribe API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs