API Reference

Anthropic Messages

Anthropic Messages

POST https://api.tu-zi.com/v1/messages
Preview guide

Paste into an AI assistant to help with integration. Documentation and examples only; no real credentials.

Preview guide

Anthropic Messages

Updated · Reviewed

Endpoint and authentication

POST https://api.tu-zi.com/v1/messages

Transport: json

Use an inference API key. Examples contain placeholders; read credentials from environment variables.

Authorization: Bearer YOUR_API_KEY
anthropic-version: 2023-06-01
Content-Type: application/json

Minimal request example

{
  "model": "YOUR_MODEL",
  "max_tokens": 512,
  "messages": [
    {
      "role": "user",
      "content": "Hello"
    }
  ]
}

Before running

Replace https://api.tu-zi.com with this site origin (do not append /v1 twice), and YOUR_MODEL with the exact marketplace model ID. Install requests for Python; use Node.js 20+ and save JavaScript as .mjs. WebSocket samples list their own dependencies.

Create an inference key on the site and set API_KEY in the environment; replace YOUR_API_KEY in cURL. Prepare local input.png/input.wav files for upload examples.

Start with a minimal request, then read the result using the response fields below. For async APIs, a returned task ID requires polling; acceptance does not mean generation has finished.

Constraints

This page describes the base protocol. Use the selected model quick start for supported fields, enums, limits and asynchronous behavior. Replace YOUR_MODEL. Form initial values are not upstream defaults.

Body parameters

FieldTypeRequiredDescription / constraints
modelstringYesModel name to call. Example: claude-3-7-sonnet
max_tokensnumberYesRequired explicit Anthropic output token limit. Small limits can truncate output; larger limits may increase maximum time and cost without forcing longer output. Form initial value (not an upstream default): 512 Range in this definition: 1 ~ 128000 Example: 512
messagesarrayYesConversation messages; content supports structured text blocks and other supported block types. Example: [{"role":"user","content":"你好"}]
streambooleanNoWhether to enable streaming responses. Form initial value (not an upstream default): false Example: false
temperaturenumberNoSampling temperature between 0 and 1. Form initial value (not an upstream default): 0.7 Range in this definition: 0 ~ 1 Example: 0.7
top_pnumberNoNucleus sampling probability threshold. Form initial value (not an upstream default): 1 Range in this definition: 0 ~ 1 Example: 0.9
top_knumberNoSample only from the K most probable tokens. Range in this definition: 1 ~ 500 Example: 40
messages[].rolestringNouser or assistant. System instructions belong in top-level system.
messages[].contentstring | arrayNoText or text/image/tool_use/tool_result blocks.
toolsarrayNoTool definitions contain name, description and input_schema.

Response fields

FieldTypeDescription / constraints
content[]objectContent blocks such as text and tool_use.
stop_reasonstringStop reason.
usageobjectinput_tokens and output_tokens.

Illustrative response; some endpoints show essential fields only. Optional fields may be absent.

{
  "id": "msg_example",
  "type": "message",
  "role": "assistant",
  "content": [
    {
      "type": "text",
      "text": "Hello"
    }
  ],
  "stop_reason": "end_turn",
  "usage": {
    "input_tokens": 5,
    "output_tokens": 1
  }
}

Streaming

With stream=true handle message_start, content_block_delta, message_delta and message_stop SSE events.

Errors and retries

Check HTTP status and protocol-specific errors; do not mix error formats across protocols. For 401/403 check credentials and permissions, for 429 back off, and for 5xx check gateway/upstream status. Error bodies may contain error/message/code depending on the protocol.

Use bounded exponential backoff for reads. Do not blindly retry task creation, generation, or key mutations, to avoid duplicate billing or execution.