Test an agent
Run the agent’s prompt, model and knowledge base against a message and return the reply instead of delivering it. Writes nothing and charges nothing, so it is safe to call repeatedly while iterating on a prompt.
Note that this exercises the text path, which does not offer tools to the model. When the agent has enabled tools, that is reported in warnings rather than silently producing an answer that looks like a tool call happened.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Agent ID.
Body
Run the agent and return what it would say. Nothing is delivered to anyone, no execution is recorded, and nothing is charged.
What to say to the agent.
"Where is order ORD-12345?"
Prior turns, oldest first, to exercise multi-turn behaviour without persisting a thread. Trimmed to the agent's context window.
Set false to skip retrieval and isolate prompt behaviour from the knowledge base.
Response
The agent's reply.
What the agent would reply.
Knowledge-base chunks retrieved for this message. Zero means the answer was not grounded in your documents.
Things that are true of this agent but that a dry run cannot prove: the agent being disabled, enabled tools that its channels will never call (the text path does not offer tools to the model), and contact metadata that exists on a real conversation but not here. Surfaced so a passing dry run is never mistaken for proof that the agent works live.
