Endpoint coverage
Exposes 1 public endpoint(s): chat_completion.
Smaller GPT-4.1 model; 1M context, image input and tools via OpenAI-compatible API
# Base URL
https://runapi.ai
# Endpoints
POST /v1/chat/completions
POST /v1/responses
POST /v1/messages
POST /v1beta/models/gpt-4.1-mini:generateContent
POST /v1beta/models/gpt-4.1-mini:streamGenerateContent
curl https://runapi.ai/v1/chat/completions \
-H "Authorization: Bearer $RUNAPI_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "gpt-4.1-mini",
"messages": [
{
"role": "user",
"content": "Analyze this quarterly revenue data and produce a summary with key trends, anomalies, and three recommendations."
}
]
}'
from openai import OpenAI
client = OpenAI(
base_url="https://runapi.ai/v1",
api_key="your-runapi-key"
)
response = client.chat.completions.create(
model="gpt-4.1-mini",
messages=[{"role": "user", "content": "Analyze this quarterly revenue data and produce a summary with key trends, anomalies, and three recommendations."}]
)
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: "gpt-4.1-mini",
messages: [{ role: "user", content: "Analyze this quarterly revenue data and produce a summary with key trends, anomalies, and three recommendations." }]
});
23 versions available
GPT-4.1 mini is the smaller member of OpenAI's GPT-4.1 family, released on April 14, 2025 as the snapshot gpt-4.1-mini-2025-04-14. It keeps the 1,047,576-token context window and 32,768 max output tokens of GPT-4.1, and OpenAI targets it at fast instruction-following and tool-calling workloads.
It accepts text and image input and answers without a reasoning step. OpenAI supports function calling and structured outputs on the model, and recommends GPT-5 mini for more complex tasks.
On RunAPI, call gpt-4.1-mini through the OpenAI-compatible Chat Completions endpoint (/v1/chat/completions) with the OpenAI SDK pointed at https://runapi.ai/v1. The same API key also calls gpt-4.1 and the newer GPT models, so you can switch by changing the model ID.
Pick any model and generate in seconds.
| Provider | OpenAI |
| Model ID | gpt-4.1-mini |
| Modality | Text |
| Task types | Synchronous |
| API endpoint | /v1/chat/completions |
| /v1/responses |
| /v1/messages | |
| /v1beta/models/gpt-4.1-mini:generateContent | |
| /v1beta/models/gpt-4.1-mini:streamGenerateContent | |
| Billing unit | 1K tokens |
| Catalog status | Operational |
Sign up for free and create an API key for gpt-4.1-mini from the dashboard.
POST to /v1/chat/completions with the gpt-4.1-mini model slug and your parameters.
Read the completed gpt-4.1-mini response directly from the endpoint.
Exposes 1 public endpoint(s): chat_completion.
Metered by 1K tokens with no subscription requirement.
No request parameters are published for this endpoint.
Answer customer questions from a private knowledge base, reducing ticket volume.
Draft contract summaries and flag key clauses for attorney review.
Auto-generate unit tests, code reviews, and refactoring suggestions in CI.
Verified customer feedback is not available for this model yet.
Use gpt-4.1-mini for fast, high-volume instruction following and tool calls where the larger model is not needed. Use gpt-4.1 for harder instructions. Both share the same context window, output limit, and input types.
Yes. It takes text and image input. On RunAPI, add image_url parts next to the text in messages[].content[] of a Chat Completions request.
No. Like gpt-4.1, it has no reasoning step. OpenAI recommends GPT-5 mini for more complex tasks.
Point the OpenAI SDK at https://runapi.ai/v1 with your RunAPI API key and send Chat Completions requests with model set to gpt-4.1-mini. Tools use the standard OpenAI tools format.
Pass the model ID shown in the quickstart.
Per-key rate limits scale with your usage tier. The pricing page shows current limits. If you need higher throughput, contact support to discuss tier upgrades.
Yes. Variant is a parameter in the request. Switch by changing the model ID — no code changes, no re-authentication, no separate billing setup. All variants share the same API key and request shape.
Where streaming is available, RunAPI streams end-to-end. LLM models support token-level streaming. Media models use async task polling or webhook callbacks for result delivery.
Open an issue on the public GitHub repo or email support at [email protected]. Include the task ID and model ID so the team can investigate the specific generation.
No. Your RunAPI API key is enough to access this variant and every other model in the catalog. You do not need accounts with the underlying provider.
We're here to help with enterprise setup, integrations, and technical questions.
Contact Us