---
title: "Move an agent to another organization (admin-in-both)"
method: POST
path: "/agents/{agent_id}/move"
tags: ["Agents"]
---

# Move an agent to another organization (admin-in-both)

`POST /agents/{agent_id}/move`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/agents/{agent_id}/move`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-Mnemom-Api-Key`
  - API key in cookie `mnemom_session`

Role-based agent relocation between organizations. The caller must be an owner/admin of BOTH the agent's current (source) org and the destination org — this is the role-based counterpart to re-claim, which relocates by proof of possession (`hash_proof`); move never needs the agent's key. Personal↔company moves are allowed under the same rule. Side effects mirror claim's org-reassignment: billing/quota recompute, canonical-card recomposition (the destination org's template can floor/cap composed values, so the agent's effective posture may change), and source-org team memberships are closed. Every move writes an `agent.org_moved` governance audit row. Mutations require an `Idempotency-Key` header. Moving to the agent's current org is an idempotent no-op (`moved: false`).

## Path parameters

- `agent_id` string, required

## Request body

- object
  - `dest_org_id` string, required: The organization to move the agent into (e.g. `org-...` or `pers-...`). The caller must be an owner/admin of this org AND of the agent's current org.

## Response `200`

Agent moved to the destination organization (or already there — idempotent no-op with `moved: false`)

- object
  - `moved` boolean, required: `true` when the agent's org changed; `false` when it was already in the destination org (idempotent no-op).
  - `agent_id` string, required
  - `from_org_id` string, required
  - `to_org_id` string, required

## 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.
- `503`: An upstream dependency is currently unavailable. The request was not processed; retry after the cooldown window.

---

[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)