inf inferences
inf inference list
List and filter inferences in the active project.
inf inference ls
Options
Don’t hardcode filter values — run
inf inference facets to discover the valid models, providers, environments, tasks, and metadata keys for the active project, along with the full filter reference.--json flag to emit the full result object — { items, nextCursor, hasMore, totalCount } — so scripts can read .items and paginate by passing .nextCursor back via --cursor.
Examples
inf inference facets
Probe the active project for the values you can filter on — models, providers, environments, task IDs, and metadata keys — plus the full numeric/metadata/sort reference. Values are discovered from your data, not hardcoded, which makes this the starting point for building a filtered inf inference list query (and a one-call way for an AI agent to learn the filter surface).
Alias: inf inference filters
--json flag to emit a machine-readable object combining the probed values with a static reference (numeric fields, operators, and sort keys).
inf inference get
Fetch the complete stored request and response for a specific inference — method, path, headers, and the full request/response bodies (returned only when payload storage was enabled for the request; otherwise the sides come back null). Useful for debugging specific calls, inspecting model behavior, or archiving payloads.
Arguments
Options
Add the global
--json flag to print the full { request, response } payload (method, path, headers, and complete bodies) as clean JSON for piping into jq or saving.