Initiates an AI orchestration execution. The orchestration engine tracks every step, LLM inference call, tool invocation, and decision point — producing a complete, transparency-log-anchored audit trail. Orchestrations are the primary unit of AI agent work in MAIP. They capture the full lifecycle of an agent’s reasoning and actions, enabling compliance teams to audit what the agent did, why it did it, and what data it consumed.Documentation Index
Fetch the complete documentation index at: https://docs.truthlocks.com/llms.txt
Use this file to discover all available pages before exploring further.
Authentication
API key with
orchestrations:write scope. Alternatively, pass a Bearer JWT
token in the Authorization header.Tenant identifier for multi-tenant isolation.
Request
MAIP agent identifier executing the orchestration.
Optional workflow definition identifier. If provided, the orchestration
follows the workflow’s DAG of steps.
Input data for the orchestration. Schema depends on the workflow definition or
agent’s expected input format.
Default LLM model identifier to use for inference steps (e.g.
claude-sonnet-4-20250514, gpt-4o). Individual steps may override this.Maximum number of steps the orchestration may execute before automatic
termination. Defaults to
10.Maximum wall-clock duration in seconds before the orchestration is timed out.
Defaults to
300 (5 minutes).Response
Unique orchestration identifier in MAIP format (
maip-orch:ULID).The agent executing the orchestration.
The workflow definition identifier, if provided.
Execution status. Always
running on creation.ISO 8601 timestamp when execution began.

