MOmoda-dev

Search traces

Searches and filters traces by text, cluster, user, time range, environment, world-state keywords, and outcome.

get/api/v1/data/conversations

Request

  • Base URL
    https://moda.dev
  • Auth
    API key in header x-api-key

Query parameters

searchstring

Full-text search term for trace summaries.

cluster_idstring

Filter by cluster node ID.

user_idstring

Filter by user ID.

time_range'all' | '1h' | '24h' | '3d' | '7d' | '30d' | '90d'
sincestring

Absolute start, inclusive (ISO 8601 date or datetime, UTC). Lists traces active during the range.

untilstring

Absolute end, inclusive; a date-only value covers that whole UTC day.

environment'all' | 'development' | 'staging' | 'production'
world_statestring

Comma-separated keywords matched against each trace's world state: its task goals and summaries and, for a trace the task engine owns, its facts and the user's profile; terms are ANDed.

outcome'any' | 'positive' | 'negative'

Filter by outcome: negative = the trace has a detected user frustration, positive = it has none.

cohortstring

builtin:<key> or a saved cohort id: only traces of the cohort's current members, as the dashboard trace list scopes them.

limitinteger

Maximum traces to return.

offsetinteger

Number of traces to skip.

Response

Successful response.

object required

Trace search results, trace metadata, and pagination information. Each row carries the dashboard trace list's state: processing_status (pending until processed, then complete), error_message, indexed_at, and membership_score (use-case confidence for cluster_id); trace_state: "unavailable" when that state could not be read.

Changes

No recorded changes to this operation across all 1 revision of this API.