Developer platform / API v1

Video is hard.
Your API shouldn’t be.

Upload directly from your app, or import a source from connected cloud storage (AWS S3, Google Cloud, Azure Blob, Quat). VEXOR processes and protects the video, then delivers adaptive playback with webhooks and short-lived tokens.

01 / THE INTEGRATION

Four steps between
file and first frame.

Choose direct upload or import from storage you already own. VEXOR runs the video pipeline in the background and reports when each asset changes state.

01 / 04

Ingest

Upload with resumable Tus, or import a file from connected cloud storage (S3, GCS, Azure, Quat).

UPLOAD · IMPORT
02 / 04

Process

A worker probes the source, transcodes renditions, and packages encrypted HLS.

ASYNC · FFmpeg
03 / 04

Listen

Receive signed lifecycle events and update your app when processing finishes.

video.asset.ready
04 / 04

Play

Request a short-lived token from your server and pass the playback URL to a player.

POST /v1/tokens

02 / SDKs & PLUGINS

Meet Vexor
where you build.

Automate video pipelines with our official GitHub Action, use the Node.js / TypeScript or Python SDK for backend services, and embed with React or WordPress. Keep API keys on your server; send viewers only short-lived playback tokens.

01 / INTEGRATIONNode.js

Node.js / TS SDK

Server uploads, S3 imports, playback tokens, and signed webhook verification.

npm package
$ npm i @vexor-video/sdk
const vexor = new Vexor();
Read integration guide
02 / INTEGRATIONPython

Python SDK

Server uploads, asset status, playback token authorization, and webhook verification.

pypi package
$ pip install vexor-video-sdk
client = Vexor()
Read integration guide
03 / INTEGRATIONReact

React Player

Adaptive HLS playback, accessible controls, dynamic watermark, and token auto-refresh.

react component
$ npm i @vexor-video/player
<VexorPlayer src={url} />
Read integration guide
04 / INTEGRATIONWordPress

WordPress Plugin

Connect your Vexor account in wp-admin, pick an asset, and embed it in posts or lessons.

wp shortcode
<!-- WordPress Lesson -->
[vexor_player id="..."]
Read integration guide
05 / INTEGRATIONGitHub Action

GitHub Action

Automate video transcoding, cloud storage imports, and PR player previews in CI/CD.

ci/cd action
name: Transcode Video
uses: vexor/action@v1
Read integration guide

03 / AI AGENT ACCESS

Onboard your
AI coding agent.

Give your AI coding assistant read-only access to your VEXOR assets, processing status, and wallet balance through the Model Context Protocol (MCP).

MCP Server

VEXOR provides a hosted remote MCP server that your AI coding agent (Cursor, Claude, Codex, etc.) can connect to using a dedicated read-only API key.

Read-only access. Agents can list assets, check processing status, and view wallet balance—never upload, delete, or modify.

Secure by design. Uses dedicated read-only API keys, never your full-access credentials.

Rate limited. 60 requests/minute + 10 burst capacity per account to prevent abuse.

Full observability. Client IP logging, metrics tracking, and audit trail for every request.

Available Tools

Your agent can access these read-only tools through the MCP protocol:

list_assets

List video assets with pagination, processing states, and metadata

get_asset

Get detailed status and progress for a specific asset

get_usage

Check wallet balance, storage usage, and projected monthly costs

Privacy guaranteed. Sensitive fields (storage paths, credentials) are never exposed to agents.

Create keys in dashboard. Go to Settings → API Keys and create a read-only scoped key for MCP.

MCP Server Endpoint

https://vexor-video.vercel.app/api/mcp

Stateless Streamable HTTP transport · MCP Protocol 2025-11-25

View setup guide

04 / QUICKSTART

Authorize playback
from your server.

When an asset is ready, call the token endpoint from your trusted backend. It returns an asset-scoped playback token and manifest URL for your viewer.

Keep secrets server-side. Never ship your Vexor API key in browser or mobile app code.

Short-lived by design. Playback tokens expire after five minutes and are bound to one asset.

Ready assets only. Token requests are accepted after the asset reaches the ready state.

Get your API key
Issue a playback token (cURL)
bash
# Run this from your server after the asset is ready.
curl -X POST "$VEXOR_API_URL/v1/tokens" \
  -H "Authorization: Bearer $VEXOR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"asset_id":"YOUR_ASSET_ID","viewer_id":"viewer_123","session_id":"session_456"}'
Never expose VEXOR_API_KEY in browser or mobile code.Playback tokens expire after 5 minutes.

05 / API SURFACE

Small surface.
Complete pipeline.

Use standard HTTP and tus. Your application owns the customer experience; Vexor handles video processing and delivery controls.

01
POST/v1/uploads/direct

Start a direct multipart upload

Opt-in; returns a private upload session for parallel, resumable browser-to-storage parts.

02
POST/uploads

Create a resumable upload

Tus 1.0 upload creation and byte-range resume.

03
GET/v1/assets/{id}

Track processing

Read asset state, progress, and generated metadata.

04
POST/v1/tokens

Authorize playback

Issue a short-lived, asset-scoped playback token.

05
POST/v1/webhooks

Receive lifecycle events

Configure signed delivery for upload and ready events.

Track your usage. Processing and storage charges appear in your account ledger.

Billing details

06 / BUILD WITH VEXOR

Your next feature
starts with video.

Create an account to get your API credentials, configure a webhook, and ship your first video workflow.