CreativeClaw MCP API
69
AI ReadinessAI-Aware (B+)69/100
Official vendor OpenAPI document · agent-readyMediaVideo Processingoauth2, bearer5 EndpointsREST
For Agents
Generate video, 3D models, and audio through a remote MCP server by calling its streamable HTTP endpoint, then poll the returned job until it finishes. Authenticated with OAuth 2.1 or a bearer JWT; discovery and health endpoints are public.
Use for: Generate a video from a text prompt, Render an HTML page into a video, Create a 3D model from an input, Transcribe an audio file
Not supported: Does not handle media hosting, image editing, or payment processing. Use for generating video, 3D models, and audio through its MCP endpoint only.
The CreativeClaw API generates video, 3D models, and audio for AI agents through a remote tool server that speaks JSON-RPC over a single streamable HTTP endpoint rather than a resource-oriented REST surface. Agents authenticate with OAuth 2.1, list the available tools, and invoke them. Generation tools such as video creation, HTML-to-video rendering, 3D model generation, transcription, audio isolation, and media merging run asynchronously and return a job to poll until it completes or fails.
Install Jentic One Beta
Connect the CreativeClaw MCP API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CreativeClaw MCP 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%2Fcreativeclaw.co%2Fcreativeclaw" | 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%2Fcreativeclaw.co%2Fcreativeclaw" | 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 CreativeClaw MCP API.
List the live generation tools and their schemas over the MCP endpoint
Generate a video from a prompt and render an HTML page to a video
Generate a 3D model from an input
Transcribe audio and isolate an audio track
Merge multiple media assets into one output
Poll an asynchronous generation job until it completes or fails
Use Cases
Patterns agents use CreativeClaw MCP API for, with concrete tasks.
★ Asynchronous Media Generation
An agent lists the CreativeClaw tools over the MCP endpoint, invokes video, 3D, or audio generation with its inputs, and receives a job it polls until the result is ready. Because generation runs asynchronously, the agent calls the job-check tool rather than blocking, then uses the finished asset once the status reports completion.
Call POST /mcp with a tools/call request to generate a video, then poll the returned job with the job-check tool until it completes
Audio Processing for Agents
An agent transcribes an audio file, isolates a track, or merges clips by invoking the matching CreativeClaw tool over the MCP endpoint. The tools accept the source media and return a job, so the agent can chain transcription and audio isolation into a larger content pipeline.
Call POST /mcp with a tools/call request to transcribe an audio file, then poll the job until the transcript is ready
AI Agent Integration via Jentic
An AI agent reaches CreativeClaw through Jentic without managing the OAuth flow itself. It searches by intent, receives the matching operation and its input schema, and executes the call with the credential injected at run time. This lets an agent request a generated asset as one step in a task without handling the MCP client setup in code.
Search Jentic for 'generate a video', load the CreativeClaw MCP operation schema, and execute it with Jentic-managed credentials
Key Endpoints
5 endpoints — the creativeclaw api generates video, 3d models, and audio for ai agents through a remote tool server that speaks json-rpc over a single streamable http endpoint rather than a resource-oriented rest surface.
METHOD
PATH
DESCRIPTION
POST
/mcp
MCP Streamable HTTP endpoint for tool listing and calls
GET
/health
MCP host health
GET
/.well-known/oauth-authorization-server
OAuth authorization server metadata
GET
/.well-known/openid-configuration
OpenID provider configuration
POST
/mcp
MCP Streamable HTTP endpoint for tool listing and calls
GET
/health
MCP host health
GET
/.well-known/oauth-authorization-server
OAuth authorization server metadata
GET
/.well-known/openid-configuration
OpenID provider configuration
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
CreativeClaw MCP API
- AI-Aware (B+)69/100
100
Foundational Compliance60
Developer Experience & Jentic Compatibility48
AI-Readiness & Agent Experience94
Agent Usability83
Security75
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
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.
60
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: C+Signals: 4
5%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
35%
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.
48
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D+Signals: 4
28%
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.
64%
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.
83
Security
Trust, risk posture, and security compliance.
Grade: ASignals: 1
82%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
75
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A-Signals: 1
75%
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 CreativeClaw by hand means running its OAuth 2.1 flow with PKCE, speaking JSON-RPC over its streamable HTTP endpoint, and polling each asynchronous generation job yourself. Through Jentic you install once, import CreativeClaw from the API Directory, store the credential once, and your agent calls it.
Permission scoping
CreativeClaw routes every tool through a single tool-call operation, with the tool and its inputs carried in the request body, so a rule bounds whether your agent may reach that operation rather than which tool it invokes. You choose to allow or withhold that operation, and the public health and discovery endpoints need no credential at all.
Credential isolation
Your CreativeClaw credential 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 'generate a video' or 'transcribe audio', and Jentic returns the matching CreativeClaw 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 CreativeClaw MCP API through Jentic.
What authentication does the CreativeClaw MCP API use?
The MCP endpoint authenticates with OAuth 2.1 using the authorization code flow with PKCE, or a bearer JWT obtained from the token endpoint, per its OpenAPI spec. The health and OAuth discovery endpoints are public. Through Jentic the credential is stored encrypted by your own Jentic One instance and injected at execution time, so it never reaches the agent.
Can I generate a video with the CreativeClaw MCP API?
Yes. You call the video-generation tool over the MCP endpoint, which returns a job that runs asynchronously, then poll the job-check tool until its status reports completion. The same pattern covers HTML-to-video rendering, 3D model generation, transcription, audio isolation, and media merging.
What are the rate limits for the CreativeClaw MCP API?
The OpenAPI spec does not publish specific rate-limit numbers; check https://creativeclaw.co/developers for current details. Because generation runs as an asynchronous job, an agent invokes a tool and then polls its job rather than issuing a burst of requests.
Is there a CreativeClaw MCP server?
Yes, CreativeClaw is itself a remote MCP server reached over OAuth 2.1. You can also connect it directly through Jentic: your credential is injected at call time by your self-hosted instance instead of living in an MCP client config, your rules decide whether the agent may reach the endpoint, and every call is logged. Connecting the next API is then an import rather than another install and auth step.
Can I limit what my agent is allowed to do with the CreativeClaw MCP API?
Yes. CreativeClaw routes every tool through one /mcp operation with the tool and its inputs in the request body, so a rule allows or withholds that operation as a whole rather than scoping individual tools. Because every call runs through your own Jentic One instance, each invocation is logged for you to review.
How do I generate media with the CreativeClaw MCP API through Jentic?
Search Jentic for 'generate a video', and it returns the CreativeClaw MCP operation with its input schema. Load the schema and execute POST /mcp with a tools/call request, with the credential injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED