v1Stable
Traces provide complete visibility into Apollo-1’s symbolic reasoning: intents parsed, entities resolved, rules evaluated, parameters extracted, and decisions made. Every interaction produces a trace that records the computation in full.
Get All Task Traces
Retrieve traces for all interactions in a conversation thread.cURL
GET /v1/messaging/tasks/{task_id}/trace-info
Base URL: https://api.aui.io
Headers
| Header | Required | Description |
|---|---|---|
x-aui-api-key | Yes | Your API key |
Path Parameters
The task identifier (conversation thread).
Response
Returns an array of trace objects, one per interaction in the thread. Each trace contains:The interaction identifier (same as message ID).
The parsed user intent from the message.
Entities extracted and resolved from the conversation.
Parameters collected during this interaction.
All rules that were evaluated, including:
Tools the agent considered invoking for this interaction.
Tools that were actually called, including parameters passed.
The final decision made by the agent (e.g., “proceed”, “block_with_explanation”, “request_confirmation”).
Get Single Interaction Trace
Retrieve the trace for a specific interaction.cURL
GET /v1/messaging/tasks/{task_id}/interactions/{interaction_id}/trace-info
Path Parameters
The task identifier.
The interaction/message identifier to trace.
Response
Returns a single trace object (same structure as above) for the specified interaction.Code Examples
Understanding Traces
White-Box Traceability
Every turn produces a trace that records the symbolic computation in full. Apollo-1’s trace is not a generated explanation—it’s the actual computation, recorded as it happens. The runtime cannot decide one thing and trace another, because the decision and the trace are the same object.Trace Components
Intent Parsing: How the user’s message was interpreted and mapped to a symbolic intent. Entity Resolution: What values were extracted from the conversation and how they map to your domain entities. Rule Evaluation: Which predicates fired, which blocked actions, and why. Evaluation is deterministic—given the same state, the same rules fire the same way. Parameter Extraction: What information was collected to fulfill the request. Tool Invocation: Which tools were considered, which were called, with what parameters, and what they returned. Decision: The final action taken by the agent based on the symbolic computation.Debugging with Traces
Traces let you diagnose failures to the exact point where perception diverged from intent:- Misclassified intent: The agent understood a different intent than the user meant
- Missing entity: A required value wasn’t extracted from the conversation
- Rule blocked action: A predicate evaluated false and prevented the tool call
- Tool failure: A tool was invoked but returned an error
Errors
| Status | Description |
|---|---|
401 | Missing or invalid x-aui-api-key header |
404 | Task or interaction not found |
403 | Insufficient permissions for the specified agent |
401
404
