canonical: https://jentic.com/apis/zapcap.ai/zapcap

# ZapCap API

ZapCap API for automated video captioning and subtitle generation. The API exposes 3 endpoints secured with apiKey authentication.

## For AI agents

Programmatically upload a video file, upload video by url. Covers 3 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for media and content only.

## Capabilities

- Upload a video file
- Create a captioning task
- Integrate ZapCap API into automated workflows
- Query and filter ZapCap API records by parameters
- Monitor ZapCap API operational status and events

## Use cases

### Media and Content Operations

Use the ZapCap API to perform media operations programmatically. The API provides 3 endpoints covering core functionality including upload a video file, upload video by url, create a captioning task.

Example prompt: Call POST /videos to upload a video file

### Automated Tasks Management

Automate tasks operations by combining multiple ZapCap API endpoints. Agents can upload video by url and then create a captioning task in a single workflow.

Example prompt: Call POST `/videos/url` to upload video by url, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call ZapCap 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 apiKey tokens manually.

Example prompt: Search Jentic for 'upload a video file', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/videos` | Upload a video file |
| POST | `/videos/url` | Upload video by URL |
| POST | `/videos/{videoId}/task` | Create a captioning task |

## Key resources

- **Tasks** — Operations related to Tasks
- **Videos** — Operations related to Videos

## 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:** 65 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 45 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/zapcap.ai/zapcap/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 ZapCap by hand means setting its x-api-key header on every request, uploading video by file or by URL, and polling the task endpoint yourself. Through Jentic you install once, import ZapCap from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** ZapCap puts the video id in the URL path (`/videos/{videoId}/task`), so a rule can pin your agent to work on one uploaded video and start tasks for it. You choose the operations it may call, so it can create tasks for that video without being able to touch others.
- **Credential handling:** Your ZapCap 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.
- **Discovery method:** Agents search Jentic by intent such as 'upload a video for captioning' or 'start a video task', and Jentic returns the matching ZapCap operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Cloudinary** — Alternative media API
- **Mux** — Alternative media API

## FAQ

### What authentication does the ZapCap API use?

The ZapCap API uses an API key passed in the `x-api-key` 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 upload a video file with the ZapCap API?

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

### What are the rate limits for the ZapCap 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 upload a video file through Jentic?

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

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

The ZapCap API exposes 3 endpoints covering tasks, videos operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which ZapCap operations and credentials your agent may use. Since ZapCap carries the video id in the URL path (`/videos/{videoId}/task`), you can write a rule that pins the agent to one uploaded video and lets it start captioning tasks only for that video. You also choose whether it may call the upload operations (POST /videos and POST `/videos/url`) at all, so it cannot touch videos you did not authorize.