Castmagic API

Name: Castmagic API
Brand: Castmagic API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaAudio Processingbearer5 EndpointsREST

For Agents

Submit audio or video files to Castmagic for transcription and content generation, list workspaces, and manage webhook subscriptions for processing events.

Install Jentic One Beta

Connect the Castmagic API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Castmagic 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Castmagic API.

Validate that a Castmagic API key is active before triggering downstream calls

List the Spaces available on a Castmagic account for routing new media

Create a Castmagic media object from an audio or video URL to start processing

GET STARTED

Start building with Castmagic API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Castmagic API, keeping it validated and agent-ready. Castmagic is a content processing platform that ingests audio and video files and produces transcripts, show notes, social posts, and other derived assets organised into workspaces called Spaces. The Zapier-style API surface lets you list available Spaces, create a new media object from a source URL, subscribe and unsubscribe webhooks for processing events, and validate that an API key is active. It is intended for piping podcast and video content into Castmagic from external recording, scheduling, or storage tools.

Use Cases

Patterns agents use Castmagic API for, with concrete tasks.

★ Automated podcast post-production

Once a podcast episode is recorded and uploaded to cloud storage, an automation can POST the file URL to Castmagic /objects to start transcription, show note generation, and clip suggestions. The webhook subscription lets the automation know when the assets are ready to be pulled into a publishing tool.

POST to /objects with the audio file URL and the target space_id, then POST /hooks/subscribe with the callback URL that should receive the completion event.

Video content repurposing pipeline

A creator uploading a long-form video can have it forwarded to Castmagic as a media object so Castmagic produces transcript, summary, and social caption assets. The same /objects call can route output into a per-client Space, which keeps assets separated for agency workflows.

POST /objects with the video URL and the client-specific space_id obtained from GET /spaces.

Webhook-driven content publishing

Editorial systems can register a webhook with POST /hooks/subscribe so Castmagic notifies them as soon as transcripts and derivative assets are ready, rather than polling. When a project ends, DELETE /hooks/unsubscribe removes the subscription cleanly.

POST /hooks/subscribe with target_url=https://example.com/castmagic-callback and event='object.completed'.

AI agent media workflow via Jentic

An AI content agent can collect new audio recordings, push them to Castmagic, and pull back the structured assets without the developer hand-coding the Zapier-style endpoint contract. Jentic stores the bearer API key in the vault and injects it at execution time.

Search Jentic for 'submit an audio file to Castmagic', load POST /objects, and execute it with the user's audio URL and chosen Space.

Key Endpoints

5 endpoints — jentic publishes the only available openapi specification for castmagic api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/validate

Validate the supplied API key

GET

/spaces

List available Spaces on the account

POST

/objects

Create a media object from an audio or video URL

POST

/hooks/subscribe

Subscribe a webhook to processing events

DELETE

/hooks/unsubscribe

Remove a webhook subscription

GET

/validate

Validate the supplied API key

GET

/spaces

List available Spaces on the account

POST

/objects

Create a media object from an audio or video URL

POST

/hooks/subscribe

Subscribe a webhook to processing events

DELETE

/hooks/unsubscribe

Remove a webhook subscription

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Castmagic bearer API keys are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access at execution time and the raw token never enters prompts, logs, or response payloads.

Intent-based discovery

Agents search by intent (e.g., 'submit an audio file to Castmagic') and Jentic returns the matching POST /objects operation along with its input schema, so the agent does not need to learn the Zapier endpoint contract.

Time to first call

Direct Castmagic integration including webhook lifecycle handling: about half a day. Through Jentic: under 30 minutes — search, load, execute.

FAQs

Specific to using Castmagic API through Jentic.

Why is there no official OpenAPI spec for Castmagic API?

Castmagic publishes a Zapier-targeted API but no machine-readable OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Castmagic API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Castmagic API use?

The Castmagic API uses HTTP bearer token authentication. You generate the API key in the Castmagic dashboard and pass it as Authorization: Bearer in every request. Through Jentic the key is held encrypted in the MAXsystem vault and never exposed to the agent.

How do I submit an audio file to Castmagic for processing?

POST a JSON body to /objects containing the source audio or video URL and the target space_id. Castmagic ingests the file asynchronously, and you can register a webhook with POST /hooks/subscribe to be notified when transcription and derivative assets are ready.

What are the rate limits for the Castmagic API?

Castmagic does not document explicit numeric rate limits in this OpenAPI spec; the Zapier-style endpoints are designed for moderate trigger volume. Avoid tight polling against /spaces or /validate, and prefer webhook subscriptions over polling for completion events.

How do I create a Castmagic media object through Jentic?

Run pip install jentic, search Jentic with the query 'submit an audio file to Castmagic', load the POST /objects schema, and execute it with the file URL and a space_id obtained from GET /spaces. Jentic handles the bearer key automatically.

Can I retrieve the generated transcript directly from this API?

No. The current spec covers media submission and webhook management but not transcript retrieval, which happens through the Castmagic web UI or via the webhook payload that fires when processing completes. Use POST /hooks/subscribe to receive the asset URLs.

Castmagic API

Connect the Castmagic API to your agent

Capabilities

Start building with Castmagic API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs