---
title: "Trigger a deliberate failure scenario"
method: GET
path: "/agent/v1/scenarios/{scenario}"
tags: ["Agent Sandbox"]
---

# Trigger a deliberate failure scenario

`GET /agent/v1/scenarios/{scenario}`

Returns a controlled failure for testing agent error handling. All responses include header X-Agent-Sandbox-Intentional: <scenario> so error reporters can suppress them. Available scenarios: rate-limited, server-error, bad-gateway, timeout, validation-error, unauthorized, forbidden, not-found, conflict, too-large, slow, partial-content, redirect-loop, malformed-json, empty-response.

## Path parameters

- `scenario` string, required

## Response `200`

Slow / partial-content / empty-response / malformed-json scenarios

## Other responses

- `206` — Partial content
- `302` — Redirect loop hop
- `401` — Unauthorized scenario
- `403` — Forbidden scenario
- `404` — Not-found scenario or unknown scenario name
- `409` — Conflict scenario
- `413` — Too-large scenario
- `422` — Validation-error scenario
- `429` — Rate-limited scenario
- `500` — Server-error scenario
- `502` — Bad-gateway scenario
- `504` — Timeout scenario (returns immediately, see X-Agent-Sandbox-Simulated-Delay header)

---

[API](https://skmtc.net/reqres/apis/reqres-api.md) · [All operations](https://skmtc.net/reqres/apis/reqres-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/reqres/reqres-api/revisions/e5ced6578853/schema)