---
title: "Archive an agent"
method: POST
path: "/v1/agents/{id}/archive"
tags: ["Agents"]
---

# Archive an agent

`POST /v1/agents/{id}/archive`

## Request

- Base URL: `https://api.cadencercs.com`
- URL: `https://api.cadencercs.com/v1/agents/{id}/archive`
- Auth: HTTP bearer

The honest answer to "how do I get rid of this". **Google deprecated agent deletion for RBM**, so an agent created by mistake — a typo, a test, a brand that changed its mind — is permanent. Archiving is what removal actually looks like here: it disappears from listings on both sides, and unlike deletion it can be undone.

Google is updated first and our record only follows if that succeeded, because a local archive sitting over a live agent at Google looks tidy here and keeps receiving traffic there.

Conversations, transcripts and consent records are untouched. Archiving is not deletion, and there is no deletion.

## Path parameters

- `id` string, required

## Response `200`

Archived.

- object
  - `ok` boolean, required
  - `agentId` string
  - `archived` boolean, required
  - `atGoogle` 'done' | 'skipped' | 'failed'
  - `note` string

## Other responses

- `401`: Not signed in, and no account-linked API key was sent.
- `409`: Conversations are still open on this agent — archiving mid-conversation leaves people who replied to a live message with nothing answering them.
- `500`: Unexpected server error. The body is always JSON.
- `502`: Google refused. Nothing changed here either, so the two cannot disagree silently.

---

[API](https://skmtc.dev/cadencercs/apis/cadence-api.md) · [All operations](https://skmtc.dev/cadencercs/apis/cadence-api/llms.txt) · [OpenAPI document](https://skmtc.dev/cadencercs/apis/cadence-api/revisions/9438443c2081?raw)