AI Agent Orchestration Platform  ·  View 17 of 32  ·  4 · Runtime

Execute an Agent

One synchronous run end to end, including the tool hop and the point at which the result becomes final.

Editable source SVG draw.io All views
Caller API Management Admission Service Durable Orchestrator Runtime Worker AI Gateway Tool Broker Execution Store 1. POST /v1/executions 2. verify token, scope 3. submit run 4. pin versions, evaluate policy 5. 429 budget exhausted 6. start orchestration 7. checkpoint: admitted 8. dispatch step 9. assemble context, guard input 10. chat completion, stream 11. token stream 12. tool call requested 13. invoke with idempotency key 14. tool result 15. continue with result 16. final answer 17. guard output, enforce schema 18. checkpoint: completed 19. 200 result and cost Execute an Agent — Critical Flow with Streaming Tokens stream from the gateway to the caller while the run is still open. The result is not final until the checkpoint commits. v 1.0 · owner Runtime Engineering · date 2026-08

Decisions

  • Admission is where a run can be refused: over budget, policy denied or a pinned version that no longer resolves
  • Tokens stream to the caller from the gateway while the run is open, so perceived latency is model latency, not orchestration latency
  • The result is not final until the completion checkpoint commits — a response acknowledged before that would be a lie under crash

Timing budget

  • Edge to admission decision p95 under 60 ms; admission to first dispatch p95 under 60 ms
  • First token to the caller p95 under 900 ms end to end for an interactive agent
  • Tool hop budget 5 s default, declared per tool and enforced by the executor

Not shown

  • The asynchronous submission path, where the caller receives an execution id and polls or subscribes
  • Multi-agent delegation — see Multi-Agent Coordination
  • Failure and retry — see Durable Execution