Explorer

Explorer is your window into production traffic.

It lets you search, filter, and inspect every chat completion event flowing through your Workspace.

i
Information

Explorer is restricted to Workspace administrators.

What you can do

What you can do

  • Search and filter events by model, tool usage, message content, latency, etc.
  • Inspect any conversation records (messages, tool calls, and metadata).
  • Export filtered events to Datasets.
  • Automate by creating Judges and Campaigns directly from your filter results.
Filter language

Filter language

Explorer supports a structured filter language.

You write conditions on event fields and combine them with AND, OR, and parentheses.

Available operators

OperatorMeaningExample
=Equalsmodel_name = "mistral-medium-2508"
!=Not equalsmodel_name != "mistral-medium-2508"
containsSubstring matchmodel_name contains "large"
includesList contains valueinvoked_tools includes "web_search"
excludesList doesn't include valueinvoked_tools excludes "web_search"
>Greater thantotal_time_elapsed > 5
<Less thantotal_time_elapsed < 2
>=Greater than or equaltotal_time_elapsed >= 5
<=Less than or equaltotal_time_elapsed <= 2
isnullIs nullapi_agent_id isnull False
length_equalsList length equalsinvoked_tools length_equals 3
starts_withStarts with substringmodel_name startswith "mistral-med"
ends_withEnds with substringmodel_name endswith "-2508"
matchesRegex matchmodel_name matches ".+-8b-.+"

Examples

Filter by model and tool usage:

model_name = "mistral-medium-2508" AND invoked_tools includes "web_search"

Filter by model family with code output:

(model_name contains "large" OR model_name contains "small") AND invoked_tools includes "code_interpreter"

Filter by response time:

total_time_elapsed > 5

Combine multiple conditions:

model_name = "mistral-large" AND total_time_elapsed > 5 AND (last_user_message_preview contains "password" OR response_messages_preview contains "error")
tip

Use the autocomplete dropdown to select from the suggested fields and values as you type.

Query design tips

  1. Start broad with a time range, then narrow down.
  2. Add one business-relevant condition (e.g., a specific tool, feature, or model).
  3. Add one technical condition (e.g., latency, message content, or specific tools).
  4. Scan a few results before exporting. Make sure the sample is relevant.
Inspect events

Inspect events

Click any event in the results list to see the full detail view. Each event includes:

  • A feed of messages, including the full conversation (user inputs, assistant responses, and system prompts).
  • A list of properties (model name, token counts, computation duration, and any tools invoked by the model).
Export to a Dataset

Export to a Dataset

Once you've filtered to a useful set of events, you can export them to a Dataset.

  1. Select one or more events using the checkboxes
  2. Click Add to dataset.
  3. Choose an existing Dataset or create a new one.

Treat Dataset exports as snapshots. Use descriptive names (e.g., support_web_search_2026_02) and clear descriptions to enable accurate comparisons over time.

tip

Found a useful filter? Reuse it to create a Judge or Campaign directly from the Explorer UI.

[Developer] Use Explorer programmatically

[Developer] Use Explorer programmatically

All Explorer functionality is available via the SDK. Use it to automate searches, build reporting pipelines, or integrate with custom tooling.

FAQ

FAQ