remove_standby_installation
Stop keeping the standby installation (the spare bot) registered for a project.
Purpose
The standby is forgotten and withdrawn from the connector; the live installation, members and access stay as they are, and the next bot replacement will need a fresh credential pasted on the dashboard. Registering a standby is not offered to tokens because it takes a credential; removing one is. Only the project owner may do this.
This tool is annotated destructive: a client that supports the annotation asks a human before running it. The REST twin is DELETE /v1/projects/{project}/recovery/standby-installation.
Required ability
project-recovery:delete
Input schema
{
"type": "object",
"required": [
"project_id"
],
"properties": {
"project_id": {
"type": "string",
"description": "UUID of the project whose standby installation to remove."
}
}
}Output shape
{
"data": {
"project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",
"standby_installation_registered": false
},
"meta": {}
}Example prompts
"Drop the standby bot on Research Premium; I am replacing it with a new one from the dashboard."
Failure modes
VALIDATION_FAILED— the token is not the project owner's.RESOURCE_NOT_FOUND—project_idis not a project the token can see.AUTHENTICATION_REQUIRED— no authenticated user on the request.TOKEN_MISSING_ABILITY— token lacksproject-recovery:delete.
Related
get_recovery_settings—standby_installation_registeredsays whether one is kept.- Recovery API
How is this guide?
remove_resource_standby
Stop keeping a standby for one resource; the chat itself is untouched and the resource keeps its live chat.
request_resource_replacement
Ask the creator, through the connector, to pick the chat that replaces a resource's; the swap runs the moment they choose. Nothing is swapped by the call itself.