Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Visibot 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%2Fvisibot.app%2Fvisibot" | shStep 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%2Fvisibot.app%2Fvisibot" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Visibot API.
Get current user
Register new user
Create a video
Edit a video
WarriorPlus IPN
Patterns agents use Visibot API for, with concrete tasks.
GET STARTED
★ Media and Content Operations
Use the Visibot API to perform media operations programmatically. The API provides 8 endpoints covering core functionality including get current user, get usage stats, register new user.
Call GET /api/me to get current user
Automated Me Management
Automate me operations by combining multiple Visibot API endpoints. Agents can get usage stats and then register new user in a single workflow.
Call GET /api/usage to get usage stats, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Visibot 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 bearer tokens manually.
Search Jentic for 'get current user', load the operation schema, and execute with Jentic-managed credentials
8 endpoints — ai-powered video editing api for creating and editing videos with captions, emojis, and more.
METHOD
PATH
DESCRIPTION
/api/me
Get current user
/api/usage
Get usage stats
/api/user/register
Register new user
/api/video/create
Create a video
/api/video/edit
Edit a video
/api/video/get
Get video status
/api/warriorplus/ipn
WarriorPlus IPN
/api/webhooks/manychat/telegram-subscriber
ManyChat Telegram Subscriber
/api/me
Get current user
/api/usage
Get usage stats
/api/user/register
Register new user
/api/video/create
Create a video
/api/video/edit
Edit a video
/api/video/get
Get video status
/api/warriorplus/ipn
WarriorPlus IPN
/api/webhooks/manychat/telegram-subscriber
ManyChat Telegram Subscriber
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Visibot API by hand means passing its bearer token in the Authorization header and driving its video create, edit, and retrieval calls yourself. Through Jentic you install once, import the Visibot API from the API Directory, store the token once, and your agent calls it.
Permission scoping
Visibot carries its video targets in the request body rather than the URL path, so scope the agent to the operations it needs, such as creating or retrieving a video. You choose that set, so a state-changing operation like editing a video is not included unless you add it.
Credential isolation
Your Visibot token 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 'create a video' or 'check my usage', and Jentic returns the matching Visibot operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Visibot API through Jentic.
What authentication does the Visibot API use?
The Visibot API uses a Bearer token in the Authorization 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 get current user with the Visibot API?
Yes. Use the GET /api/me endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Visibot 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 get current user through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get current user'. Jentic returns the matching Visibot API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Visibot API have?
The Visibot API exposes 8 endpoints covering me, usage, user operations.
Can I limit what my agent is allowed to do with the Visibot API?
Yes. Because you self-host Jentic One, your own rules decide which Visibot operations and credentials the agent can use, so you can grant only what a task needs, such as creating a video or checking your usage stats. Visibot carries its video targets in the request body rather than the URL path, so you scope access at the operation level rather than by path. A state-changing operation like editing a video stays out of the agent's reach unless you explicitly add it to the allowed set.
For Agents
Programmatically get current user, get usage stats. Covers 8 operations with bearer authentication.
Use for: I need to current user, I want to usage stats, Search for register new user, Find all a video
Not supported: Does not handle payments, communications, or crm - use for media and content only.
AI-powered video editing API for creating and editing videos with captions, emojis, and more. The API exposes 8 endpoints secured with bearer authentication.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>