---
title: "Self-serve re-arm of a stuck (burned) demo token."
method: GET
path: "/dojo/try-me/reset"
tags: ["Dojo"]
---

# Self-serve re-arm of a stuck (burned) demo token.

`GET /dojo/try-me/reset`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/dojo/try-me/reset`
- Auth: none required

UNAUTHED — the token IS the credential, exactly like resolve. Re-arms a BURNED, self-serve-resettable demo token so the next resolve mints a fresh manifest, WITHOUT an operator (a stuck demo self-heals). Bounded against abuse: the config must be opt-in `self_serve_resettable`, the reset count is hard-capped, and a token is re-armable only while already burned (never multiplies a live token) — all enforced atomically. The 409 is uniform across every not-resettable reason (unknown / not opt-in / still live / over cap) so it is not an enumeration or state oracle. POST (body `{token}`) is equivalent. MNE-800.

## Query parameters

- `token` string, required

## Response `200`

The token was re-armed; re-resolve to get a fresh manifest.

- object
  - `reset` true, required

## Other responses

- `400`: Bad request
- `409`: Not resettable (uniform: unknown / not opt-in / still live / over cap).
- `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)