Responses API.
Stay on Messages API if your current Anthropic-compatible tooling already works well and compatibility matters more than a cleaner default surface.
Mental Model Shift
| Messages | Responses |
|---|---|
| content blocks | typed input/output items |
tool_use | function_call |
tool_result | function_call_output |
message_start / content_block_delta | semantic Responses events |
| thinking blocks | reasoning items |
| repeated message history | input replay or previous_response_id |
When To Stay On Messages
- your app already depends on Anthropic SDK behavior
- your tooling expects content blocks directly
- migration cost is higher than the near-term benefit
When To Migrate
- you want the recommended primary NagaAI LLM surface
- you are starting a new app or redesigning your current one
- you want one docs path for new feature work
Field mapping
| Messages field or concept | Responses equivalent |
|---|---|
system | instructions or a system / developer input message |
| user text block | input_text |
| image block | input_image |
| document block | input_file |
tool_use block | function_call |
tool_result block | function_call_output |
| thinking block | reasoning item |
Simple request conversion
Messages
Responses
Tool and reasoning notes
- Anthropic
tool_useandtool_resultblocks map tofunction_callandfunction_call_output - visible thinking maps to
reasoningitems and Responses reasoning events - if you preserve reasoning continuity across turns, replay reasoning payloads unchanged