Submit traces for evaluation
Scores one or more prompt/response traces against the monitoring configuration on the application.
Prerequisites: monitoring must include at least one metric or security plugin (PUT /applications/{applicationId}/monitoring).
Trace payload: each trace includes prompt and response strings. Optional trusys metadata supports agentic flows (tool_calls, agent_calls, plan) and retrieval-augmented flows (query, context).
Single vs batch: pass traces as one object or an array. For a single trace, the response data is one object; for a batch, data is an array.
Trace IDs: supply traceId (string) to correlate with your own logging, or omit it and one is generated automatically.
Authorizations
Your Trusys API key. Create and manage keys in the Trusys UI under Settings → API Keys.
Include the key on every request:
x-api-key: <your-api-key>Path Parameters
Unique identifier (UUID) of the application. Returned by POST /applications.
Body
One trace or an array of traces to evaluate.
One trace object or a non-empty array of traces.
- object
- object[]