Install Jentic One Beta

Connect the ModelRush Public API to your agent

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

List callable models and available regions before selecting one

Create chat completions against a chosen model

Generate and edit images from prompts or source media

Create asynchronous video generation jobs and poll their status

Synthesize speech and transcribe audio

GET STARTED

Start building with ModelRush Public API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use ModelRush Public API for, with concrete tasks.

★ AI agent multi-model routing via Jentic

An AI agent connected through Jentic runs a generation job without hardcoding one provider. It searches by intent such as creating a chat completion, Jentic returns the matching ModelRush operation with its input schema, and the agent lists current models, selects one, and runs the job. The developer's own Jentic One instance injects the bearer token at call time.

Call GET /models to list callable models, then POST /chat/completions against the chosen model

Image generation and editing

Design tools create and refine images from prompts. ModelRush generates images from a prompt and edits one or more source images, so an agent can produce a draft, upload a source, and request an edit through the same contract rather than integrating a separate image provider.

Call POST /images/generations with a prompt, then POST /images/edits with a staged source image

Asynchronous video and audio jobs

Media pipelines handle long-running generation. ModelRush creates asynchronous video jobs that an agent polls by id, synthesizes WAV speech, and transcribes audio, so a workflow can submit a job, receive a signed webhook on completion, and fetch the unified prediction result.

Call POST /videos/generations to start a job, then GET /videos/generations/{id} to poll its status

Region-aware model selection

Teams with data-residency needs pick an execution region before running billable work. The regions operation lists available API surfaces and regions, and the models operation reports what is currently callable, so an agent chooses a region and a current model rather than failing on a retired one.

Call GET /regions to list surfaces and regions, then GET /models to confirm the chosen model is callable

Key Endpoints

16 endpoints — the modelrush api runs chat, image, video, audio, and prediction workloads across many models behind one unified contract.

METHOD

PATH

DESCRIPTION

GET

/models

List callable models

GET

/regions

List API surfaces and regions

POST

/chat/completions

Create a chat completion

POST

/images/generations

Generate images

POST

/videos/generations

Create an asynchronous video job

GET

/videos/generations/{id}

Get video job status

POST

/audio/transcriptions

Transcribe audio

POST

/webhooks/endpoints

Create a signed webhook endpoint

GET

/models

List callable models

GET

/regions

List API surfaces and regions

POST

/chat/completions

Create a chat completion

POST

/images/generations

Generate images

POST

/videos/generations

Create an asynchronous video job

GET

/videos/generations/{id}

Get video job status

POST

/audio/transcriptions

Transcribe audio

POST

/webhooks/endpoints

Create a signed webhook endpoint

Why Jentic?

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

Setup

Wiring the ModelRush API by hand means learning its bearer scheme, listing current models and regions before each job, and polling asynchronous video and prediction status yourself. Through Jentic you install once, import ModelRush from the API Directory, store the token once, and your agent calls the discovery and generation operations.

Permission scoping

ModelRush carries the chosen model in the request body, so Jentic rules bound which operations your agent may call rather than which model. A rule can allow only the discovery and chat completion operations, so billable image, video, and audio generation stay out unless you add them.

Credential isolation

Your ModelRush bearer token 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 'create a chat completion' or 'generate an image', and Jentic returns the matching ModelRush operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using ModelRush Public API through Jentic.

What authentication does the ModelRush API use?

The ModelRush API authenticates with an HTTP bearer token in the Authorization header, per its OpenAPI spec, and the vendor advises keeping API keys server-side. The model and region discovery operations are open, while generation operations require the token. Through Jentic, your token is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's context.

Can I run chat, image, and video jobs through one ModelRush contract?

Yes. The chat completions, image generation and edit, video generation, speech, and transcription operations all share one contract, and the models operation lists what is callable, so an agent can route different workloads to different models without separate integrations.

What are the rate limits for the ModelRush API?

The OpenAPI spec does not state numeric rate limits, and authenticated generation operations may create billable usage. Check the ModelRush documentation at https://modelrush.ai for current limits and pricing before running large jobs.

How do I create a chat completion through Jentic?

Search Jentic by intent such as creating a chat completion, and it returns the ModelRush operation with its input schema. List current models, select one, and run the completion, with your token injected at call time. 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 ModelRush API?

Yes. Write a rule that allows only the discovery and chat completion operations, so the agent can list models and converse but cannot start billable image, video, or audio generation jobs unless you add those operations, and every call it makes is logged by your self-hosted instance.

Is there a ModelRush API MCP server?

You do not need an MCP server to give your agent the ModelRush API. Jentic connects it directly from the API Directory: import it, store your bearer token once, and your agent calls the discovery and generation operations on demand without loading another server's tool definitions into its context.

ModelRush Public API

AI ReadinessAI-Aware (B-)63/100

See full scorecard

Official vendor OpenAPI document · agent-readyAI/MLMl Inferencebearer16 EndpointsREST

For Agents

Run chat, image, video, audio, and prediction jobs across many models through one API, with model and region discovery, uploads, and signed webhooks.

Use for: I need to create a chat completion with a specific model, I want to generate an image from a text prompt, List the models currently callable through the API, Create an asynchronous video generation job

Not supported: Does not host datasets, fine-tune models, or manage billing accounts. Use for running chat, image, video, and audio inference across models only.

The ModelRush API runs chat, image, video, audio, and prediction workloads across many models behind one unified contract. Discovery operations list callable models and available regions so a caller can pick a current model before running a job, and generation operations create chat completions, images, image edits, speech, transcriptions, and asynchronous video jobs. Private upload slots stage source media, predictions track unified job status, and signed webhook endpoints deliver results as they complete.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

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.

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.

44%

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

14%

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.

57%

Summary Coverage

Coverage of summaries across operations/tags/info.

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.

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).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: BSignals: 1

64%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the ModelRush Public API to your agent

Capabilities

Start building with ModelRush Public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

ModelRush Public API

Jentic AI Readiness Score

ModelRush Public 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