---
title: "Mint a single-use claim-intent ticket (anonymous, birth-token proof)."
method: POST
path: "/dojo/claim-intent"
tags: ["Dojo"]
---

# Mint a single-use claim-intent ticket (anonymous, birth-token proof).

`POST /dojo/claim-intent`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/dojo/claim-intent`
- Auth: none required

The true-first-timer claim flow (MNE-879). A LOGGED-OUT user who opens a dojo claim link proves ownership with the birth token (`mnbt_…`) / hash proof and receives a short-lived, single-use, opaque ticket (`mci_…`). That ticket — NOT the secret proof — rides the sign-up → email-confirm → return round-trip, so nothing sensitive lands in the URL, the confirmation email, or browser localStorage (which is gone when the email opens on another device — the exact reason a first-timer claimed an agent but it never bound to its dojo config). The proof is verified HERE and never stored; the ticket is the post-verification capability. Intentionally public (`security: []`) — the birth-token proof IS the authorization, the same posture as `/dojo/try-me/resolve`. Exchange the ticket via `POST /dojo/claim-intent/exchange` once authenticated.

## Request body

- object
  - `agent_id` string, required: The agent (`mnm-…`) being claimed.
  - `hash_proof` string, required: Ownership proof — the live birth token (`mnbt_…`) whose row pins this agent's hash, or the full 64-hex `SHA-256(apiKey|name)` proof. Verified at mint; never stored.
  - `dojo_config_id` string, uuid: Optional — the TryMeConfig to bind the agent to at exchange (the claim link's `&dojo_config`). Carried through the round-trip so the bind can't be lost.

## Response `201`

A single-use claim-intent ticket.

- object
  - `intent_token` string, required: Opaque single-use ticket (`mci_…`). Present it to the exchange.
  - `expires_at` string, date-time, required

## Other responses

- `400`: Bad request
- `403`: Forbidden
- `404`: Resource not found
- `409`: Resource conflict — the request cannot proceed because of a current state conflict (e.g., resource already exists, version mismatch, in-flight idempotency key with a different body).
- `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)