prompt, get an AI response. A single endpoint serves every mode and feature, so you can start simple and layer in capabilities as you need them.
This page is a guided tour. For the full request and response schema, see the Converse API reference.
Your first call
content is an array; the text of the reply is at content[0].text.
Use an agent
To run a configured agent, pass itsagent_id. The agent’s instructions, knowledge, and tools are applied automatically.
config object lets you override an agent’s settings for a single turn without changing the stored agent. See Getting started with Agents for the full create-and-run flow.
Choose a mode
Converse can answer with a fast LLM-first response, a lighter search-backed agent, or a full multi-step agent. You select this withchat_mode (and config.agent_model):
See Converse modes for the full mapping between
chat_mode, config.agent_model, and which tools each mode allows.
Scope knowledge with corpus
By default the agent can use all knowledge in scope. Passconfig.corpus to limit a request to specific knowledge bases or pages.
Stream responses
Setstream: true to receive the response incrementally as server-sent events — useful for responsive UIs on longer answers.
start, delta, end).
Get structured output
Pass a JSON Schema intext.format to guarantee the response matches a schema. This works for every mode.
Add file inputs
Upload a file, then reference it in a structured prompt to ask questions about documents, PDFs, or images.Continue a conversation
Pass aconversation_id to keep context across turns. The first call returns one (or you can create one explicitly via the Conversations API).
More capabilities
- MCP servers — connect external tools via the Model Context Protocol (Beta).
- Rate limits — limits, headers, and retry guidance.
Next steps
- Getting started with Agents — create reusable agents to run via Converse.
- Converse modes — pick the right mode for each task.