models

OpenAI: o4 Mini (batch)

Markdown · JSON

OpenAI: o4 Mini (batch)

OpenAI o4-mini is a compact reasoning model focused on efficient coding and visual tasks. It accepts text and images, returns text, and supports structured answers and tools for solving a bounded technical problem or extracting a useful conclusion from supplied material.

About the model

This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.

o4-mini is OpenAI’s compact o-series reasoning model, optimized for fast, effective reasoning in coding and visual tasks. It accepts text and images and produces text. Its useful role is a defined technical problem that needs analysis before an answer: understanding a code failure, interpreting a diagram, connecting facts in supplied material or producing a structured result that a subsequent step can use.

For coding, give the model the relevant function or files, the expected behavior and the exact failing input or error. Include the language and environment details that affect the result. A focused request can ask for the likely cause, a minimal proposed correction and an explanation of how the change addresses the observed behavior. Define the boundary of the change, such as preserving the public interface or the meaning of existing data, so the result can be reviewed against the actual task.

For a visual problem, provide a legible screenshot, diagram or chart and identify the question it should answer. Keep meaningful labels, axes and units visible. An illustrative brief is to explain what a chart supports, identify the observations used, and separate a visible value from an inference. For a document task, label the source material and define the fields or relationships required in the answer. A compact model still benefits from complete problem information and a precise output request.

OpenAI specifies a 200,000-token context window, a maximum output of 100,000 tokens and a knowledge cutoff of June 1, 2024. Reasoning tokens consume both context and output capacity, so leave room for analysis and the final response rather than filling the entire allowance with input. Reaching a context or output limit can produce an incomplete response before any visible answer. A short final answer can still require internal reasoning; its visible length alone does not describe the full token budget.

The exact o4-mini model page lists Chat Completions, Responses, Batch and fine-tuning interfaces. Its documented features include streaming, Structured Outputs, function calling, file uploads, image input, file search, prompt caching and fine-tuning. The tool set lists web and file search, code interpretation and MCP connections. Give an application tool a clear purpose and input contract, return the actual result, and ask the model to use that result for the next decision. A requested function call is an action proposal, while a structured final answer organizes the information the task produces.

OpenAI’s o-series prompting guidance recommends a simple, direct goal with explicit constraints and clear delimiters around source material. Let the model work through the problem internally; request the final explanation, evidence or calculation you need instead of a transcript of hidden reasoning. Try a clear task brief first, then add examples when a required format or category boundary remains unclear. An example should demonstrate the same rules as the real task, including how to represent missing information.

For applications that need an optional explanation of the reasoning process, OpenAI’s reasoning guide explicitly documents detailed reasoning summaries for o4-mini. A summary must be requested and is distinct from the raw internal reasoning tokens, which are not exposed. The final answer still needs to contain the result the user asked for: for example, a proposed code change, a chart interpretation with relevant observations, or extracted fields tied to the supplied material. Supply recent facts when they matter, verify important claims against their source, and use a bounded task and completion criterion to keep the workflow focused.

Ailoot Ultra · Batch POST /v1/batches openai/o4-mini:batch

openai/o4-mini:batch

OpenAI /openai/o4-mini:batch

Overview

OpenAI o4-mini is a compact reasoning model focused on efficient coding and visual tasks. It accepts text and images, returns text, and supports structured answers and tools for solving a bounded technical problem or extracting a useful conclusion from supplied material.

Accepted inputs
Text
Results
Text

Available in Ailoot · inputs & methods

Ailoot Ultra · Batch POST /v1/batches
Input types
text
Output types
text
Output format
inline results[].response.body JSON
FieldTypeRequirementValues & limitsDefault
FieldendpointTypestringRequirementRequiredValues & limits
/v1/chat/completions
Default—
FieldmodelTypestringRequirementRequiredValues & limits
openai/o4-mini:batch
Default—
FieldrequestsTypebatch_item[]RequirementRequiredValues & limits
Minimum items: 1
Default—
Fieldrequests[].custom_idTypestringRequirementRequiredValues & limitsDefault—
Fieldrequests[].body.messagesTypemessage[]RequirementRequiredValues & limitsDefault—
Fieldcompletion_windowTypestringRequirementOptionalValues & limits
24h
Default—
FieldproviderTypeobject|nullRequirementOptionalValues & limitsDefault—
Fieldrequests[].body.modelTypestringRequirementOptionalValues & limits
openai/o4-mini:batch, openai/o4-mini
Default—
Fieldprovider.onlyTypestring[]RequirementOptionalValues & limits
openai
Default—
Fieldprovider.allow_fallbacksTypeboolean|nullRequirementOptionalValues & limits
false, null
Default—
Method parameters and lifecycle
ParameterContract
Parametercontent_typeContractapplication/json
ParameterrequiredContractendpoint, model, requests
Parametermaterial_typesContracttext
ParameterrepresentationContractinline requests[]; each item has custom_id and body
Parameterrequest_endpoint_profileContract/v1/chat/completions
Parameterfile_materialContractCaller may read actual UTF-8 JSONL locally into requests[]. No upload purpose, input_file_id or file reference is used. Missing/empty customer material stops preparation before POST.
Parameterserialization_orderContractendpoint, model, provider (if supplied), completion_window (if supplied), requests last
Parameteroptional_controlsContractprovider.only, provider.allow_fallbacks, completion_window
Parameterschema_scopeContractText Chat Completions bodies in the documented inline Batch envelope.

Lifecycle: asynchronous

GET /v1/batches/{operation_id} · actual original create response.id; same user/key/group

Pricing

Tariff references do not add request options. Supported parameters are listed for the selected method.

Fast mode
Not specified When fast mode is selected
Flex mode
Not specified When flex mode is selected
Maximum reasoning effort
Not specified When maximum reasoning effort uses the default adjustment
Explicit cache pricing
Not enabled When explicit cache is requested

Ailoot rates

Prices by configuration

Match each charge to the conditions shown. Use one rate for each set of alternative configurations.

ConfigurationRate scheduleContext tokens, more thanContext tokens, up to and includingCharge
ConfigurationBase token ratesRate scheduleBase rateContext tokens, more than—Context tokens, up to and includingNo upper boundCharge
Input · Input tokens $0.0011 / 1K tokens
Output · Output tokens $0.0044 / 1K tokens
Input · Cache read $0.000275 / 1K tokens
Input · Cache write — / 1K tokens
Input · Cache write, 1 hour — / 1K tokens
ConfigurationRequest-length tier 1Rate schedule—Context tokens, more than0Context tokens, up to and includingNo upper boundCharge
Input · Input tokens $0.0011 / 1K tokens
Output · Output tokens $0.0044 / 1K tokens
Input · Cache read $0.000275 / 1K tokens
Input · Cache write — / 1K tokens
Input · Cache write, 1 hour — / 1K tokens

Ailoot reserves an estimated amount before a request. After the result, it settles the final charge from measured usage. Streaming settlement uses the final usage record. How reservation and settlement work →

Example requests

Ailoot Ultra · Batch

curl · retained fixturePython HTTP · actual customer JSONLPython · save every completed result
set -eu
: "${AILOOT_API_KEY:?Set your Ailoot API key}"
python3 - <<'PY_REQUEST'
import json
from pathlib import Path
body=json.loads('{"endpoint":"/v1/chat/completions","model":"openai/o4-mini:batch","requests":[{"custom_id":"req-0001","body":{"messages":[{"role":"user","content":"Hello!"}],"max_tokens":16}}]}')
Path("batch-request.json").write_text(json.dumps(body,ensure_ascii=False),encoding="utf-8")
PY_REQUEST
curl --fail-with-body --silent --show-error https://api.ailoot.ai/v1/batches \
  -H "Authorization: Bearer $AILOOT_API_KEY" -H 'Content-Type: application/json' \
  --data-binary @batch-request.json -D batch-response-headers.txt -o batch-create-response.json
import json, os
from pathlib import Path
from urllib.request import Request, urlopen

def prepare_requests(customer_path):
    path = Path(customer_path)
    if not path.is_file(): raise ValueError("Customer JSONL file is missing")
    items = [json.loads(line) for line in path.read_text(encoding="utf-8").splitlines() if line.strip()]
    if not items: raise ValueError("Customer JSONL contains no requests")
    ids = set()
    for item in items:
        if set(item) != {"custom_id", "body"}: raise ValueError("Each item needs custom_id and body")
        cid = item["custom_id"]
        if not isinstance(cid, str) or not cid.strip() or cid in ids: raise ValueError("custom_id must be nonempty and unique")
        ids.add(cid)
        if not isinstance(item["body"], dict) or not item["body"].get("messages"): raise ValueError("Supply actual text messages")
        supplied_model = item["body"].get("model")
        if supplied_model is not None and supplied_model not in ['openai/o4-mini:batch', 'openai/o4-mini']: raise ValueError("body.model must be an exact documented caller or wire ID")
    return {"endpoint":"/v1/chat/completions", "model":"openai/o4-mini:batch", "requests":items}

if __name__ == "__main__":
    material = os.environ.get("AILOOT_BATCH_REQUESTS_JSONL", "")
    if not material: raise SystemExit("Set AILOOT_BATCH_REQUESTS_JSONL to your actual customer file")
    body = prepare_requests(material)
    key = os.environ.get("AILOOT_API_KEY", "")
    if not key: raise SystemExit("Set AILOOT_API_KEY")
    request = Request("https://api.ailoot.ai/v1/batches", data=json.dumps(body, ensure_ascii=False).encode("utf-8"), headers={"Authorization":"Bearer " + key, "Content-Type":"application/json"}, method="POST")
    with urlopen(request) as response:
        raw = response.read()
        Path("batch-create-response.json").write_bytes(raw)
        print(raw.decode("utf-8"))
import json
from pathlib import Path
raw = Path("batch-status-response.json").read_bytes()
response = json.loads(raw)
if response.get("status") != "completed":
    raise SystemExit("Keep the original operation; read its status without resubmitting")
results = response.get("results")
if not isinstance(results, list) or not results:
    raise SystemExit("Preserve the original response; completed results are missing")
Path("batch-results.jsonl").write_text("".join(json.dumps(item, ensure_ascii=False) + "\n" for item in results), encoding="utf-8")
# Preserve batch-status-response.json with aggregate usage and every result/error.

Receive and save results

Ailoot Ultra · Batch

inline results[].response.body JSON

  • GET /v1/batches/{operation_id}
Check job status
curl · original operation status
set -eu
: "${AILOOT_API_KEY:?Set your Ailoot API key}"
BATCH_OPERATION_ID="$(python3 - <<'PY_ID'
import json
from pathlib import Path
from urllib.parse import quote
response = json.loads(Path("batch-create-response.json").read_text(encoding="utf-8"))
operation = response.get("id")
if not isinstance(operation, str) or not operation: raise SystemExit("No actual original operation ID; preserve the response and do not resubmit")
print(quote(operation, safe=""))
PY_ID
)"
curl --fail-with-body --silent --show-error "https://api.ailoot.ai/v1/batches/$BATCH_OPERATION_ID" \
  -H "Authorization: Bearer $AILOOT_API_KEY" -o batch-status-response.json
Keep all completed results

Keep every complete returned response, file and content part.

Preserve the full original status JSON, every result/custom_id and complete response or error body. Save completed results[] as JSONL without filtering.

If the original response needs checking

Preserve the original operation ID. 503 result_pending_check has X-Should-Retry:false; never resubmit an unknown original batch.

Response fields
FieldType
Fieldresults[].custom_idTypestring
Fieldresults[].response.body.choices[].message.contentTypestring|null
Fieldresults[].errorTypeobject|null
FieldusageTypeobject|null
FieldidTypestring
FieldmodelTypestring
FieldendpointTypestring
FieldstatusTypestring
Fieldrequest_countsTypeobject
Fieldresults[].idTypestring
Fieldresults[].response.status_codeTypeinteger
Fieldresults[].response.request_idTypestring
Errors and next steps
ResponseConditionNext step
Response400 · invalid_request_errorConditionInvalid documented inline envelope, duplicate keys, item identity, or configured model capabilities conflict.Next stepCorrect the indicated fields before any new submission.
Response401 · authentication_errorConditionInvalid API key.Next stepUse the authorized Ailoot key.
Response403 · permission_errorConditionBatch group unavailable.Next stepCheck key/group entitlement.
Response422 · invalid_request_errorConditionBatch uses balance billing; subscription creation is rejected.Next stepUse the authorized balance-billed group.
Response422 · price_unavailableConditionBatch input cannot be quoted.Next stepPreserve response; use documented family input.
Response402 · billing_errorConditionBatch reserve unavailable.Next stepResolve admission before a new request.
Response503 · price_unavailableConditionBatch method price/native rates unavailable.Next stepPreserve response; do not substitute prices.
Response503 · api_errorConditionExact supplier route unavailable.Next stepPreserve response for route repair.
Response503 · result_pending_checkConditionOriginal result requires checking; X-Should-Retry:false.Next stepKeep original operation_id/id and read its status; never repeat original POST.
Response404 · not_foundConditionBatch status operation absent or owned by another identity.Next stepUse exact original id and same user/key/group.

Aliases

Model aliases

Ailoot Ultra openai/o4-mini:batch

Method path aliases

Use the method paths shown above.

Related caller IDs

openai/o4-mini:batch

FAQ · OpenAI: o4 Mini (batch)
What inputs and results are available?

POST /v1/batches · openai/o4-mini:batch: text → text

Which fields does the request use?

POST /v1/batches · openai/o4-mini:batch: endpoint, model, requests, completion_window, provider

What limits apply?

POST /v1/batches · openai/o4-mini:batch: requests.min_items: 1

More details

Connect Ailoot to Claude Code, OpenCode, Hermes or your own app.

The company and its project portfolio

The company and its project portfolio: millions of customers; monthly sales in the billions.

Buy tokens at a discount.

Subscription discounts for regular use. Promo codes offer up to 50% off token purchases.

Subscription
Choose a discounted plan for your regular requests.
Promo code: up to 50% off
Enter your code at checkout. The price updates to reflect the current promotion.
Spending in your history
The model, tokens and amount are recorded for each request.

Choose a subscription · View model prices

Connect the API to a product you sell.

Use Ailoot in SaaS, apps and bots under its official service offer and licence agreement. Request a reseller licence for resale.

Commercial application
Add text, image, video and audio generation to paid features in your service.
Reseller licence
Send a description of your project and how you provide access. Request written terms for use and resale.
Documents on the website
The service offer, licence agreement and data processing policy are available before you connect.

Request a reseller licence · Service offer and licence agreement