Batches.

Two flavors, one lifecycle

Collection	Item params	Auth header
`/v1/messages/batches`	Anthropic Messages bodies	`x-api-key`
`/v1/batches`	OpenAI Chat Completions bodies	`Authorization: Bearer`

Both collections expose the same five operations. Everything below is written against /v1/messages/batches; substitute the path and item shape for the OpenAI flavor.

Create a batch

POST /v1/messages/batches

Send an inline requests array. Each item carries a custom_id (yours, for matching results) and a params object — the same body you would send to the live endpoint.

Create

curl https://api.layerx1.com/v1/messages/batches \
  -H "x-api-key: $LAYERX1_API_KEY" \
  -H "content-type: application/json" \
  -d '{
    "requests": [
      {
        "custom_id": "req-1",
        "params": {
          "model": "lx1-gpt-oss-120b",
          "max_tokens": 256,
          "messages": [{ "role": "user", "content": "First task" }]
        }
      },
      {
        "custom_id": "req-2",
        "params": {
          "model": "lx1-gpt-oss-120b",
          "max_tokens": 256,
          "messages": [{ "role": "user", "content": "Second task" }]
        }
      }
    ]
  }'

Limit	Value
Requests per batch	1,000
Size per item	100 KB

Lifecycle

GET  /v1/messages/batches
GET  /v1/messages/batches/{id}
POST /v1/messages/batches/{id}/cancel
GET  /v1/messages/batches/{id}/results

Processing is asynchronous. processing_status flows in_progress → ended (via canceling if you cancel). Poll the status endpoint; fetch /results only once the batch has ended — before that it returns 409.

Results

Results are JSONL — one line per request, keyed by your custom_id, with a discriminated result.type of succeeded | errored | canceled | expired. Order is not guaranteed to match submission order; always match on custom_id.

Results (JSONL, one line per request)

{"custom_id":"req-1","result":{"type":"succeeded","message":{"id":"msg_...","content":[{"type":"text","text":"..."}]}}}
{"custom_id":"req-2","result":{"type":"errored","error":{"type":"invalid_request_error","message":"..."}}}

Batch items draw from the same monthly included-usage pool as live requests, at the same public list rates — see Plans & limits.

Get started

API reference

Agent-native API

Guides

Reference

Two flavors, one lifecycle

Create a batch

Lifecycle

Results

​Two flavors, one lifecycle

​Create a batch

​Lifecycle

​Results

Two flavors, one lifecycle

Create a batch

Lifecycle

Results