notify_members_of_recovery

Email every member the project can reach that its bot changed after a bot replacement, at the per-email fee. Sent once per recovery.

Purpose

After a bot replacement, members who only ever talked to the old bot need the new one's link. This emails every member the project can reach by email with the new bot and the portal, at the per-email fee added to the creator's transaction fees, and remembers that it did: a second call answers with the count already sent and sends nothing. It spends money and reaches real people, so confirm with the creator first.

This tool is annotated destructive: a client that supports the annotation asks a human before running it. The REST twin is POST /v1/recovery/operations/{operation}/notify-members.

Required ability

project-recovery:update

Input schema

{
    "type": "object",
    "required": [
        "operation_id"
    ],
    "properties": {
        "operation_id": {
            "type": "string",
            "description": "UUID of the bot recovery whose project members to email."
        }
    }
}

Output shape

{
    "data": {
        "operation_id": "c2e8f1a9-6d47-4b3e-9f05-1a8d7c2e4b60",
        "notified": 340
    },
    "meta": {}
}

Example prompts

"Email my members about the new bot for Research Premium."

Failure modes

VALIDATION_FAILED — the recovery belongs to no project, or the token is not the project owner's.
RESOURCE_NOT_FOUND — operation_id is not in this creator's ledger.
AUTHENTICATION_REQUIRED — no authenticated user on the request.
TOKEN_MISSING_ABILITY — token lacks project-recovery:update.

Replacing a banned bot — when to send it.
Recovery API