Install Jentic One Beta

Connect the ZapCap API to your agent

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

Upload a video file

Create a captioning task

Integrate ZapCap API into automated workflows

Query and filter ZapCap API records by parameters

Monitor ZapCap API operational status and events

GET STARTED

Start building with ZapCap API

Explore with Jentic One

View OpenAPI Document

Automated Tasks Management

Automate tasks operations by combining multiple ZapCap API endpoints. Agents can upload video by url and then create a captioning task in a single workflow.

Call POST /videos/url to upload video by url, then verify the result

AI Agent Integration via Jentic

AI agents discover and call ZapCap 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 'upload a video file', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

3 endpoints — zapcap api for automated video captioning and subtitle generation.

METHOD

PATH

DESCRIPTION

POST

/videos

Upload a video file

POST

/videos/url

Upload video by URL

POST

/videos/{videoId}/task

Create a captioning task

POST

/videos

Upload a video file

POST

/videos/url

Upload video by URL

POST

/videos/{videoId}/task

Create a captioning task

Why Jentic?

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

Setup

Wiring ZapCap by hand means setting its x-api-key header on every request, uploading video by file or by URL, and polling the task endpoint yourself. Through Jentic you install once, import ZapCap from the API Directory, store the key once, and your agent calls it.

Permission scoping

ZapCap puts the video id in the URL path (/videos/{videoId}/task), so a rule can pin your agent to work on one uploaded video and start tasks for it. You choose the operations it may call, so it can create tasks for that video without being able to touch others.

Credential isolation

Your ZapCap 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 for captioning' or 'start a video task', and Jentic returns the matching ZapCap operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using ZapCap API through Jentic.

What authentication does the ZapCap API use?

The ZapCap API uses an API key passed in the `x-api-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 upload a video file with the ZapCap API?

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

What are the rate limits for the ZapCap 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 upload a video file through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'upload a video file'. Jentic returns the matching ZapCap API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the ZapCap API have?

The ZapCap API exposes 3 endpoints covering tasks, videos operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which ZapCap operations and credentials your agent may use. Since ZapCap carries the video id in the URL path (/videos/{videoId}/task), you can write a rule that pins the agent to one uploaded video and lets it start captioning tasks only for that video. You also choose whether it may call the upload operations (POST /videos and POST /videos/url) at all, so it cannot touch videos you did not authorize.

ZapCap API

AI ReadinessAI-Aware (B)65/100

See full scorecard

Official vendor OpenAPI document · agent-readyMediaVideo ProcessingapiKey3 EndpointsREST

For Agents

Programmatically upload a video file, upload video by url. Covers 3 operations with apiKey authentication.

Use for: I need to upload a video file, I want to upload video by url, Search for a captioning task, List all records from ZapCap API

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

ZapCap API for automated video captioning and subtitle generation. The API exposes 3 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

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

100%

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: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

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

28%

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: C-Signals: 1

50%

Authentication Strength

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

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the ZapCap API to your agent

Capabilities

Start building with ZapCap API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

ZapCap API

Jentic AI Readiness Score

ZapCap 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