Skip to main content
DELETE
Archive an agent
Sets the agent’s status to archived. Its /v1/ai/{slug} route stops serving — requests are refused with 503 agent_not_active. Archiving also disables the upstream routes row it orphans, scoped to the data space you archived in, so archiving a sandbox agent does not disable the Live route. Before 2026-08-30 the route stayed enabled and the upstream remained reachable through an agent you had archived. Existing phantom tokens for the agent are not revoked — they simply have nothing to reach. Revoke them explicitly if the credential itself is the concern: Revoke a phantom token. Requires the delete capability on ai_gateway. See the control-plane overview for authentication, the {data, meta} envelope, pagination and error types.

Authorizations

Authorization
string
header
required

OAuth 2.1 authentication — recommended for new integrations. Access tokens (kc_ prefix) are minted at the root-host token endpoint https://api.knoxcall.com/oauth/token and passed as Authorization: Bearer <access_token>. Public clients must use PKCE with the authorization_code grant; confidential clients may use client_credentials. The first-party SDKs and the knoxcall login CLI handle token minting, caching, refresh, and DPoP for you.

Path Parameters

id
string<uuid>
required

The AI agent UUID.

Response

The archived agent.

data
object
meta
object

Metadata included with every API response.