Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the contentmaschine.ai 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%2Fcontentmaschine.ai%2Fcontentmaschine" | shStep 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%2Fcontentmaschine.ai%2Fcontentmaschine" | 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.
What an agent can do with contentmaschine.ai API.
Generate images and produce variations, fusions, and upscales
Remove backgrounds and edit masked regions of an image
Generate videos and merge two videos together
Transcribe an audio file into text
Run text generation tools
GET STARTED
Poll job status and fetch short-lived file links
Patterns agents use contentmaschine.ai API for, with concrete tasks.
★ Agent-Generated Visual Assets
An AI agent connected through Jentic can produce finished imagery without a person in the loop: it submits an image generation request, polls the job until it completes, and fetches a short-lived link to the result. The async job model lets the agent start a render and check back rather than holding a request open.
Generate an image from a prompt, poll the job until it finishes, and fetch a short-lived link to the result
Image Post-Processing
Generated images often need cleanup before use. ContentMaschine upscales an image, removes its background, and edits a masked region, so an agent can take a raw render and turn it into a product-ready shot in a single pipeline of calls.
Upscale a generated image and remove its background for a product shot
Video Creation
Short video assets can be assembled programmatically. ContentMaschine generates a video from a prompt and merges two videos the caller owns, so an agent can render clips and concatenate them into one deliverable.
Generate two short video clips and merge them into one
Audio Transcription
Spoken content becomes searchable once transcribed. ContentMaschine transcribes an audio file the caller owns and returns the transcript, so an agent can turn a recording into text it can summarize or index.
Transcribe an uploaded audio file and read the resulting transcript
52 endpoints — the contentmaschine api generates and edits images, videos, audio, and text from one media endpoint set.
METHOD
PATH
DESCRIPTION
/v1/images/generate
Generate an image
/v1/images/upscale
Upscale an image
/v1/images/remove-background
Remove an image background
/v1/videos/generate
Generate a video
/v1/audio/transcribe
Transcribe an audio file
/v1/text/generate
Run a text generation tool
/v1/jobs/{id}
Poll job status
/v1/images/generate
Generate an image
/v1/images/upscale
Upscale an image
/v1/images/remove-background
Remove an image background
/v1/videos/generate
Generate a video
/v1/audio/transcribe
Transcribe an audio file
/v1/text/generate
Run a text generation tool
/v1/jobs/{id}
Poll job status
What agents get from Jentic-routed access to this vendor.
Setup
Wiring ContentMaschine by hand means handling its bearer sk-cm- key or an OAuth2 token with per-media-type scopes, and polling a job for every async image or video render. Through Jentic you install once, import ContentMaschine from the API Directory, store the credential once, and your agent calls it.
Permission scoping
ContentMaschine groups its operations by media type (images, videos, audio, text) and takes inputs in the request body rather than a resource in the URL path, so a rule bounds which operations your agent may call. Limit it to the operations it needs, such as image generation and upscaling, and leave video, audio, and file-deletion operations out unless you add them.
Credential isolation
Your ContentMaschine 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 'generate an image' or 'transcribe audio', and Jentic returns the matching ContentMaschine operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using contentmaschine.ai API through Jentic.
What authentication does the ContentMaschine API use?
The ContentMaschine API authenticates with a bearer API key (keys use an sk-cm- prefix) or an OAuth2 access token whose scopes are granted per media type, such as images:write or videos:read, per its OpenAPI spec. When you call it through Jentic, that credential is stored once by your own Jentic One instance and injected at execution time, so it never reaches the agent's prompt or logs.
Can I edit an image with the ContentMaschine API, not just generate one?
Yes. Beyond image generation, the API upscales an image, removes its background, edits a masked region, and creates variations and fusions, so an agent can run a full edit pipeline on an image it generated or uploaded.
What are the rate limits for the ContentMaschine API?
The OpenAPI spec does not define numeric rate limits for the ContentMaschine API. Check the ContentMaschine documentation at https://contentmaschine.ai for the current request limits that apply to your key.
Can I limit what my agent is allowed to do with the ContentMaschine API?
Yes. ContentMaschine groups operations by media type and takes inputs in the request body, so a rule bounds which operations the agent may call. Write a rule that allows only the image generation and upscale operations, so the agent can create and enlarge images but cannot generate video, transcribe audio, or delete files, and every call it makes is logged.
How do I generate an image with the ContentMaschine API through Jentic?
Search Jentic with an intent like 'generate an image from a prompt', and Jentic returns the image generation operation at /v1/images/generate with its input schema so your agent submits the prompt and then polls the job for the result. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there a ContentMaschine MCP server?
You don't need an MCP server to give your agent ContentMaschine. Jentic connects it directly from the API Directory: import the API, store your key once, and your agent calls the image, video, audio, and text operations on demand.
For Agents
Generate and edit images, videos, audio, and text, poll long-running generation jobs, and fetch results through short-lived signed links with the ContentMaschine API.
Use for: Generate an image from a prompt, Create a variation of an existing image, Upscale an image to a higher resolution, Remove the background from an image
Not supported: Does not run a persistent media CDN beyond short-lived links, and does not handle live streaming. Use for AI generation and editing of images, video, audio, and text only.
The ContentMaschine API generates and edits images, videos, audio, and text from one media endpoint set. It generates images and produces variations, fusions, upscales, background removals, and masked region edits, generates and merges videos, transcribes audio, and runs text tools. Long-running operations return a job that is polled for status, and generated files are served through short-lived signed links. Authentication uses a bearer API key with an sk-cm- prefix or an OAuth2 access token scoped per media type.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
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>