Install Jentic One Beta

Connect the KinoPipe API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the KinoPipe 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%2Fkinopipe.com%2Fkinopipe" | 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%2Fkinopipe.com%2Fkinopipe" | 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 KinoPipe API.

Run a ready-made video tool by slug, such as trim-video, compress-video, video-to-vertical, or add-subtitles-to-video

Chain up to 12 editing operations, including trim, resize, crop, watermark, picture-in-picture, and concat, in one job

Upload a local file directly with filename, contentType, and byteSize, then reuse its mediaUrl as a job input

Cap what a request may bill with maxCredits, checked before the work starts

GET STARTED

Start building with KinoPipe API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use KinoPipe API for, with concrete tasks.

★ AI agent video editing through Jentic

An agent asked to cut or reformat a clip searches Jentic for 'trim a video', loads the KinoPipe tool operation with its input schema, and runs the trim-video tool on a public URL with a maxCredits ceiling. Your own Jentic One instance attaches the kp_live_ key at call time, and the agent reads the finished output by jobId.

Call POST /api/v1/tools/trim-video with a main input URL and maxCredits set, then poll GET /api/v1/jobs/{jobId} until the job completes and return the output URL

Social-ready clips from long video

A content team turns long recordings into short vertical clips. KinoPipe tools such as find-highlights, video-to-vertical, youtube-short, and tiktok-video handle detection and reformatting, so each clip is one tool call instead of a hand-built ffmpeg pipeline.

Run POST /api/v1/tools/find-highlights on a recording, then POST /api/v1/tools/video-to-vertical on the chosen segment

Multi-step edit jobs

When one tool is not enough, a job chains operations: trim the main input, overlay a watermark from a second input, add subtitles, and write the output in the chosen format. The first input must use the id main, each id must be unique, and a webhook can notify your system when the job is done.

Submit POST /api/v1/jobs with inputs main and logo, operations for trim and watermark, and a webhook URL, then read the result with GET /api/v1/jobs/{jobId}

Edit local files with direct upload

Files that are not already online go through a direct upload first. POST /api/v1/uploads takes the filename, contentType, and byteSize and returns a mediaUrl that any tool or job accepts as an input.

Create an upload with POST /api/v1/uploads for 'clip.mp4' with contentType 'video/mp4', upload the file, then pass the mediaUrl to POST /api/v1/tools/compress-video

Key Endpoints

5 endpoints — the kinopipe api edits video in the cloud: it trims, resizes, crops, subtitles, watermarks, merges, and converts media from a public url or a direct upload.

METHOD

PATH

DESCRIPTION

POST

/api/v1/tools/{slug}

Run a ready-made video editing tool

POST

/api/v1/jobs

Create a video editing job

GET

/api/v1/jobs/{jobId}

Read a video editing job

GET

/api/v1/jobs

List recent video editing jobs

POST

/api/v1/uploads

Create a direct media upload

POST

/api/v1/tools/{slug}

Run a ready-made video editing tool

POST

/api/v1/jobs

Create a video editing job

GET

/api/v1/jobs/{jobId}

Read a video editing job

GET

/api/v1/jobs

List recent video editing jobs

POST

/api/v1/uploads

Create a direct media upload

Why Jentic?

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

Setup

Wiring KinoPipe by hand means sending a kp_live_ bearer key, uploading local files before editing, and polling jobs or handling webhooks for results. Through Jentic you install once, import KinoPipe from the API Directory, store the key once, and your agent calls it.

Permission scoping

KinoPipe puts the tool slug in the URL path (/api/v1/tools/{slug}), so a rule can pin your agent to specific tools such as trim-video and the operations you pick. You choose the operations it may call, so multi-step jobs or other tools are not included unless you add them.

Credential isolation

Your KinoPipe 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 'trim a video' or 'add subtitles', and Jentic returns the matching KinoPipe operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using KinoPipe API through Jentic.

What authentication does the KinoPipe API use?

The KinoPipe API authenticates with a bearer token per its OpenAPI spec: a KinoPipe API key beginning with kp_live_, sent in the Authorization header on every operation. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time.

Should I use a tool or a job with the KinoPipe API?

Use POST /api/v1/tools/{slug} when one ready-made tool such as trim-video or add-subtitles-to-video does the whole task, with tool settings passed in options. Use POST /api/v1/jobs when you need to chain several operations, such as trim, crop, and watermark, across multiple named inputs in one run.

How do I stop a KinoPipe edit from costing more than expected?

Set maxCredits on the tool or job request. It is a hard ceiling checked before the work starts: the full amount is reserved before the job is queued and unused credits are refunded after success.

What are the rate limits for the KinoPipe API?

The OpenAPI spec does not specify rate limits. Check the KinoPipe documentation at https://kinopipe.com for current limits.

Is there a KinoPipe MCP server?

You don't need an MCP server to give your agent the KinoPipe API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the tool, job, and upload operations on demand without loading another server's tool definitions into its context.

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

Yes. For example, write a rule that allows only POST /api/v1/tools/compress-video and GET /api/v1/jobs/{jobId}, so the agent can compress videos and check their status but cannot run other tools or submit multi-step jobs. Every call it makes through your instance is logged.

How do I add subtitles to a video through Jentic?

Search Jentic for 'add subtitles to a video', load the KinoPipe tool operation, and call it with the add-subtitles-to-video slug and a main input URL. Read the result with GET /api/v1/jobs/{jobId}. To run it on your own infrastructure, install Jentic One from its GitHub repo.

KinoPipe API

AI ReadinessAI-Aware (B)65/100

See full scorecard

Official vendor OpenAPI document · agent-readyMediaVideo Processingbearer5 EndpointsREST

For Agents

Trim, resize, subtitle, watermark, merge, and convert video by running ready-made KinoPipe tools or multi-step editing jobs, with a credit ceiling per request.

Use for: Trim the first ten seconds off this video, I want to turn a landscape clip into a vertical video, Add subtitles to a video from a URL, Merge two clips into one MP4

Not supported: Does not host or stream video, generate video from text prompts, or manage a media library. Use for editing, converting, and analysing video files only.

The KinoPipe API edits video in the cloud: it trims, resizes, crops, subtitles, watermarks, merges, and converts media from a public URL or a direct upload. You either run a ready-made tool such as trim-video, compress-video, or add-subtitles-to-video, or submit a job that chains up to 12 operations across as many as 6 named inputs. Each request can carry a maxCredits ceiling that is checked before the work starts, and jobs report their status by id or through a webhook.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: BSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

65%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

25%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

70%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the KinoPipe API to your agent

Capabilities

Start building with KinoPipe API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

KinoPipe API

Jentic AI Readiness Score

KinoPipe API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness