Install Jentic One Beta

Connect the Dacast API to your agent

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

Create a live stream and configure ingest settings via POST /live

Upload a video on demand asset and store its metadata via POST /vod

Update VOD or live stream details such as title, description, and access settings

Create a 24/7 channel for scheduled looping or simulated-live programming

List existing live streams, VOD assets, or channels for a portfolio audit

GET STARTED

Start building with Dacast API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Dacast API for, with concrete tasks.

★ Live Event Provisioning

Production teams running a series of live events use POST /live to provision a fresh stream for each event, capturing the stream key and ingest URL for the encoder. The agent pre-creates streams the night before, attaches the right access settings, and writes the credentials into the production runbook so the broadcast team can connect directly.

POST to /live with title 'Q3 Earnings Call' and the desired access settings, then return the ingest URL and stream key.

VOD Catalogue Management

Content teams managing a library of recorded videos use POST /vod to add new assets and PUT /vod/{contentId} to keep titles, descriptions, and pricing settings consistent. Periodically the agent calls GET /vod to audit the catalogue, identify orphaned or expired assets, and call DELETE /vod/{contentId} to remove them.

Call GET /vod, filter for assets last updated more than 18 months ago, and DELETE /vod/{contentId} for each match.

24/7 Channel Programming

Broadcasters running always-on channels for highlights, training content, or marketing loops use POST /channel to create the channel and PUT to update its programming. The API surfaces the playlist and access settings so an agent can rotate content through a virtual channel without manual editing in the dashboard.

POST to /channel with title 'Customer Stories Loop' and a playlist of contentIds, then return the new channel ID.

Agent-Driven Content Cleanup

An AI agent running a weekly housekeeping job lists every live stream and VOD asset, cross-references them with an internal rights database, and removes content that has aged out. The combination of GET /live, GET /vod, and the matching DELETE endpoints lets the agent enforce retention policy without a human reviewing every asset.

For each contentId in the rights database with status='expired', call DELETE /vod/{contentId} or DELETE /live/{contentId} and log the outcome.

Key Endpoints

14 endpoints — dacast is a video streaming platform aimed at broadcasters, sports rights holders, and businesses that need monetised live and on-demand video.

METHOD

PATH

DESCRIPTION

POST

/live

Create a live stream

GET

/live

List live streams

POST

/vod

Create VOD content

GET

/vod

List VOD content

PUT

/vod/{contentId}

Update VOD content

DELETE

/vod/{contentId}

Delete VOD content

POST

/channel

Create a channel

GET

/channel

List channels

POST

/live

Create a live stream

GET

/live

List live streams

POST

/vod

Create VOD content

GET

/vod

List VOD content

PUT

/vod/{contentId}

Update VOD content

DELETE

/vod/{contentId}

Delete VOD content

POST

/channel

Create a channel

GET

/channel

List channels

Why Jentic?

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

Setup

Wiring Dacast by hand means learning its X-API-Key header auth against developer.dacast.com/v2 and handling upload, listing, and retry plumbing for live streams and VOD yourself. Through Jentic you install once, import the Dacast API from the API Directory, store the key once, and your agent calls it.

Permission scoping

Dacast puts the content id in the URL path (/vod/{contentId}), so a rule can pin your agent to one VOD asset for reads and updates. You choose the operations it may call, so destructive ones like deleting a VOD asset are not included unless you add them.

Credential isolation

Your Dacast X-API-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 'create a Dacast live stream' or 'upload a video to Dacast', and Jentic returns the matching Dacast operation with its input schema so the agent calls the right endpoint without browsing the developer.dacast.com docs.

FAQs

Specific to using Dacast API through Jentic.

What authentication does the Dacast API use?

The Dacast API uses an API key passed in the X-API-Key header. You generate the key in the Dacast account settings and include it on every request to developer.dacast.com/v2. Through Jentic the key is stored encrypted in the vault and the agent receives a scoped runtime credential, so the raw key never enters the model context.

Can I create a live stream with the Dacast API?

Yes. POST /live creates a new live stream and returns the ingest URL and stream key needed by the encoder. You can then GET /live/{contentId} to fetch the stream's playback details and PUT /live/{contentId} to update settings such as title or access controls.

What are the rate limits for the Dacast API?

The OpenAPI spec does not document explicit rate limits. Dacast's developer guidance recommends keeping API traffic below a few requests per second per key for management workflows; bulk operations such as catalogue audits should be paced rather than fired in parallel.

How do I upload a VOD asset through Jentic?

Install pip install jentic and run an agent with the search query 'upload a video to Dacast'. Jentic returns the POST /vod operation with its input schema; the agent provides the asset metadata and follows up with the upload step described in the spec.

Can I delete expired VOD content through the API?

Yes. DELETE /vod/{contentId} removes a VOD asset by ID. A typical pattern is to call GET /vod, filter for assets that have aged out, and loop the matching contentIds through DELETE /vod/{contentId} as part of a housekeeping job.

Does the Dacast API expose viewer analytics?

The 14 endpoints in this spec cover content management for live streams, VOD, and channels. Detailed viewer analytics are surfaced in the Dacast dashboard rather than through these REST endpoints; use the platform's analytics view or contact Dacast for analytics data export options.

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

Yes. Because Jentic One is self-hosted, your own rules decide which Dacast operations and credentials the agent may use. Since Dacast puts the content id in the URL path, such as /vod/{contentId}, you can pin the agent to a single VOD asset for reads and updates. You also pick the exact operations it may call, so destructive ones like DELETE /vod/{contentId} or DELETE /live/{contentId} are excluded unless you add them.

Dacast API

Name: Dacast API
Brand: Dacast API
Availability: InStock

Official vendor OpenAPI document · agent-readyMediaVideo ProcessingapiKey14 EndpointsREST

For Agents

Manage Dacast live streams, video on demand assets, and channels for end-to-end video publishing workflows.

Use for: I need to create a new Dacast live stream for a webinar, Upload a recorded video as a Dacast VOD asset, Update the title of a VOD asset after a typo, List all live streams scheduled for this week

Not supported: Does not handle player embedding, viewer analytics, or paywall configuration - use for live stream, VOD, and channel content management only.

Dacast is a video streaming platform aimed at broadcasters, sports rights holders, and businesses that need monetised live and on-demand video. The v2 API exposes 14 endpoints covering live streams, video on demand assets, and channels, all behind an X-API-Key header. It supports the workflows needed to schedule a live event, upload a VOD asset, manage scheduled channels, and clean up content after broadcast.

Jentic One on Github View OpenAPI Document

Connect the Dacast API to your agent

Capabilities

Start building with Dacast API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Dacast API