amp agent-analytics

このページはまだあなたの言語に翻訳されていません。 現在取り組んでいますので、後でもう一度確認してください。

amp agent-analytics reads saved Agent Analytics insights and manages datasets, evaluators, and eval runs. Read commands require analytics:read; commands that change data require analytics:write.

amp agent-analytics insights list

Returns saved cost, efficiency, and quality findings, ranked by magnitude times confidence. These are periodically evaluated findings, not live queries. Healthy and closed findings can remain visible. Thumbs-downed findings are excluded. Use each finding's project_id for individual reads.

Requires the analytics:read scope.

amp agent-analytics insights get

Returns one finding by its stable UUID and own project_id. Missing, cross-project, and thumbs-downed findings return 404.

Requires the analytics:read scope.

amp agent-analytics datasets create

Creates an empty dataset. Add sessions with the dataset sessions endpoint. name is not an identity key, so repeating a create makes another dataset, even with the same Idempotency-Key.

Listing and reading datasets is served by the Agent Analytics MCP read surface, not by this API.

Requires the analytics:write scope.

amp agent-analytics datasets update

Updates dataset metadata. Absent fields are unchanged; an explicit null clears description. id, agent_name, and source_type are immutable — create a new dataset to change the agent scope.

Requires the analytics:write scope.

amp agent-analytics datasets remove-sessions

Removes sessions from a dataset. The sessions themselves are untouched; only their dataset membership is removed. Sessions that are not in the dataset are ignored, so the call is safe to repeat.

Takes the same body as the add operation, so an add is undone in one call rather than one call per session. dry_run=true validates the dataset and the session ids without mutating, returning 204 on a hit and 404 if the dataset does not exist.

Requires --yes to apply changes, or --dry-run when supported to validate without applying changes.

Requires the analytics:write scope.

amp agent-analytics datasets add-sessions

Adds sessions to a dataset. Sessions already in the dataset are ignored, so the call is safe to repeat. Every session must belong to the path project; a session from another project fails the whole request with 422.

Requires the analytics:write scope.

amp agent-analytics evaluators create

Creates an evaluator in the inactive state. Activation is a separate permission and is not exposed by this API — activate in the Agent Analytics UI once the evaluator has been reviewed.

tags constrains what a result may record. Supplying them for a binary or categorical evaluator is what keeps results to a known set of values rather than free-form model output.

Listing and reading evaluators is served by the Agent Analytics MCP read surface, not by this API.

Requires the analytics:write scope.

amp agent-analytics evaluators update

Updates an evaluator addressed by its stable identifier. Absent fields are unchanged. Each update creates a new inactive version; the response id is that new version, and stable_id is unchanged.

Updating does not activate. An evaluator already active in the UI keeps serving its current active version until the new one is promoted there.

Requires the analytics:write scope.

amp agent-analytics eval-runs list

Returns eval runs for the project, most recent first. A run is a batch evaluation of sessions by one or more evaluators; it is asynchronous, so a freshly triggered run is returned with a pending status and no results.

Requires the analytics:read scope.

amp agent-analytics eval-runs get

Returns one eval run by id, including progress counters and, once the run finishes, cost and latency. Per-session results are read through the Agent Analytics read surface, not here.

Requires the analytics:read scope.

amp agent-analytics eval-runs trigger

Starts an asynchronous eval run and returns it immediately with a pending status. Poll the run by id, or read results through the Agent Analytics read surface once it completes.

Target the run either at a dataset or at a session list, not both. Caps are enforced server-side: 10 evaluators and 100 targeted sessions per run. For larger datasets, only the first 100 members are targeted and the acceptance response includes a truncation warning. This selection warning is not persisted on the run returned by later get/list calls.

Requires the analytics:write scope.

これは役に立ちましたか?

For AI agents: a documentation index is available at /docs/llms.txt. Append .md to any page URL for markdown, or send Accept: text/markdown.

このページでは