API Anthropic Messages

Anthropic Messages API

Use a Messages-format request with a separately qualified inference engine. This is not an assertion that the Panel gateway implements the engine's Messages endpoint.

1. Open API workbench (/rust/api) and select POST /v1/messages in Endpoint catalog.
2. Open its entry under Browse every endpoint (generated from route registration); administrators can also press Generate examples. The workbench labels the route Engine-only and uses ENGINE_URL, not PANEL_URL. Set ENGINE_URL to the protected URL of an engine that explicitly reports Messages compatibility.
3. Substitute a model ID admitted by that engine and a credential configured for that engine. Do not reuse a Panel token unless that engine was explicitly configured to accept it.
4. Send the request with a user message and max_tokens; inspect the actual response. POST /v1/messages/count_tokens is another engine-only operation and must also be qualified before use.

Example request body:

{"model":"MODEL_ID","max_tokens":128,"messages":[{"role":"user","content":"Hello"}]}

If the engine is not present, qualified, or listening, the correct result is unavailable or refused; Panel OpenAPI registration is not evidence of engine readiness. The guarded In-page tester does not issue engine-only requests. See Panel API and Compatible clients.

Control reference

Control	Help text
Messages (api.messages)	Use the separate engine Messages route only when the active engine declares support.