---
title: "Get Eval Adoption"
method: GET
path: "/api/platform/v1/evals/{slug}/adoption"
tags: ["observability"]
---

# Get Eval Adoption

`GET /api/platform/v1/evals/{slug}/adoption`

## Request

- Base URL: `https://docs.amdahl.ai`
- URL: `https://docs.amdahl.ai/api/platform/v1/evals/{slug}/adoption`
- Auth: one of:
  - API key in header `X-API-Key`
  - HTTP bearer

Fetch whether this eval changed anything: how many runs produced a recommendation, how many were reported on, how many were applied, and how often the server could confirm it. Read when asked whether an eval is worth running, or alongside the KPI — a rising score with no adoption means callers improved on their own. Every count states its denominator; the rate abstains rather than assert one on a thin window.

## Path parameters

- `slug` string, required

## Query parameters

- `window_days` integer: Trailing window (default 90, clamped 7-365).

## Response `200`

OK

- object
  - `data` object, required
    - `adoption` object, required: Counts, then the rate. `runs_completed` >= `runs_eligible` (refusals and gate-mode runs recommended nothing) >= `runs_with_signal` (someone reported) >= `runs_adopted`. `adoption_rate` is runs_adopted / runs_with_signal, or null with an `abstain_reason` — an abstain (`thin_window`, `no_signal`, `no_eligible_runs`) is never a zero. `counted_evidence` names which evidence values the rate counted; `inferred` is never one of them.

## Other responses

- `400`: Invalid input - failed schema validation
- `401`: Authentication required
- `403`: Forbidden - missing scope or role
- `404`: Not found
- `500`: Internal server error

---

[API](https://skmtc.dev/amdahl/apis/amdahl-platform-api.md) · [All operations](https://skmtc.dev/amdahl/apis/amdahl-platform-api/llms.txt) · [OpenAPI document](https://skmtc.dev/amdahl/apis/amdahl-platform-api/revisions/d4eee33e2472?raw)