canonical: https://jentic.com/apis/transkriptor.com/transkriptor-api

# Transkriptor API

Transkriptor API provides audio and video transcription services with speaker recognition, AI chat, and text-to-speech capabilities. The API exposes 20 endpoints secured with bearer authentication.

## For AI agents

Programmatically transcribe local file, transcribe meeting. Covers 20 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for ai and machine learning only.

## Capabilities

- Transcribe local file
- Get file content
- Rename file
- Delete file
- Monitor Transkriptor API operational status and events

## Use cases

### AI and Machine Learning Operations

Use the Transkriptor API to perform ai ml operations programmatically. The API provides 20 endpoints covering core functionality including transcribe local file, transcribe meeting, transcribe via url.

Example prompt: Call POST /transcribe/local to transcribe local file

### Automated Transcription Management

Automate transcription operations by combining multiple Transkriptor API endpoints. Agents can transcribe meeting and then transcribe via url in a single workflow.

Example prompt: Call POST /transcribe/meeting to transcribe meeting, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Transkriptor API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'transcribe local file', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /transcribe/local | Transcribe local file |
| POST | /transcribe/meeting | Transcribe meeting |
| POST | /transcribe/url | Transcribe via URL |
| GET | /files/{file_id}/content | Get file content |
| GET | /files/{file_id} | Get file detail |
| PATCH | /files/{file_id} | Rename file |
| DELETE | /files/{file_id} | Delete file |
| GET | /meetings/{meeting_id} | Get meeting details |

## Key resources

- **Transcription** — Audio and video transcription operations
- **Files** — File management operations
- **Meetings** — Meeting recording operations
- **Folders** — Folder management
- **User** — User account operations

## Why Jentic

- **Setup:** Wiring the Transkriptor API by hand means setting up its bearer token auth against app.transkriptor.com and coordinating its transcribe-then-fetch flow yourself. Through Jentic you install once, import the Transkriptor API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Transkriptor puts the file id in the URL path (/files/{file_id}), so a rule can pin your agent to one file: it can read that file's content and nothing else. You choose the operations it may call, so a file update or a file deletion is not included unless you add it.
- **Credential handling:** Your Transkriptor API token 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.
- **Discovery method:** Agents search Jentic by intent such as 'transcribe a local file' or 'get a transcribed file's content', and Jentic returns the matching Transkriptor API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Openai** — Alternative ai ml API
- **Anthropic** — Alternative ai ml API
- **Cohere** — Complementary ai ml API
- **Huggingface** — Complementary ai ml API

## FAQ

### What authentication does the Transkriptor API use?

The Transkriptor API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I transcribe local file with the Transkriptor API?

Yes. Use the POST /transcribe/local endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Transkriptor API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I transcribe local file through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'transcribe local file'. Jentic returns the matching Transkriptor API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Transkriptor API have?

The Transkriptor API exposes 20 endpoints covering transcription, files, meetings operations.

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

Yes. Jentic One is self-hosted, so you set the rules that decide which Transkriptor operations and credentials your agent can use. Because Transkriptor puts the file id in the URL path (/files/{file_id}), you can pin the agent to a single file and let it read only that file's content. You pick the operations it may call, so renaming a file (PATCH /files/{file_id}) or deleting one (DELETE /files/{file_id}) stays off unless you add it.