GPT-4o Mini is OpenAI’s small GPT-4o-family model for focused work. It takes text and images and produces text, including Structured Outputs. Its role is useful when an application needs a concise response to a well-specified request: extracting fields, developing a reply from supplied reference material or carrying out a bounded step in a larger process.
For a support response, provide the incoming message, relevant policy excerpts and the facts already established in the conversation. Ask for a short proposed reply and identify any information still needed from the sender. For document extraction, define the fields, explain how to handle missing values and preserve a label that connects each result to its source. The same approach can produce a classification, an edited passage or an explanation of a small code change without treating the model as a substitute for the application’s surrounding logic.
The producer lists a 128,000-token context window, a maximum output of 16,384 tokens and a knowledge cutoff of October 1, 2023. Source material, conversation and generated output occupy that context together. Keep significant earlier facts visible and state the required final artifact. GPT-4o Mini is a separate small model, not an output-length mode of full GPT-4o; its own identity and capabilities should guide the task even where the two models share specifications.
Images can supply a screenshot, a document page, a photograph or a diagram. OpenAI’s vision workflow accepts PNG, JPEG, WebP and non-animated GIF, with low, high or auto detail for this family. Higher detail follows the producer’s tile-based image handling. Keep important labels readable and upright, and explain which part of the image should inform the answer. Fine spatial relationships, exact object counts, unusual image projections and some non-Latin text are documented difficulties. A focused question makes a visual response easier to compare with the original evidence. In OpenAI’s documented vision workflow, the total request payload is limited to 512 MB and a request can include up to 1,500 images; the images and text must also fit the model’s context.
The producer’s file workflow passes extracted text and page images from PDFs to vision-capable models. Other office and text files contribute extracted text, so their embedded images and charts need a PDF representation when those visuals matter. Spreadsheet augmentation uses up to the first 1,000 rows per sheet. Each file must be under 50 MB, with a combined request allowance of 50 MB. Chat Completions accepts PDF file parts; the documented Responses workflow accepts a broader set of file formats. Preserve page, row or section identifiers in the material you use for extraction.
Streaming returns text incrementally. Structured Outputs constrains a completed response to the supported JSON Schema subset, whereas a request for JSON mode only ensures valid JSON. Name the required fields and permitted values, including an explicit representation for missing evidence. Applications need to handle refusals and incomplete responses separately. A schema can make the artifact suitable for the next stage, but the values still need to reflect the actual source rather than an invented completion of an empty field.
GPT-4o Mini supports function calling and the producer’s tool-oriented workflows with web search, file search, code interpretation and MCP connections. Describe an available function, let the application execute the requested operation and return its observation before the model develops a follow-up answer. OpenAI also supports a separate image-generation tool in the configured Responses workflow. Images produced by that tool are separate artifacts; the model’s native documented output remains text. Search and tool use are configured activities, rather than evidence that every reply consulted current information.
Predicted Outputs supports regenerating a largely known document or code file with a small change. Provide the previous content and the precise edit, then compare the resulting artifact with that request. The prediction path supports text only and does not combine with function calling; logprobs, max_completion_tokens and several other controls are also excluded. An ordinary tool-using request is a different path when the reply depends on a fresh lookup or calculation.
OpenAI documents fine-tuning for this model and describes using a larger model’s outputs to teach a smaller GPT-4o Mini model a specialised task. This distillation workflow produces a customised model; it does not change the identity of a normal Mini response. For an ordinary request, establish the task and output format with clear examples, then use a focused follow-up to revise the same result. A useful final artifact remains connected to the source facts, the intended reader and the application step that consumes it.
", "aboutText": "GPT-4o Mini is OpenAI’s small GPT-4o-family model for focused work. It takes text and images and produces text, including Structured Outputs. Its role is useful when an application needs a concise response to a well-specified request: extracting fields, developing a reply from supplied reference material or carrying out a bounded step in a larger process.\n\nFor a support response, provide the incoming message, relevant policy excerpts and the facts already established in the conversation. Ask for a short proposed reply and identify any information still needed from the sender. For document extraction, define the fields, explain how to handle missing values and preserve a label that connects each result to its source. The same approach can produce a classification, an edited passage or an explanation of a small code change without treating the model as a substitute for the application’s surrounding logic.\n\nThe producer lists a 128,000-token context window, a maximum output of 16,384 tokens and a knowledge cutoff of October 1, 2023. Source material, conversation and generated output occupy that context together. Keep significant earlier facts visible and state the required final artifact. GPT-4o Mini is a separate small model, not an output-length mode of full GPT-4o; its own identity and capabilities should guide the task even where the two models share specifications.\n\nImages can supply a screenshot, a document page, a photograph or a diagram. OpenAI’s vision workflow accepts PNG, JPEG, WebP and non-animated GIF, with low, high or auto detail for this family. Higher detail follows the producer’s tile-based image handling. Keep important labels readable and upright, and explain which part of the image should inform the answer. Fine spatial relationships, exact object counts, unusual image projections and some non-Latin text are documented difficulties. A focused question makes a visual response easier to compare with the original evidence. In OpenAI’s documented vision workflow, the total request payload is limited to 512 MB and a request can include up to 1,500 images; the images and text must also fit the model’s context.\n\nThe producer’s file workflow passes extracted text and page images from PDFs to vision-capable models. Other office and text files contribute extracted text, so their embedded images and charts need a PDF representation when those visuals matter. Spreadsheet augmentation uses up to the first 1,000 rows per sheet. Each file must be under 50 MB, with a combined request allowance of 50 MB. Chat Completions accepts PDF file parts; the documented Responses workflow accepts a broader set of file formats. Preserve page, row or section identifiers in the material you use for extraction.\n\nStreaming returns text incrementally. Structured Outputs constrains a completed response to the supported JSON Schema subset, whereas a request for JSON mode only ensures valid JSON. Name the required fields and permitted values, including an explicit representation for missing evidence. Applications need to handle refusals and incomplete responses separately. A schema can make the artifact suitable for the next stage, but the values still need to reflect the actual source rather than an invented completion of an empty field.\n\nGPT-4o Mini supports function calling and the producer’s tool-oriented workflows with web search, file search, code interpretation and MCP connections. Describe an available function, let the application execute the requested operation and return its observation before the model develops a follow-up answer. OpenAI also supports a separate image-generation tool in the configured Responses workflow. Images produced by that tool are separate artifacts; the model’s native documented output remains text. Search and tool use are configured activities, rather than evidence that every reply consulted current information.\n\nPredicted Outputs supports regenerating a largely known document or code file with a small change. Provide the previous content and the precise edit, then compare the resulting artifact with that request. The prediction path supports text only and does not combine with function calling; logprobs, max_completion_tokens and several other controls are also excluded. An ordinary tool-using request is a different path when the reply depends on a fresh lookup or calculation.\n\nOpenAI documents fine-tuning for this model and describes using a larger model’s outputs to teach a smaller GPT-4o Mini model a specialised task. This distillation workflow produces a customised model; it does not change the identity of a normal Mini response. For an ordinary request, establish the task and output format with clear examples, then use a focused follow-up to revise the same result. A useful final artifact remains connected to the source facts, the intended reader and the application step that consumes it.", "editorialOverlay": { "copy_fields": null, "copy_sha256": null, "copy_source": null, "html_sha256": "81b526c503b0e427503299181245c90cb983716938319618d3e42d0e06c60086", "module_sha256": "ee9dc1c50b1e6a8fb7fa062030fcb4646b9aaaeb08be513b723a5a92a7290f06", "raw_model_unchanged": true, "schema": "ailoot-native-model-editorial-v1" }, "locale": "en", "methods": [ { "html": "openai/gpt-4o-mini:batchGPT-4o Mini handles focused text and image tasks, including document extraction, concise replies and application tool calls. Its 128,000-token context and Structured Outputs support repeatable workflows with a clearly defined result.
This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.
GPT-4o Mini is OpenAI’s small GPT-4o-family model for focused work. It takes text and images and produces text, including Structured Outputs. Its role is useful when an application needs a concise response to a well-specified request: extracting fields, developing a reply from supplied reference material or carrying out a bounded step in a larger process.
For a support response, provide the incoming message, relevant policy excerpts and the facts already established in the conversation. Ask for a short proposed reply and identify any information still needed from the sender. For document extraction, define the fields, explain how to handle missing values and preserve a label that connects each result to its source. The same approach can produce a classification, an edited passage or an explanation of a small code change without treating the model as a substitute for the application’s surrounding logic.
The producer lists a 128,000-token context window, a maximum output of 16,384 tokens and a knowledge cutoff of October 1, 2023. Source material, conversation and generated output occupy that context together. Keep significant earlier facts visible and state the required final artifact. GPT-4o Mini is a separate small model, not an output-length mode of full GPT-4o; its own identity and capabilities should guide the task even where the two models share specifications.
Images can supply a screenshot, a document page, a photograph or a diagram. OpenAI’s vision workflow accepts PNG, JPEG, WebP and non-animated GIF, with low, high or auto detail for this family. Higher detail follows the producer’s tile-based image handling. Keep important labels readable and upright, and explain which part of the image should inform the answer. Fine spatial relationships, exact object counts, unusual image projections and some non-Latin text are documented difficulties. A focused question makes a visual response easier to compare with the original evidence. In OpenAI’s documented vision workflow, the total request payload is limited to 512 MB and a request can include up to 1,500 images; the images and text must also fit the model’s context.
The producer’s file workflow passes extracted text and page images from PDFs to vision-capable models. Other office and text files contribute extracted text, so their embedded images and charts need a PDF representation when those visuals matter. Spreadsheet augmentation uses up to the first 1,000 rows per sheet. Each file must be under 50 MB, with a combined request allowance of 50 MB. Chat Completions accepts PDF file parts; the documented Responses workflow accepts a broader set of file formats. Preserve page, row or section identifiers in the material you use for extraction.
Streaming returns text incrementally. Structured Outputs constrains a completed response to the supported JSON Schema subset, whereas a request for JSON mode only ensures valid JSON. Name the required fields and permitted values, including an explicit representation for missing evidence. Applications need to handle refusals and incomplete responses separately. A schema can make the artifact suitable for the next stage, but the values still need to reflect the actual source rather than an invented completion of an empty field.
GPT-4o Mini supports function calling and the producer’s tool-oriented workflows with web search, file search, code interpretation and MCP connections. Describe an available function, let the application execute the requested operation and return its observation before the model develops a follow-up answer. OpenAI also supports a separate image-generation tool in the configured Responses workflow. Images produced by that tool are separate artifacts; the model’s native documented output remains text. Search and tool use are configured activities, rather than evidence that every reply consulted current information.
Predicted Outputs supports regenerating a largely known document or code file with a small change. Provide the previous content and the precise edit, then compare the resulting artifact with that request. The prediction path supports text only and does not combine with function calling; logprobs, max_completion_tokens and several other controls are also excluded. An ordinary tool-using request is a different path when the reply depends on a fresh lookup or calculation.
OpenAI documents fine-tuning for this model and describes using a larger model’s outputs to teach a smaller GPT-4o Mini model a specialised task. This distillation workflow produces a customised model; it does not change the identity of a normal Mini response. For an ordinary request, establish the task and output format with clear examples, then use a focused follow-up to revise the same result. A useful final artifact remains connected to the source facts, the intended reader and the application step that consumes it.
POST /v1/batchestexttext| Field | Type | Requirement | Values & limits | Default |
|---|---|---|---|---|
Fieldendpoint | Typestring | RequirementRequired | Values & limits /v1/chat/completions | Default— |
Fieldmodel | Typestring | RequirementRequired | Values & limits openai/gpt-4o-mini:batch | Default— |
Fieldrequests | Typebatch_item[] | RequirementRequired | Values & limits Minimum items: 1 | Default— |
Fieldrequests[].custom_id | Typestring | RequirementRequired | Values & limits | Default— |
Fieldrequests[].body.messages | Typemessage[] | RequirementRequired | Values & limits | Default— |
Fieldcompletion_window | Typestring | RequirementOptional | Values & limits 24h | Default— |
Fieldprovider | Typeobject|null | RequirementOptional | Values & limits | Default— |
Fieldrequests[].body.model | Typestring | RequirementOptional | Values & limits openai/gpt-4o-mini:batch, openai/gpt-4o-mini | Default— |
Fieldprovider.only | Typestring[] | RequirementOptional | Values & limits openai | Default— |
Fieldprovider.allow_fallbacks | Typeboolean|null | RequirementOptional | Values & limits false, null | Default— |
| Parameter | Contract |
|---|---|
Parametercontent_type | Contractapplication/json |
Parameterrequired | Contractendpoint, model, requests |
Parametermaterial_types | Contracttext |
Parameterrepresentation | Contractinline requests[]; each item has custom_id and body |
Parameterrequest_endpoint_profile | Contract/v1/chat/completions |
Parameterfile_material | ContractCaller 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_order | Contractendpoint, model, provider (if supplied), completion_window (if supplied), requests last |
Parameteroptional_controls | Contractprovider.only, provider.allow_fallbacks, completion_window |
Parameterschema_scope | ContractText 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
Tariff references do not add request options. Supported parameters are listed for the selected method.
Match each charge to the conditions shown. Use one rate for each set of alternative configurations.
| Configuration | Rate schedule | Context tokens, more than | Context tokens, up to and including | Charge |
|---|---|---|---|---|
| ConfigurationBase token rates | Rate scheduleBase rate | Context tokens, more than— | Context tokens, up to and includingNo upper bound | Charge Input · Input tokens $0.00015 / 1K tokens Output · Output tokens $0.0006 / 1K tokens Input · Cache read $0.000075 / 1K tokens Input · Cache write — / 1K tokens Input · Cache write, 1 hour — / 1K tokens |
| ConfigurationRequest-length tier 1 | Rate schedule— | Context tokens, more than0 | Context tokens, up to and includingNo upper bound | Charge Input · Input tokens $0.00015 / 1K tokens Output · Output tokens $0.0006 / 1K tokens Input · Cache read $0.000075 / 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 →
set -eu\n: "${AILOOT_API_KEY:?Set your Ailoot API key}"\npython3 - <<'PY_REQUEST'\nimport json\nfrom pathlib import Path\nbody=json.loads('{"endpoint":"/v1/chat/completions","model":"openai/gpt-4o-mini:batch","requests":[{"custom_id":"req-0001","body":{"messages":[{"role":"user","content":"Hello!"}],"max_tokens":16}}]}')\nPath("batch-request.json").write_text(json.dumps(body,ensure_ascii=False),encoding="utf-8")\nPY_REQUEST\ncurl --fail-with-body --silent --show-error https://api.ailoot.ai/v1/batches \\\n -H "Authorization: Bearer $AILOOT_API_KEY" -H 'Content-Type: application/json' \\\n --data-binary @batch-request.json -D batch-response-headers.txt -o batch-create-response.json\nimport json, os\nfrom pathlib import Path\nfrom urllib.request import Request, urlopen\n\ndef prepare_requests(customer_path):\n path = Path(customer_path)\n if not path.is_file(): raise ValueError("Customer JSONL file is missing")\n items = [json.loads(line) for line in path.read_text(encoding="utf-8").splitlines() if line.strip()]\n if not items: raise ValueError("Customer JSONL contains no requests")\n ids = set()\n for item in items:\n if set(item) != {"custom_id", "body"}: raise ValueError("Each item needs custom_id and body")\n cid = item["custom_id"]\n if not isinstance(cid, str) or not cid.strip() or cid in ids: raise ValueError("custom_id must be nonempty and unique")\n ids.add(cid)\n if not isinstance(item["body"], dict) or not item["body"].get("messages"): raise ValueError("Supply actual text messages")\n supplied_model = item["body"].get("model")\n if supplied_model is not None and supplied_model not in ['openai/gpt-4o-mini:batch', 'openai/gpt-4o-mini']: raise ValueError("body.model must be an exact documented caller or wire ID")\n return {"endpoint":"/v1/chat/completions", "model":"openai/gpt-4o-mini:batch", "requests":items}\n\nif __name__ == "__main__":\n material = os.environ.get("AILOOT_BATCH_REQUESTS_JSONL", "")\n if not material: raise SystemExit("Set AILOOT_BATCH_REQUESTS_JSONL to your actual customer file")\n body = prepare_requests(material)\n key = os.environ.get("AILOOT_API_KEY", "")\n if not key: raise SystemExit("Set AILOOT_API_KEY")\n 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")\n with urlopen(request) as response:\n raw = response.read()\n Path("batch-create-response.json").write_bytes(raw)\n print(raw.decode("utf-8"))\nimport json\nfrom pathlib import Path\nraw = Path("batch-status-response.json").read_bytes()\nresponse = json.loads(raw)\nif response.get("status") != "completed":\n raise SystemExit("Keep the original operation; read its status without resubmitting")\nresults = response.get("results")\nif not isinstance(results, list) or not results:\n raise SystemExit("Preserve the original response; completed results are missing")\nPath("batch-results.jsonl").write_text("".join(json.dumps(item, ensure_ascii=False) + "\\n" for item in results), encoding="utf-8")\n# Preserve batch-status-response.json with aggregate usage and every result/error.\ninline results[].response.body JSON
GET /v1/batches/{operation_id}set -eu\n: "${AILOOT_API_KEY:?Set your Ailoot API key}"\nBATCH_OPERATION_ID="$(python3 - <<'PY_ID'\nimport json\nfrom pathlib import Path\nfrom urllib.parse import quote\nresponse = json.loads(Path("batch-create-response.json").read_text(encoding="utf-8"))\noperation = response.get("id")\nif not isinstance(operation, str) or not operation: raise SystemExit("No actual original operation ID; preserve the response and do not resubmit")\nprint(quote(operation, safe=""))\nPY_ID\n)"\ncurl --fail-with-body --silent --show-error "https://api.ailoot.ai/v1/batches/$BATCH_OPERATION_ID" \\\n -H "Authorization: Bearer $AILOOT_API_KEY" -o batch-status-response.json\nKeep 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.
Preserve the original operation ID. 503 result_pending_check has X-Should-Retry:false; never resubmit an unknown original batch.
| Field | Type |
|---|---|
Fieldresults[].custom_id | Typestring |
Fieldresults[].response.body.choices[].message.content | Typestring|null |
Fieldresults[].error | Typeobject|null |
Fieldusage | Typeobject|null |
Fieldid | Typestring |
Fieldmodel | Typestring |
Fieldendpoint | Typestring |
Fieldstatus | Typestring |
Fieldrequest_counts | Typeobject |
Fieldresults[].id | Typestring |
Fieldresults[].response.status_code | Typeinteger |
Fieldresults[].response.request_id | Typestring |
| Response | Condition | Next step |
|---|---|---|
Response400 · invalid_request_error | ConditionInvalid documented inline envelope, duplicate keys, item identity, or configured model capabilities conflict. | Next stepCorrect the indicated fields before any new submission. |
Response401 · authentication_error | ConditionInvalid API key. | Next stepUse the authorized Ailoot key. |
Response403 · permission_error | ConditionBatch group unavailable. | Next stepCheck key/group entitlement. |
Response422 · invalid_request_error | ConditionBatch uses balance billing; subscription creation is rejected. | Next stepUse the authorized balance-billed group. |
Response422 · price_unavailable | ConditionBatch input cannot be quoted. | Next stepPreserve response; use documented family input. |
Response402 · billing_error | ConditionBatch reserve unavailable. | Next stepResolve admission before a new request. |
Response503 · price_unavailable | ConditionBatch method price/native rates unavailable. | Next stepPreserve response; do not substitute prices. |
Response503 · api_error | ConditionExact supplier route unavailable. | Next stepPreserve response for route repair. |
Response503 · result_pending_check | ConditionOriginal result requires checking; X-Should-Retry:false. | Next stepKeep original operation_id/id and read its status; never repeat original POST. |
Response404 · not_found | ConditionBatch status operation absent or owned by another identity. | Next stepUse exact original id and same user/key/group. |
Ailoot Ultra openai/gpt-4o-mini:batch
Use the method paths shown above.