Use one configuration
OpenAI and Anthropic profiles for the same model can declare different capabilities. Tools, structured output, modalities and budgets must come from the same profile, not a union across configurations. Model details list current parameters.
Tool calling
A tool call is a proposed operation. Your application checks its name, arguments and authorization, executes the permitted action, and returns the result.
These are tool-definition fragments, not complete requests.
OpenAI format:
{"tools":[{"type":"function","function":{"name":"lookup_weather","description":"Look up weather for a city","parameters":{"type":"object","properties":{"city":{"type":"string"}},"required":["city"]}}}]}Anthropic format:
{"tools":[{"name":"lookup_weather","description":"Look up weather for a city","input_schema":{"type":"object","properties":{"city":{"type":"string"}},"required":["city"]}}]}| Stage | OpenAI | Anthropic |
|---|---|---|
| Requested call | message.tool_calls | tool_use blocks in content |
| Arguments | JSON string in function.arguments | input object |
| Result association | role=tool and original tool_call_id | tool_result and original tool_use_id |
Streaming tool arguments can arrive in fragments. Assemble them by call ID/index before execution; do not execute each delta. A playground display of tool output does not mean it executes your external tools.
Structured output
Use this only when the profile declares support and lists the required parameters. Do not send OpenAI response_format unchanged to Anthropic. Without a published JSON Schema subset, strict mode or guarantee for the integration, no universal guarantee is implied. Consult the model’s API reference.
Inspect stop reasons and errors. Truncation, refusal or interrupted delivery is not complete JSON. Allow enough output budget for the expected structure.
Image input and caching
An image input modality is not image-generation support. Message blocks, size limits and transports depend on protocol and model; do not invent unpublished limits.
See billing for cache metering. Vendor explicit-cache controls are not automatically supported by the platform. The current DashScope adapter uses implicit caching; vendor cache_control promises do not carry over automatically.