---
title: "Record the born agent on its Try-Me Config (authed, owner-only)."
method: POST
path: "/dojo/try-me/bind-agent"
tags: ["Dojo"]
---

# Record the born agent on its Try-Me Config (authed, owner-only).

`POST /dojo/try-me/bind-agent`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/dojo/try-me/bind-agent`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-Mnemom-Api-Key`

Links the born agent's id to its TryMeConfig so Begin Sim can later resolve the dojo provider key by agent_id alone (the dashboard never handles the key). A SEPARATE, dojo-specific step the agent performs AFTER `mnemom login` — NOT part of the canonical claim flow (that page is untouched). AUTHED + owner-only: the caller must authenticate (Bearer/API key — the agent uses its `mnemom login` session) AND be a member of the agent's governing org (ADR-062 — the same gate as `put_alignment_by_agent`/DECLARE). `config_id` (baked into the manifest's `bind` block + the claim link's `&dojo_config`) is the unambiguous selector vs the burned token. Idempotent. MNE-517 §1 / MNE-524.

## Request body

- object
  - `config_id` string, uuid, required: The TryMeConfig to bind to — the unambiguous selector baked into the manifest's `bind` block and the claim link's `&dojo_config`. Begin Sim resolves the dojo provider key from this config.
  - `agent_id` string, required: The born agent's id (`mnm-…`) to link to the config. Owner-only: you must be a member of the agent's governing org (ADR-062), the same gate as publishing its alignment card.

## Response `200`

Bound. A 200 MEANS the agent is now recorded on the config — the endpoint no longer answers `200 {bound:false}`; a failed linkage is 404 `config_not_found` / 403 `config_linkage_forbidden` / 500 `config_bind_failed`.

- object
  - `bound` boolean, required: Always `true` on a 200. Kept for wire compatibility.

## Other responses

- `400`: Bad request
- `401`: Authentication required
- `403`: Forbidden
- `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)