Skiv API

Name: Skiv API
Brand: Skiv API
Availability: InStock

✓ Official Vendor SpecMediaVideo ProcessingapiKey38 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the Skiv API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Skiv API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fskiv.com%2Fskiv" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fskiv.com%2Fskiv" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Skiv API.

Create key using password

Generate new authentication key

Upload video file

Cut clip from video

GET STARTED

Start building with Skiv API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Skiv API for, with concrete tasks.

★ 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.

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.

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.

Search Jentic for 'create key using password', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

38 endpoints — skiv is a video hosting and ai analysis platform.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Skiv API through Jentic.

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.

Skiv API

Connect the Skiv API to your agent

Capabilities

Start building with Skiv API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs