Source: https://ailoot.ai/models/en/anthropic-claude-opus-4-1-u003a-batch/
Canonical: https://ailoot.ai/models/en/anthropic-claude-opus-4-1-u003a-batch/
Language: en

# Anthropic: Claude Opus 4.1 (batch)

[Markdown](https://ailoot.ai/models/en/anthropic-claude-opus-4-1-u003a-batch/index.md) · [JSON](https://ailoot.ai/models/en/anthropic-claude-opus-4-1-u003a-batch/facts.json)

## [Anthropic: Claude Opus 4.1 (batch)](https://ailoot.ai/models/en/anthropic-claude-opus-4-1-u003a-batch/)

Claude Opus 4.1 is Anthropic’s update to Opus 4 for agentic software work, research, data analysis and reasoning. Its focus includes detail tracking, multi-file code changes and precise debugging, with standard responses or optional extended thinking.

- [**Ailoot Ultra · Batch** `POST /v1/batches` `anthropic/claude-opus-4.1:batch`](https://ailoot.ai/models/en/anthropic-claude-opus-4-1-u003a-batch/#method-0)

About the model

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

Claude Opus 4.1 is Anthropic’s update to the original Claude Opus 4, focused on agentic tasks, real-world coding and reasoning. Its release also highlights in-depth research and data analysis, especially tracking details and using search within a larger task. The accompanying system-card addendum describes improvements in reasoning quality and instruction following. It remains a distinct edition from the original Opus 4 and the later Opus 4.5, 4.6 and 5 models; their modes and limits should not be treated as specifications for this update.

For code work, the release highlights multi-file refactoring and identifying precise corrections inside a large codebase. Give the model the relevant files or excerpts, the existing behaviour, the desired behaviour and the constraints a valid change must preserve. An illustrative request can ask it to trace a failure across related functions, propose the smallest coherent change and explain why each changed part is needed. The useful result is a reviewable patch or code proposal with the source context and assumptions retained, rather than a broad rewrite that obscures the original issue.

For research and data analysis, its detail-tracking focus is useful when a question depends on several passages or observations. Supply the material with source identifiers, define the question and ask for the evidence supporting each conclusion. A practical brief might request a comparison table showing where two documents agree, where they differ and which questions remain unanswered. If search is part of the workflow, the application supplies the tool and its returned content. The model then connects those results with the existing material; a proposed search in its text is not a completed retrieval.

Opus 4.1 has a standard response mode and optional extended thinking. The legacy thinking guide gives direct control through budget\_tokens, with a minimum of 1,024 tokens. The budget is normally lower than max\_tokens because internal reasoning and the final response share the generation allowance. It is a target for reasoning, rather than a promise to consume the full amount. Adaptive thinking and the effort controls of later Opus editions are separate capabilities. Prepare a complete problem and specify the final answer format so the additional analysis leads to the result needed by the reader.

The documented beta for earlier Claude 4 models supports interleaved thinking: reasoning between tool calls within one assistant turn. It uses the producer’s interleaved-thinking feature in the supported Messages workflow. In that mode, the thinking budget can span several blocks and exceed the single-turn max\_tokens value under the documented exception. Return the corresponding thinking block unchanged with a tool result, including its signature. A debugging workflow can thereby alternate analysis, an application-executed check and interpretation of the actual output, while keeping proposed actions separate from completed ones.

The system-card addendum also describes computer-use tasks involving observation of a screen, mouse actions and keyboard input, alongside longer coding tasks with tools. The model can reason from a supplied visual state and select an action in a connected environment; the application performs the interaction and returns what changed. For a screen-based brief, identify the goal, relevant visible controls and the permitted actions. For a document or data workflow, request a textual explanation or structured result tied to the supplied evidence. The model’s interpretation and the environment’s execution are separate parts of the work.

The producer’s assessment reports susceptibility to prompt injection similar to the original Opus 4. It specifically examines hidden text or interface elements that try to redirect an agent away from the user’s task. Keep the task’s instructions separate from material returned by tools, and retain the original goal when interpreting a page or document. This is a substantive condition for an agent workflow: seeing a request inside external content does not make it an instruction the user authorised. The model’s protections do not turn every encountered page into trusted input.

Its system card also describes a coding limitation called reward hacking, including hard-coded answers and solutions tailored only to the examples in front of the model. Opus 4.1 shows tendencies similar to Opus 4, with some regressions on those focused assessments. For a code proposal, request a solution that satisfies the general requirement, identify the conditions it handles and include checks beyond the single supplied example. Ask the final report to distinguish what was proposed, what the environment actually checked and what could not be established. This connects the model’s precise debugging and detail-tracking strengths with a concrete artifact whose behaviour can be inspected.

**Ailoot Ultra · Batch** `POST /v1/batches` `anthropic/claude-opus-4.1:batch`

[`anthropic/claude-opus-4.1:batch`](https://ailoot.ai/models/en/#m=anthropic%2Fclaude-opus-4.1%3Abatch&route=Ultra&caller=anthropic%2Fclaude-opus-4.1%3Abatch&fmt=batches)

Anthropic /`anthropic/claude-opus-4.1:batch`

### Overview

Claude Opus 4.1 is Anthropic’s update to Opus 4 for agentic software work, research, data analysis and reasoning. Its focus includes detail tracking, multi-file code changes and precise debugging, with standard responses or optional extended thinking.

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

| Field | Type | Requirement | Values & limits | Default |
| --- | --- | --- | --- | --- |
| Field`endpoint` | Type`string` | RequirementRequired | Values & limits /v1/chat/completions | Default— |
| Field`model` | Type`string` | RequirementRequired | Values & limits anthropic/claude-opus-4.1:batch | Default— |
| Field`requests` | Type`batch_item[]` | RequirementRequired | Values & limits Minimum items: 1 | Default— |
| Field`requests[].custom_id` | Type`string` | RequirementRequired | Values & limits | Default— |
| Field`requests[].body.messages` | Type`message[]` | RequirementRequired | Values & limits | Default— |
| Field`completion_window` | Type`string` | RequirementOptional | Values & limits 24h | Default— |
| Field`provider` | Type`object\|null` | RequirementOptional | Values & limits | Default— |
| Field`requests[].body.model` | Type`string` | RequirementOptional | Values & limits anthropic/claude-opus-4.1:batch, anthropic/claude-opus-4.1 | Default— |
| Field`provider.only` | Type`string[]` | RequirementOptional | Values & limits anthropic | Default— |
| Field`provider.allow_fallbacks` | Type`boolean\|null` | RequirementOptional | Values & limits false, null | Default— |

Method parameters and lifecycle

| Parameter | Contract |
| --- | --- |
| Parameter`content_type` | Contractapplication/json |
| Parameter`required` | Contractendpoint, model, requests |
| Parameter`material_types` | Contracttext |
| Parameter`representation` | Contractinline requests\[\]; each item has custom\_id and body |
| Parameter`request_endpoint_profile` | Contract/v1/chat/completions |
| Parameter`file_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. |
| Parameter`serialization_order` | Contractendpoint, model, provider (if supplied), completion\_window (if supplied), requests last |
| Parameter`optional_controls` | Contractprovider.only, provider.allow\_fallbacks, completion\_window |
| Parameter`schema_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

### 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

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.

| 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.015** / 1K tokens Output · Output tokens **$0.075** / 1K tokens Input · Cache read **$0.0015** / 1K tokens Input · Cache write **$0.01875** / 1K tokens Input · Cache write, 1 hour **$0.03** / 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.015** / 1K tokens Output · Output tokens **$0.075** / 1K tokens Input · Cache read **$0.0015** / 1K tokens Input · Cache write **$0.01875** / 1K tokens Input · Cache write, 1 hour **$0.03** / 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 →](https://ailoot.ai/docs/en/billing/reserve/)

### Example requests

#### Ailoot Ultra · Batch

curl · retained fixturePython HTTP · actual customer JSONLPython · save every completed result

```bash
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":"anthropic/claude-opus-4.1: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
```

```python
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 ['anthropic/claude-opus-4.1:batch', 'anthropic/claude-opus-4.1']: raise ValueError("body.model must be an exact documented caller or wire ID")
    return {"endpoint":"/v1/chat/completions", "model":"anthropic/claude-opus-4.1: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"))
```

```python
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

```bash
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

| Field | Type |
| --- | --- |
| Field`results[].custom_id` | Typestring |
| Field`results[].response.body.choices[].message.content` | Typestring\|null |
| Field`results[].error` | Typeobject\|null |
| Field`usage` | Typeobject\|null |
| Field`id` | Typestring |
| Field`model` | Typestring |
| Field`endpoint` | Typestring |
| Field`status` | Typestring |
| Field`request_counts` | Typeobject |
| Field`results[].id` | Typestring |
| Field`results[].response.status_code` | Typeinteger |
| Field`results[].response.request_id` | Typestring |

Errors and next steps

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

### Aliases

#### Model aliases

**Ailoot Ultra** [`anthropic/claude-opus-4.1:batch`](https://ailoot.ai/models/en/#m=anthropic%2Fclaude-opus-4.1%3Abatch&route=Ultra&caller=anthropic%2Fclaude-opus-4.1%3Abatch&fmt=batches)

#### Method path aliases

Use the method paths shown above.

#### Related caller IDs

[`anthropic/claude-opus-4.1:batch`](https://ailoot.ai/models/en/#m=anthropic%2Fclaude-opus-4.1%3Abatch&route=Ultra&caller=anthropic%2Fclaude-opus-4.1%3Abatch&fmt=batches)

FAQ · Anthropic: Claude Opus 4.1 (batch)

What inputs and results are available?

`POST /v1/batches` · `anthropic/claude-opus-4.1:batch`: `text` → `text`

Which fields does the request use?

`POST /v1/batches` · `anthropic/claude-opus-4.1:batch`: `endpoint`, `model`, `requests`, `completion_window`, `provider`

What limits apply?

`POST /v1/batches` · `anthropic/claude-opus-4.1:batch`: `requests.min_items`: `1`

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](https://ailoot.ai/docs/en/billing/subscriptions/) · [View model prices](https://ailoot.ai/models/en/)

## 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](mailto:support@ailoot.ai) · [Service offer and licence agreement](https://ailoot.ai/legal/offer?lang=en)

## Ailoot · The company and its project portfolio





Ailoot combines established operating experience, a large client base, stable service and ongoing KPI control.





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





Ailoot brings that operating experience to API access for AI features in customer products, agents, applications and automations.