Video hosting and streaming API for developers

One video hosting and streaming API for resumable upload, parallel transcoding, Widevine and FairPlay DRM, live streaming, CDN delivery and analytics. Your AI agent manages videos, live events and analytics through the MCP server, and your apps play them with cross-platform and native SDKs.

Connect your AI agent to Kinescope

Kinescope MCP Server, now in public beta, lets Cursor, Claude Desktop, Claude Code and other MCP clients work with your workspace in plain language. It uses your API token and your account’s access rights, and delete operations are turned off.

What your agent can do

  • Videos Search by title, description and tags, edit metadata and privacy, copy and move videos between projects.
  • Projects Create projects and organise videos into folders and playlists.
  • Analytics Views, engagement, viewer geography and custom reports.
  • Live streams Create and schedule events, configure restreaming, get recordings.
  • Subtitles and chapters Add subtitle files, read the subtitle text, update chapters with timestamps.
  • And more Posters, supplementary materials, upload requests, usage and billing statistics.
mcp.json Cursor Claude Code Qwen3
{
  "mcpServers": {
    "Kinescope MCP": {
      "type": "streamable-http",
      "url": "https://api.kinescope.io/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}
Claude Desktop terminal
npx -y @smithery/cli@latest mcp add kinescope/kinescope-mcp --client claude

Then ask

  • Show view statistics for all videos in the “Marketing” project for the last month
  • Create a live stream event “Product Launch Q4” for next week
  • Add chapters to the video: at 5:30 — “API Overview”, at 12:15 — “Pricing Discussion”

Deliver video features faster. We’ll take care of the infra behind you.

Kinescope runs its own video CDN — owned capacity, not resold — with points of presence across Latin America, the United States, Europe and the CIS. Live signal comes in over RTMP, RTMPS and SRT at ingest servers on four continents.

North America Brazil Europe CIS Asia
Live ingest servers: North America, Brazil, Europe, Asia and the CIS — server list
uptime SLA
99.98%
videos uploaded
100M+
minutes watched a day
5M
live streams run through the API
10,000+
  • RTMP
  • RTMPS
  • SRT
  • HLS
  • CMAF
  • LL-HLS
  • Widevine
  • FairPlay

From upload to protected playback in three steps

Three snippets from the docs: the upload and transcoding API takes the file, an iframe plays it, and your backend decides who watches. Swap in your API token and IDs.

  1. 1

    Upload

    Import a file by URL, as here, send it in a single request, or create an upload link for client apps. Large files go in chunks over TUS.

    cURL · import by URL
    curl -X POST https://uploader.kinescope.io/v2/video \
      -H "Authorization: Bearer $KINESCOPE_API_TOKEN" \
      -H "X-Parent-ID: $PARENT_ID" \
      -H "X-Video-Title: Lesson 1" \
      -H "X-Video-URL: https://example.com/lesson-1.mp4"
  2. 2

    Embed

    Kinescope encodes every upload into adaptive renditions up to 4K. Paste the iframe, or drive the player from JavaScript with the IFrame Player API.

    HTML · iframe
    <iframe src="https://kinescope.io/embed/VIDEO_ID"
      allow="autoplay; fullscreen; picture-in-picture; encrypted-media;"
      frameborder="0" allowfullscreen
      width="560" height="315"></iframe>
  3. 3

    Protect

    Turn on DRM and point Kinescope at your authorization backend. Before it issues a decryption key, it asks your server, and your 200 or 403 decides who watches.

    cURL · authorization backend
    curl -X PUT https://api.kinescope.io/v1/drm/auth \
      -H "Authorization: Bearer $KINESCOPE_API_TOKEN" \
      -H "Content-Type: application/json" \
      -d '{"url": "https://api.example.com/drm/authorize"}'
    
    # The viewer comes from the embed: ?drmauthtoken=USER_JWT
    # Answer 200 to allow the play or 403 to deny it.

Control the player from your code

A real Kinescope player. Each button calls an IFrame Player API method, the panel shows the code that ran, and the log shows the events the player sends back.

currentTime
0
paused
true
playbackRate
1
quality
—
volume
1
muted
false
Playback
Speed
Quality
Sound
Subtitles
player.js
import { load } from '@kinescope/player-iframe-api-loader';

const factory = await load();
const player = await factory.create('player', {
  url: 'https://kinescope.io/56Jg27MqvvttAwHcrCzEA4',
  size: { width: '100%', height: '100%' },
});

player.on(player.Events.TimeUpdate, ({ data }) => {
  console.log(data.currentTime, data.percent);
});
// Click a button on the left to run a call
Events Loads as you scroll here
  1. Events appear here once the player loads.

Every method and event is in the IFrame Player API docs.

Video streaming SDKs for web and mobile

Eight open-source SDKs for the same player, in the order developers download them. Each install line comes from the package README.

  • JavaScript IFrame Player API

    @kinescope/player-iframe-api-loader
    npm install @kinescope/player-iframe-api-loader
  • React video player component

    @kinescope/react-kinescope-player
    npm install @kinescope/react-kinescope-player
  • Flutter video player plugin

    flutter_kinescope_sdk
    flutter pub add flutter_kinescope_sdk
  • Vue video player component

    @kinescope/vue-kinescope-player
    npm install @kinescope/vue-kinescope-player
  • iOS Swift SDK

    KinescopeSDK
    pod 'KinescopeSDK' or Swift Package Manager
  • Android Kotlin SDK

    io.kinescope:kotlin-kinescope-player
    implementation 'io.kinescope:kotlin-kinescope-player:<version>' Maven Central
  • React Native video player component

    @kinescope/react-native-kinescope-video
    yarn add @kinescope/react-native-kinescope-video plus the peer dependencies listed in the README
  • Angular video player component

    @kinescope/angular-kinescope-player
    npm install @kinescope/angular-kinescope-player

What you build on the API

The endpoints, events and tools behind the player. Each card links to its part of the docs.

Video upload and transcoding API

Upload videos, organise projects and folders and pull analytics over JSON at api.kinescope.io/v1 with an API token. Each upload is encoded into adaptive renditions up to 4K, so there is no separate video encoding API to wire up.

Live streaming API

A live video streaming API: create and schedule events and restreams, push RTMP or SRT from OBS or any encoder and keep an automatic recording. The web player and the iOS and Android SDKs play the stream live.

Playback security

Widevine and FairPlay DRM on paid plans, domain restrictions, signed links with an expiry and your own backend approving each play.

Webhooks

Seven events posted as JSON: media.update.status for processing and six for the live-stream lifecycle.

Analytics API

Playback totals, a timeline and top lists by country, city, device, OS and browser from /v1/analytics/overview, for the workspace or one video, plus CDN, encoding and storage usage from /v1/billing/usage.

AI subtitles and chapters

Generate subtitles in the video’s language with one API call, and AI chapters and a short description from the dashboard. Through the MCP server, an agent can read the subtitle text and write chapters back.

Video API pricing

No separate developer plan: the full API comes with paid plans from €10 a month. Delivery, storage and processing are pay-as-you-go, and rates go down as your volume grows.

CDN delivery

Traffic (GB)

Price per GB (€)

0–1,000

0.03

1,000–6,000

0.02

6,000–21,000

0.015

21,000–51,000

0.01

> 51,000

Custom

Storage

Volume (GB)

Price per GB (€)

0–1,000

0.03

1,000–21,000

0.02

> 21,000

Custom

Video processing

Video duration (min)

Price per min (€)

0–60,000

0.01

> 60,000

Custom

See all prices and the calculator →

How Kinescope compares with other video APIs

Kinescope vs Mux

Widevine and FairPlay included, where Mux charges $100 a month plus $0.003 per license, and a video library your editors can use. Where Mux is stronger: PlayReady, per-minute pricing with free basic encoding, and Mux Data for playback analytics. Full comparison

Kinescope vs Cloudflare Stream

Widevine and FairPlay DRM and adaptive streams up to 4K; Stream delivers up to 1080p without DRM. Where Cloudflare Stream is stronger: WebRTC live under 500 ms, restreaming to up to 50 destinations and a Cloudflare Workers stack. Full comparison

Kinescope vs api.video

Widevine and FairPlay and domain restrictions included, where api.video lists private tokens and charges $20 a month for domain rules. Where api.video is stronger: Live at about 3 seconds, simulcasting and one per-minute price at any quality. Full comparison

Kinescope vs Cloudinary

Video delivery from €0.03/GB, Widevine and FairPlay, and EU storage by default; Cloudinary bills video in shared credits from $99 a month. Where Cloudinary is stronger: One platform for images and video, digital asset management and shoppable video. Full comparison

Kinescope vs AWS MediaConvert

Transcoding, CDN, player and DRM licences behind one API, where AWS needs S3, MediaConvert, CloudFront and a DRM vendor. Where AWS MediaConvert is stronger: Control over every encoding setting, HEVC up to 8K, any AWS region and CloudFront flat-rate delivery. Full comparison

Kinescope vs Bunny Stream

A ready player, dashboard and DRM in one price, instead of a CDN API with DRM as a paid add-on. Where Bunny Stream is stronger: Raw low-cost bandwidth at very high volume, if your team builds the player and security layer. Full comparison

FAQ

Can’t find the answer you need? Check out our Developer docs.

A video hosting API is the programmable layer of a video platform: your product uploads files, gets them transcoded into adaptive renditions, stores and delivers them over a CDN, protects playback and reads analytics through HTTP calls instead of a dashboard. Kinescope’s covers all of that with one API token, plus open-source player SDKs and webhooks. A longer walkthrough with code is in the video hosting API guide.

Most video APIs bill either per minute (encoding, storage and delivery minutes) or per GB. Kinescope bills per GB with no separate developer plan: the full API comes with paid plans from €10 a month, delivery starts at €0.03/GB and goes down with volume, storage starts at €0.03/GB and processing is €0.01 per minute, charged once. See the API pricing on this page.

Yes. Kinescope's REST API covers upload (a single request, upload links, import by URL and TUS for large files), automatic transcoding into adaptive renditions up to 4K, live streams over RTMP, playback protection and analytics. Requests go to api.kinescope.io/v1 with an API token — see the API reference.

Yes. Create an API token in the dashboard under Settings → API tokens, then send REST requests with JSON to api.kinescope.io/v1, passing the token as a Bearer header. The quick start on this page goes from upload to protected playback in three steps. On the front end, open-source SDKs cover iOS, Android, Flutter, React, React Native, Vue and Angular, and the IFrame Player API works on any web page; an AI agent can do the same work through the MCP server. A free plan lets you try it first.

Get an API token and ship your first video.

Free to start, then from €10/month for the full API. No credit card required.