Reset a Muse account

October 14, 2026

Table of contents

  1. Request Headers
  2. Request Body
  3. Responses
  4. Model
  5. Examples
  6. Try It

Reset the account’s Muse computer, as Reset in the muse.ai app’s data settings does. The account gets a fresh agent computer, and everything on the old one is deleted for good: every chat, file, document, web app and podcast, the agent’s memory and its name, and any open browser. This cannot be undone.

Use it when the account’s computer is stuck, for example when every new browser stays Queued and stopping browsers does not help. The account stays added, with its sign-in, and the new agent starts with a short onboarding message of its own.

  • Send the account email again as confirm, so a reset never happens by mistake.
  • Every chat id, job id and asset id of the account answers 404 after the reset.
  • Do not repeat the call after a 202 or a timeout: the reset has run, and a repeat would reset the new computer too. Check the account with GET /accounts/email or GET /chats instead.

https://api.useapi.net/v1/muse/accounts/email/reset

  • email is the email of an added account, URL-encoded in the path.
Request Headers 
Authorization: Bearer {API token}
Content-Type: application/json
Request Body 
{
  "confirm": "[email protected]"
}
  • confirm is required, the account email, the same as in the path.
Responses

  • 200 OK — the account was reset, and its new computer is ready.

    {
  "email": "[email protected]",
  "reset": true,
  "ready": true
}

  • 202 Accepted — the account was reset, and its new computer is still starting. Requests on the account may answer 503 for about a minute. Do not reset again.

    {
  "email": "[email protected]",
  "reset": true,
  "ready": false,
  "message": "Muse reset the account; its new computer is not ready yet. Requests may answer 503 for a minute"
}

  • 400 Bad Request — confirm is missing or is not the account email. Nothing was reset.

    {
  "error": "confirm must be the account email ([email protected]): a reset permanently deletes every chat, file, artifact and memory of this Muse account",
  "code": 400
}

  • 401 Unauthorized

    Invalid API token.

    {
  "error": "useapi.net ⁝ Unauthorized",
  "code": 401
}

  • 404 Not Found — the account named by email is not added.

    {
  "error": "Account [email protected] not found",
  "code": 404
}

  • 409 Conflict — jobs or chat answers are running on the account, or a reset of it is already running. Nothing was reset. Retry when they finish.

    {
  "error": "Account [email protected] has 1 running job(s) or chat answer(s). Reset it when they finish",
  "code": 409
}

    {
  "error": "A reset of account [email protected] is already running",
  "code": 409
}

  • 502 Bad Gateway — Muse refused the reset. Nothing was reset.

    {
  "error": "Muse refused the reset of account [email protected] (…)",
  "code": 502
}

  • 503 Service Unavailable — Muse could not be reached. Nothing was reset. Retry shortly.

    {
  "error": "Could not find the Muse computer of account [email protected], please retry shortly",
  "code": 503
}

  • 596 Account Error

    The account needs your attention, and it is paused until you add it again. You receive an email when this happens. There are two causes.

    Meta asks for a security check on the account. Sign in once at muse.ai in a browser, complete the check, then add the account again with POST /accounts using the same email and password. The API keeps using its session, so no new sign-in is needed.

    {
  "error": "Account [email protected]: Meta asks for a security check on account [email protected] (\"This account must complete a security checkpoint on the web\"). Sign in once at https://muse.ai in a browser, complete the check, then add the account again with POST /accounts",
  "code": 596
}

    Or Muse refused to sign the account in again when its session needed renewing, most often because the password was changed. Add the account again with the current password.

    {
  "error": "Account [email protected]: Muse refused to sign in account [email protected] (…). Update its password with POST /accounts, or sign in at https://muse.ai to clear the block, then re-add it",
  "code": 596
}
Model 
{ // TypeScript, all fields are optional
  email: string
  reset: true
  ready: boolean      // false: the new computer is still starting (202)
  message?: string    // 202 only
  error?: string      // errors only
  code?: number       // errors only
}
Examples 
  • EMAIL="[email protected]"
curl -X POST -H "Authorization: Bearer …" \
     -H "Content-Type: application/json" \
     -d "{\"confirm\": \"$EMAIL\"}" \
     "https://api.useapi.net/v1/muse/accounts/$(python3 -c "import urllib.parse,sys;print(urllib.parse.quote(sys.argv[1],safe=''))" "$EMAIL")/reset"

  • const token = "API token";
const email = "Previously added account email";
const apiUrl = `https://api.useapi.net/v1/muse/accounts/${encodeURIComponent(email)}/reset`;
const response = await fetch(apiUrl, {
  method: "POST",
  headers: {
    "Content-Type": "application/json",
    "Authorization": `Bearer ${token}`,
  },
  body: JSON.stringify({ confirm: email })
});
console.log("response", response.status, await response.json());

  • import requests
from urllib.parse import quote
token = "API token"
email = "Previously added account email"
apiUrl = f"https://api.useapi.net/v1/muse/accounts/{quote(email, safe='')}/reset"
headers = {
    "Content-Type": "application/json",
    "Authorization" : f"Bearer {token}"
}
response = requests.post(apiUrl, headers=headers, json={"confirm": email})
print(response, response.json())
Try It

Resetting deletes everything on the account. Type the account email in both fields to go ahead.