---
title: "Stop running one eval against this environment."
method: DELETE
path: "/simulate/api/harness-environments/{id}/evaluations/{eval_config_id}/"
tags: ["simulate"]
---

# Stop running one eval against this environment.

`DELETE /simulate/api/harness-environments/{id}/evaluations/{eval_config_id}/`

## Request

- Base URL: `http://localhost:8000`
- URL: `http://localhost:8000/simulate/api/harness-environments/{id}/evaluations/{eval_config_id}/`
- Auth: one of:
  - API key in header `X-Api-Key`
  - API key in header `X-Secret-Key`

Soft-delete only. The verdicts an eval already produced live on the call
executions and in their receipts, not on this row, so a hard delete would
leave past runs showing scores for something the environment no longer
lists. Removing an eval someone added stops future scenarios being
graded by it and leaves the history it already wrote intact. An eval the
harness reported itself comes back the next time the harness grades it.

## Response `204`

Removed

## Other responses

- `default`: Default error response

---

[API](https://skmtc.dev/futureagi/apis/future-agi-management-api.md) · [All operations](https://skmtc.dev/futureagi/apis/future-agi-management-api/llms.txt) · [OpenAPI document](https://skmtc.dev/futureagi/apis/future-agi-management-api/revisions/c8684118e142?raw)