Skip to main content
Call Step models using an Anthropic Messages API-compatible format, with support for streaming, tool calls, image input, and reasoning effort configuration.

Endpoint

Claude Code and the Anthropic SDK use the configuration Base URL and append /v1/messages. Use the full request URL with curl. For tool setup, see the Claude Code integration guide.

Request Parameters

The request supports the following top-level fields:

Message Content Format

The content field of each entry in messages accepts plain text (a string) or an array of the following content blocks:

step-router-v1 Field Restrictions

step-router-v1 is available only through Step Plan and routes between deepseek-v4-pro and step-3.7-flash. The restrictions below apply only to this model; other fields follow the request parameters above.

Response

Non-streaming response

Content-Type: application/json

Response Fields

Streaming response

Content-Type: text/event-stream Streaming uses standard SSE format. Each event has an event: line and a data: line; data: is JSON. Common event types: message_start, content_block_start, content_block_delta, content_block_stop, message_delta, message_stop, ping. When streaming tool-call arguments, content_block_delta.delta.type may be input_json_delta.

Examples

Replace YOUR_STEP_API_KEY with your key. Set STEP_API_KEY before running examples that use the environment variable, then select the standard API or Step Plan tab for your channel.