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

# Skiv API

Skiv is a video hosting and AI analysis platform. The API provides endpoints for video upload, management, collections, search, subtitles, audio/image analysis, and more. The API exposes 38 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create key using password, generate new authentication key. Covers 38 operations with apiKey authentication.

## Scope

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

## Capabilities

- Create key using password
- Generate new authentication key
- Upload video file
- Cut clip from video
- Update video metadata
- Remove video
- List all videos

## Use cases

### Media and Content Operations

Use the Skiv API to perform media operations programmatically. The API provides 38 endpoints covering core functionality including create key using password, generate new authentication key, upload video file.

Example prompt: Call POST /api/auth/login to create key using password

### Automated Audio Analysis Management

Automate audio analysis operations by combining multiple Skiv API endpoints. Agents can generate new authentication key and then upload video file in a single workflow.

Example prompt: Call POST /api/auth/keys to generate new authentication key, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Skiv 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 'create key using password', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /api/auth/login | Create key using password |
| POST | /api/auth/keys | Generate new authentication key |
| POST | /api/files/upload | Upload video file |
| POST | /api/files/cut | Cut clip from video |
| POST | /api/files/set/{fid} | Update video metadata |
| DELETE | /api/files/delete/{fid} | Remove video |
| GET | /api/files/videos | List all videos |
| GET | /api/files/videos/{svid} | Get specific video |

## Key resources

- **Audio Analysis** — Operations related to Audio Analysis
- **Authentication** — Operations related to Authentication
- **Collections** — Operations related to Collections
- **Concepts** — Operations related to Concepts
- **Image Analysis** — Operations related to Image Analysis

## Why Jentic

- **Setup:** Wiring Skiv by hand means logging in at skiv.com to mint a Key, sending it in the Key header on every request, and managing file upload and cut calls yourself. Through Jentic you install once, import Skiv from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Skiv puts the file id in the URL path (/api/files/set/{fid} and /api/files/delete/{fid}), so a rule can pin your agent to specific file operations. You choose the operations it may call, so destructive ones like file deletion are not included unless you add them.
- **Credential handling:** Your Skiv 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.
- **Discovery method:** Agents search Jentic by intent such as 'upload a video file' or 'list videos', and Jentic returns the matching Skiv 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 Skiv API use?

The Skiv API uses an API key passed in the `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 create key using password with the Skiv API?

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

### What are the rate limits for the Skiv 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 create key using password through Jentic?

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

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

The Skiv API exposes 38 endpoints covering audio analysis, authentication, collections operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Skiv operations and credentials the agent may use, so you can grant read-only calls like listing videos or uploading a clip while leaving destructive ones out. Skiv puts the file id in the URL path for operations such as updating metadata via /api/files/set/{fid} and removing a video via /api/files/delete/{fid}, so a rule can pin the agent to specific files. Deletion is only available to the agent if you explicitly add it to the allowed operations.