canonical: https://jentic.com/apis/visibot.app/visibot

# Visibot App Visibot API

AI-powered video editing API for creating and editing videos with captions, emojis, and more. The API exposes 8 endpoints secured with bearer authentication.

## For AI agents

Programmatically get current user, get usage stats. Covers 8 operations with bearer authentication.

## Scope

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

## Capabilities

- Get current user
- Register new user
- Create a video
- Edit a video
- WarriorPlus IPN

## Use cases

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

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'get current user', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/me` | Get current user |
| GET | `/api/usage` | Get usage stats |
| POST | `/api/user/register` | Register new user |
| POST | `/api/video/create` | Create a video |
| POST | `/api/video/edit` | Edit a video |
| GET | `/api/video/get` | Get video status |
| POST | `/api/warriorplus/ipn` | WarriorPlus IPN |
| POST | `/api/webhooks/manychat/telegram-subscriber` | ManyChat Telegram Subscriber |

## Key resources

- **Me** — Operations for me
- **Usage** — Operations for usage
- **User** — Operations for user
- **Video** — Operations for video
- **Warriorplus** — Operations for warriorplus

## AI readiness

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.

- **Score:** 66 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 87 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 46 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/visibot.app/visibot/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Cloudinary** — Alternative media API
- **Mux** — Alternative media API

## FAQ

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