canonical: https://jentic.com/apis/temi.com/temi

# Temi API

Temi is an audio transcription service that uses computers to transcribe English audio or video into text. The API allows you to submit transcription jobs, retrieve transcripts, and manage your account. The API exposes 7 endpoints secured with bearer authentication.

## For AI agents

Programmatically submit job, list jobs. Covers 7 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for cloud infrastructure only.

## Capabilities

- Submit Job
- List Jobs
- Get Job Status
- Delete Job
- Share Transcript Editor URL

## Use cases

### Cloud Infrastructure Operations

Use the Temi API to perform cloud infrastructure operations programmatically. The API provides 7 endpoints covering core functionality including submit job, list jobs, get job status.

Example prompt: Call POST /jobs to submit job

### Automated Jobs Management

Automate jobs operations by combining multiple Temi API endpoints. Agents can list jobs and then get job status in a single workflow.

Example prompt: Call GET /jobs to list jobs, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Temi 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 'submit job', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/jobs` | Submit Job |
| GET | `/jobs` | List Jobs |
| GET | `/jobs/{jobId}` | Get Job Status |
| DELETE | `/jobs/{jobId}` | Delete Job |
| GET | `/jobs/{jobId}/transcript` | Get Transcript |
| POST | `/jobs/{jobId}/share` | Share Transcript Editor URL |
| GET | `/account` | Get Account Details |

## Key resources

- **Jobs** — Manage transcription jobs
- **Transcripts** — Retrieve and share transcripts
- **Account** — Account information

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 72 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 57 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 91 / 100
- **View full report:** https://jentic.com/apis/temi.com/temi/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Temi API by hand means setting up its bearer token, attaching it to every call against api.temi.com/v1, and building the job polling and retry handling for transcription jobs yourself. Through Jentic you install once, import the Temi API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The Temi API puts the job id in the URL path (`/jobs/{jobId}`), so a rule can pin your agent to one job: it can read that job and its transcript and nothing else. You choose the operations it may call, so ones like deleting a job are not included unless you add them.
- **Credential handling:** Your Temi 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 'submit a transcription job' or 'get a job transcript', and Jentic returns the matching Temi API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Amazonaws** — Alternative cloud infrastructure API
- **Azure** — Alternative cloud infrastructure API
- **Googleapis** — Complementary cloud infrastructure API
- **Digitalocean** — Complementary cloud infrastructure API

## FAQ

### What authentication does the Temi API use?

The Temi 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 submit job with the Temi API?

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

### What are the rate limits for the Temi 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 submit job through Jentic?

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

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

The Temi API exposes 7 endpoints covering jobs, transcripts, account operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which Temi API operations and credentials the agent may use. Because the job id sits in the URL path (`/jobs/{jobId}`), a rule can pin the agent to a single job so it only reads that job and its transcript through GET `/jobs/{jobId}` and GET `/jobs/{jobId}/transcript.` You choose the operations it may call, so destructive ones like DELETE `/jobs/{jobId}` or submitting new jobs via POST /jobs are excluded unless you add them.