Castmagic API
70
AI ReadinessAI-Aware (A-)70/100
Agent-ready OpenAPI document · curated by JenticMediaAudio Processingbearer5 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Submit audio or video files to Castmagic for transcription and content generation, list workspaces, and manage webhook subscriptions for processing events.
Use for: I need to send a podcast episode to Castmagic for transcription, List all my Castmagic Spaces, Create a Castmagic media object from a Dropbox audio link, Subscribe a webhook to be notified when Castmagic finishes processing
Not supported: Does not handle transcript retrieval, asset editing, or billing - use for submitting media objects and managing webhook subscriptions on Castmagic only.
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.
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.
1
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%2Fcastmagic.io%2Fcastmagic" | sh2
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%2Fcastmagic.io%2Fcastmagic" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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
Subscribe a webhook URL to receive notifications when Castmagic processing completes
Unsubscribe a previously registered Castmagic webhook
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
Jentic AI Readiness Score
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.
C
Castmagic API
- AI-Aware (A-)70/100
100
Foundational Compliance63
Developer Experience & Jentic Compatibility52
AI-Readiness & Agent Experience94
Agent Usability60
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
52
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C-Signals: 4
59%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Castmagic API by hand means sending your key as a bearer token on every call and working against the Zapier-style routes on the app.castmagic.io host yourself. Through Jentic you install once, import the Castmagic API from the API Directory, store the key once, and your agent calls it.
Permission scoping
Castmagic takes the media object and hook details in the request body, not the URL path, so you scope by operation: limit the agent to the ones it needs, such as validating the key, listing spaces, and submitting an object, and leave webhook subscribe and unsubscribe out of the allowed set until you want them.
Credential isolation
Your Castmagic API key is stored once, encrypted, by your own Jentic One instance and injected as the bearer token at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'submit an audio file to Castmagic', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
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 with Jentic One, the self-hosted execution layer.
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 your Jentic One instance 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.
Can I limit what my agent is allowed to do with the Castmagic API?
Yes. Because you run Jentic One yourself, your own rules decide which Castmagic operations and credentials the agent may use. Castmagic scopes by operation rather than URL path, so you can allow only what the agent needs, such as validating the key, listing Spaces with GET /spaces, and submitting a media object with POST /objects. You can leave the webhook operations POST /hooks/subscribe and DELETE /hooks/unsubscribe out of the allowed set until you decide the agent should manage subscriptions.
GET STARTED