Model card

Claude Opus 4.6

lx1-opus-4.6FrontierPro planLive in the catalog

Opus-class reasoning with a million-token context at the standard Opus card. Use it when the prompt is huge and the judgment has to be Opus.

Context window1M tokens

Input · per Mtok$5

Output · per Mtok$25

Served byLayer X1 engine

Where it earns its keep[01/03]

011M-token Opus context
02Frontier reasoning
03Vision and tools

Capabilities

Tool callingYes

Strict, schema-faithful tool calls, enforced by the engine on every request — safe to build an agent loop on.

ReasoningYes

Thinks before it answers. Budget max_tokens generously — hidden reasoning counts against it.

VisionYes

Reads images — screenshots, diagrams, and UI states — inline in the conversation.

Behind the endpoint[02/03]

One endpoint. Served by our engine.

Claude Opus 4.6 is served through the Layer X1 engine — zero-downtime serving is the design target, not a status-page apology. You request it by name; everything else is our problem.

Call it by name

curl https://api.layerx1.com/v1/messages \
  -H "x-api-key: lx1_your_key" \
  -H "content-type: application/json" \
  -d '{
    "model": "lx1-opus-4.6",
    "max_tokens": 1024,
    "messages": [{ "role": "user", "content": "Hello" }]
  }'

OpenAI-style clients work too — send the same model name to /v1/chat/completions with a Bearer key. See the docs for both dialects.

Your agent stays the same.
Its inference gets better.

$export ANTHROPIC_BASE_URL=https://api.layerx1.com

Get a key Read the docs

Start free · no card · Launch from $2/mo

One endpoint. Served by our engine.

Your agent stays the same.Its inference gets better.

Your agent stays the same.
Its inference gets better.