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

Authenticate and get an API key

Generate a new API key

Upload a video file

Create a video clip

Update video metadata

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.

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

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.

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.

Search Jentic for 'authenticate and get an API key', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

38 endpoints — skiv is a platform to store, manage, search, and share video.

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

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

Why Jentic?

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

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 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 '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

Alternatives and complements available in the Jentic catalogue.

Alternative

Shopify

Alternative e commerce API

Choose Shopify when you need a different approach to e commerce operations

Alternative

Stripe

Alternative e commerce API

Choose Stripe when you need a different approach to e commerce operations

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

Skiv API

Name: Skiv API
Brand: Skiv API
Availability: InStock

Official vendor OpenAPI document · agent-readyE CommerceStorefrontapiKey38 EndpointsREST

For Agents

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

Use for: I need to authenticate and get an API key, I want to generate a new API key, Search for upload a video file, Find all a video clip

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

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.

Jentic One on Github View OpenAPI Document