Install Jentic One Beta

Connect the Muapi API to your agent

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

Generate images from a text prompt with models such as flux-dev, nano-banana, midjourney-v7, and gpt-image-2

Turn a prompt or still image into video with Veo 3.1, Kling, and Seedance model endpoints

Create songs, text-to-speech, and sound with Suno, ElevenLabs, MiniMax, and Lyria endpoints

Lipsync or translate an existing video with sync-lipsync, latentsync, and heygen-video-translate

GET STARTED

Start building with Muapi API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Muapi API for, with concrete tasks.

★ AI creative agent producing images and video on request

An AI agent asked for a campaign visual and a matching clip needs one integration, not a separate account per model vendor. Through Jentic the agent searches for 'generate an image from a prompt', loads a Muapi model operation such as flux-dev-image with its input schema, submits the prompt, and polls the prediction result route with the returned request_id until the status is completed. The same pattern then drives an image-to-video model, with the Muapi key injected at call time.

Call POST /api/v1/flux-dev-image with a prompt, then poll GET /api/v1/predictions/{id}/result with the returned request_id until status is completed and return the image URL

Text-to-video for social ads

A marketer drafting short ads sends a scene description to a video model and picks a quality tier per draft. Muapi labels operations best, balanced, fast, or budget in their summaries, so a pipeline can draft with a fast model such as veo3.1-fast-text-to-video and render the final cut with veo3.1-text-to-video, which takes prompt, aspect_ratio, resolution, and duration.

Call POST /api/v1/veo3.1-fast-text-to-video with a prompt and aspect_ratio 9:16, review the draft from the prediction result, then call POST /api/v1/veo3.1-text-to-video with the same prompt

Music and voice for video content

A creator needs a soundtrack and narration for a clip. The Suno create-music operation takes a required style plus an optional prompt, title, and instrumental flag, and text-to-speech models such as elevenlabs-v4 and minimax-speech-2.6-hd return narration. Each request lands on the same prediction result route, so the agent collects audio the same way it collects images.

Call POST /api/v1/suno-create-music with style set to lo-fi hip hop and instrumental true, then fetch the track from GET /api/v1/predictions/{id}/result

Product images to 3D assets

An e-commerce team wants 3D previews from existing product photos. Muapi exposes Meshy and Tripo3D operations for single-image, multi-image, and text-to-3D generation, and media can first be uploaded to Muapi-hosted storage so the model receives a hosted URL.

Upload a product photo with POST /api/v1/upload_file, then call POST /api/v1/meshy-6-image-to-3d with the hosted URL and poll the prediction result for the model file

Key Endpoints

1304 endpoints — the muapi api runs hundreds of generative media models behind one key, with an operation per model for text-to-image, image editing, text-to-video, image-to-video, video editing, lipsync, avatars, audio and music, and 3d generation.

METHOD

PATH

DESCRIPTION

POST

/api/v1/flux-dev-image

Generate an image with Flux Dev

POST

/api/v1/veo3.1-text-to-video

Generate a video with Veo 3.1

POST

/api/v1/seedance-2.5-image-to-video

Animate an image with Seedance 2.5

POST

/api/v1/suno-create-music

Create a song with Suno

POST

/api/v1/meshy-6-image-to-3d

Build a 3D model from an image

GET

/api/v1/predictions/{id}/result

Poll a prediction's status and outputs

POST

/api/v1/upload_file

Upload media to Muapi storage

GET

/api/v1/account/balance

Get wallet balance

POST

/api/v1/flux-dev-image

Generate an image with Flux Dev

POST

/api/v1/veo3.1-text-to-video

Generate a video with Veo 3.1

POST

/api/v1/seedance-2.5-image-to-video

Animate an image with Seedance 2.5

POST

/api/v1/suno-create-music

Create a song with Suno

POST

/api/v1/meshy-6-image-to-3d

Build a 3D model from an image

GET

/api/v1/predictions/{id}/result

Poll a prediction's status and outputs

POST

/api/v1/upload_file

Upload media to Muapi storage

GET

/api/v1/account/balance

Get wallet balance

Why Jentic?

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

Setup

Wiring Muapi by hand means choosing between an x-api-key and OAuth client credentials, picking the right model operation out of a very large surface, and building a poll loop on the prediction result route. Through Jentic you install once, import Muapi from the API Directory, store the key once, and your agent calls it.

Permission scoping

Each Muapi model has its own path, such as /api/v1/veo3.1-text-to-video, so a rule can bound your agent to the models it should use plus the prediction result read. That matters because the spec notes a Muapi API key is unscoped. You choose the operations it may call, so key creation, key deletion, and wallet top-up are not included unless you add them.

Credential isolation

Your Muapi API key or OAuth client secret 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 'turn an image into a video' or 'generate a song', and Jentic returns the matching Muapi model operation with its input schema, so the agent picks a fitting model without paging through the reference docs.

FAQs

Specific to using Muapi API through Jentic.

What authentication does the Muapi API use?

The Muapi OpenAPI spec declares two schemes, and every operation accepts either. One is an API key sent in the x-api-key header, which the spec says is also accepted as Authorization: Bearer and carries full account access. The other is OAuth 2.0 client credentials from the Muapi token endpoint with scopes such as generate:write, generate:read, files:write, account:read, and keys:manage. Through Jentic your key or client secret is held by your own instance and injected at call time.

How do I get the output of a Muapi generation?

Generation is asynchronous. A model operation such as POST /api/v1/flux-dev-image returns a request_id, and GET /api/v1/predictions/{id}/result reports the status (queued, processing, completed, failed, and others) and the outputs once done. You can instead pass a webhook query parameter on the model call to have the result posted to your URL.

What are the rate limits for the Muapi API?

The OpenAPI spec does not specify numeric rate limits; usage is metered by credits debited from your wallet on completion, and GET /api/v1/account/balance reports what remains. Check https://muapi.ai for current plan limits.

Can I test Muapi without spending credits?

Yes. Creating a key with POST /api/v1/keys and is_test set to true in the body produces a sandbox key that returns mock outputs and never deducts credits, which suits wiring up an agent before real runs.

How do I generate a video through Jentic?

Search Jentic for 'generate a video from a text prompt', load an operation such as POST /api/v1/veo3.1-text-to-video, execute it with a prompt, then load GET /api/v1/predictions/{id}/result and poll it with the returned request_id. To run it on your own infrastructure, install Jentic One from its GitHub repo.

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

Yes. Write a rule that allows only POST /api/v1/flux-dev-image and GET /api/v1/predictions/{id}/result, and the agent can generate images with that one model and fetch the results, but cannot create keys, top up the wallet, or run costlier video models. Every call it makes is logged so you can see what it spent.

Muapi API

AI ReadinessFoundational (D+)49/100

See full scorecard

Official vendor OpenAPI document · agent-readyAI/MLMl InferenceapiKey, oauth21304 EndpointsREST

For Agents

Generate images, video, audio, music, and 3D assets from hundreds of models through one Muapi key, then poll each prediction for its output.

Use for: Generate a product photo from a text prompt, I want to turn this image into a short video, Create a 30-second background music track in a lo-fi style, Check whether my video generation has finished

Not supported: Does not train custom foundation models, host your own model weights, or edit media without a model call. Use for running Muapi-hosted generative image, video, audio, and 3D models only.

The Muapi API runs hundreds of generative media models behind one key, with an operation per model for text-to-image, image editing, text-to-video, image-to-video, video editing, lipsync, avatars, audio and music, and 3D generation. Model operations such as flux-dev-image, veo3.1-text-to-video, seedance-2.5-image-to-video, suno-create-music, and meshy-6-image-to-3d are asynchronous: each returns a request_id, and the output is fetched from the prediction result route or pushed to a webhook. Supporting routes upload media to Muapi-hosted storage, report the wallet balance, manage API keys including sandbox keys, and expose OpenAI-compatible chat completions and image generation endpoints.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: B+Signals: 4

74%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

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.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

49%

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.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D-Signals: 4

10%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

51%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: D-Signals: 1

43%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B+Signals: 1

68%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: FSignals: 1

39%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Muapi API to your agent

Capabilities

Start building with Muapi API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Muapi API

Jentic AI Readiness Score

Muapi API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness