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

# Skiv API

Skiv is a platform to store, manage, search, and share video. Fast, easy, and secure. Built for teams that need video done right. The API exposes 38 endpoints secured with apiKey authentication.

## For AI agents

Programmatically authenticate and get an API key, generate a new API key. Covers 38 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- Authenticate and get an API key
- Generate a new API key
- Upload a video file
- Create a video clip
- Update video metadata
- Delete a video
- List all videos

## Use cases

### E-Commerce Operations

Use the Skiv API to perform e commerce operations programmatically. The API provides 38 endpoints covering core functionality including authenticate and get an API key, generate a new API key, upload a video file.

Example prompt: Call POST `/auth/login` to authenticate and get an API key

### Automated Authentication Management

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

Example prompt: Call POST `/auth/keys` to generate a new API 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 'authenticate and get an API key', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/auth/login` | Authenticate and get an API key |
| POST | `/auth/keys` | Generate a new API key |
| POST | `/files/upload` | Upload a video file |
| POST | `/files/cut` | Create a video clip |
| POST | `/files/set/{fid}` | Update video metadata |
| DELETE | `/files/delete/{fid}` | Delete a video |
| GET | `/files/videos` | List all videos |
| GET | `/files/videos/{svid}` | Get a single video |

## Key resources

- **Authentication** — Login and key management
- **Videos** — Video upload and management
- **Subtitles** — Subtitle management
- **Collections** — Video collection management
- **Search** — Search across 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:** 61 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 87 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 45 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 56 / 100
- **View full report:** https://jentic.com/apis/skiv/skiv/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 Skiv by hand means logging in via `/auth/login` at api.skiv.com to obtain a Key, passing it in the Key header on every call, and handling file upload and cut operations 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 (`/files/set/{fid}` and `/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 'fetch a video by id', 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

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce 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 authenticate and get an API key with the Skiv API?

Yes. Use the POST `/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 authenticate and get an API key through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'authenticate and get an API key'. 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 authentication, videos, subtitles operations.

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

Yes. Because Jentic One is self-hosted, you decide which Skiv operations and credentials your agent may use, so you can allow read-only calls like listing videos or fetching a single video while withholding write operations. Since Skiv puts the file id in the URL path for operations such as `/files/set/{fid}` and `/files/delete/{fid}`, your rules can pin the agent to specific files or actions. Destructive operations like deleting a video are excluded unless you explicitly add them.