---
title: "Get one Dojo scenario by slug (How-it-works modal)."
method: GET
path: "/dojo/scenarios/{id}"
tags: ["Dojo"]
---

# Get one Dojo scenario by slug (How-it-works modal).

`GET /dojo/scenarios/{id}`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/dojo/scenarios/{id}`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-Mnemom-Api-Key`

Returns a single Dojo scenario briefing by slug (name, description, GOOD cards, computed `setup_prompt`). Authed for ALL users (any valid Bearer/API key). MNE-517.

## Path parameters

- `id` string, required

## Response `200`

The scenario briefing.

- object
  - `scenario_id` string, required: Scenario slug (e.g. 'db-shepherd').
  - `name` string, required
  - `description` string, nullable: Human-facing blurb.
  - `alignment_card` object, required
  - `protection_card` object, required
  - `setup_prompt` string, required: Agent-facing self-setup copy, computed from the scenario row.

## Other responses

- `401`: Authentication required
- `404`: Resource not found
- `429`: Rate-limit exceeded. The global per-IP limiter (100 requests/minute, applied to every `/v1/*` route) rejected this request. Back off until the window resets — `Retry-After` carries the cooldown in seconds and `X-RateLimit-Reset` the absolute reset time.
- `500`: Server error — request was well-formed but the server failed to fulfill it. Typically a downstream dependency (DB / RPC / external API) returned an unexpected error.

---

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