Claude Opus 5
Review the preregistered Claude Opus 5 model IDs, endpoint, launch pricing, and availability in HopsAPI.
Claude Opus 5 is preregistered in the HopsAPI catalog before its upstream channels are connected. This page documents the prepared gateway configuration only; it does not claim that the upstream model is currently callable.
Model information
| Item | Value |
|---|---|
| Protocol | Anthropic Messages |
| Endpoint | POST /v1/messages |
| Availability | Hidden by default; upstream pending |
| Initial pricing | $5 input / $25 output per 1M tokens |
Model IDs
| Model ID | Channel |
|---|---|
claude-opus-5 | Use this ID when returned by the current API key's model list |
The model remains hidden and its upstreams are not connected yet. Do not send production requests
until GET /v1/models returns the ID for your API key.
Prepared request shape
Once an ID is enabled, it uses the native Anthropic Messages request shape:
curl https://hopsapi.com/v1/messages \
-H "x-api-key: sk-YOUR_KEY" \
-H "anthropic-version: 2023-06-01" \
-H "content-type: application/json" \
-d '{"model":"claude-opus-5","max_tokens":512,
"messages":[{"role":"user","content":"Introduce this model in one sentence."}]}'The example is configuration guidance only and is not a successful-call guarantee while the upstream remains pending. See Anthropic format for the native protocol rules.
Start a new conversation when switching to Opus 5 from another Claude model or channel because
historical thinking.signature values cannot be reused across models or channels. The Gateway
removes historical thinking blocks and retries once only after the upstream explicitly rejects the
signature.