Use the MiMo API via RunAPI with a model skill, unified auth, and pay-as-you-go pricing.
# Base URL
https://runapi.ai
# Endpoints
POST /v1/chat/completions
POST /v1/responses
POST /v1/messages
curl https://runapi.ai/v1/chat/completions \
-H "Authorization: Bearer $RUNAPI_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "mimo-v2.5",
"messages": [
{
"role": "user",
"content": "Summarize this report, identify its main points, and draft a clear response."
}
]
}'from openai import OpenAI
client = OpenAI(
base_url="https://runapi.ai/v1",
api_key="your-runapi-key"
)
response = client.chat.completions.create(
model="mimo-v2.5",
messages=[{"role": "user", "content": "Summarize this report, identify its main points, and draft a clear response."}]
)import OpenAI from "openai";
const client = new OpenAI({
baseURL: "https://runapi.ai/v1",
apiKey: "your-runapi-key"
});
const response = await client.chat.completions.create({
model: "mimo-v2.5",
messages: [{ role: "user", content: "Summarize this report, identify its main points, and draft a clear response." }]
});MiMo 2.5 is a language-model family. Both models support text-only requests through Chat Completions, Responses, and Anthropic Messages on their existing synchronous and SSE paths. Base mimo-v2.5 supports custom function calling and tool-result continuation on Chat Completions and native Anthropic Messages, including Claude Code, with sync and SSE responses. Pro and Responses retain basic text support. Base mimo-v2.5 additionally accepts remote HTTP(S) image_url parts in messages[].content[] only for synchronous OpenAI Chat Completions. mimo-v2.5-pro is text-only; image input through Responses, Anthropic Messages, streaming/SSE, data URLs, and audio/file/video is not verified.
| Endpoint | Protocol |
|---|---|
POST /v1/chat/completions | OpenAI compatible |
POST /v1/responses | OpenAI Responses |
POST /v1/messages | Anthropic compatible |
| Endpoint | Resolution | Duration | Price | |
|---|---|---|---|---|
| chat_completion | — | — | Input $0.09 / 1M tokens | Output $0.18 / 1M tokens | |
| response | — | — | Input $0.09 / 1M tokens | Output $0.18 / 1M tokens | |
| message | — | — | Input $0.09 / 1M tokens | Output $0.18 / 1M tokens |
Prices shown for mimo-v2.5. Other variants retain their own endpoint pricing.
Sign up and generate an API key from the dashboard.
Choose the version that best matches your quality and cost requirements.
Submit your prompt and parameters to the model's documented endpoint.
Poll the task or set a webhook, then download the completed output.
RunAPI supports text-only requests for both MiMo models through Chat Completions, Responses, and Anthropic Messages on their existing synchronous and SSE paths. The only verified image shape is base mimo-v2.5 with synchronous OpenAI Chat Completions, where messages[].content[] may contain text and remote HTTP(S) image_url parts. Pro remains text-only; other image and media shapes are closed or unverified.
A single RunAPI API key unlocks the whole model catalog across all providers. No separate accounts to create, no API keys to rotate per integration, and no credential management overhead. Add a new model to your app by changing one parameter.
Per-call pricing in USD, billed monthly into a single invoice. No subscription tiers, no minimum spend, and failed generations are never charged. The pricing page and check_pricing API show exact costs before you commit to a model.
Typed schemas, parameter constraints, and setup notes are packaged in the model skill so your implementation starts from the right contract. The skill loads into Claude Code, Codex, Gemini CLI, Cursor, and VS Code — your agent knows the correct request shape before you write a line of code.
Both models support text-only requests through Chat Completions, Responses, and Anthropic Messages on their existing synchronous and SSE paths. Base mimo-v2.5 additionally supports remote HTTP(S) image_url parts in messages[].content[] for synchronous OpenAI Chat Completions; mimo-v2.5-pro is text-only.
Text-only requests remain supported for both models through Chat Completions, Responses, and Anthropic Messages on their existing synchronous and SSE paths. For images, only base mimo-v2.5 with synchronous OpenAI Chat Completions and remote HTTP(S) image_url parts in messages[].content[] is verified.
Base mimo-v2.5 accepts remote HTTP(S) image_url parts alongside text in messages[].content[] only for synchronous OpenAI Chat Completions; Pro is text-only. Image input through Responses, Anthropic Messages, streaming/SSE, data URLs, and audio, file, or video is not verified.
Pick the cheapest variant that meets your quality bar. Most teams start on the fast variant and graduate to pro for production.
Creating an account and API key is free. API calls use prepaid, pay-as-you-go billing; add funds before making requests.
Where streaming is available, RunAPI streams end-to-end.