Setup Muse

October 12, 2026 (October 30, 2026)

Independent third-party service, see Legal

Table of contents

  1. Before you start
  2. Add the account
  3. What to expect
  4. If the account needs attention
  5. Usage limits

Approximately 5 minutes to complete setup steps.


This is the setup guide for Muse API. A Muse account and a useapi.net subscription are required for the API to work.

Add a Muse account with its email and password. The API signs in once and keeps the account signed in from then on.

Before you start

  • Muse is available in the US, Canada, Japan and Singapore (as of October 30, 2026), so create the account in one of them. Once it is added, you can call the API from anywhere.
  • Finish Muse’s onboarding at muse.ai, including Meta’s age check, and create one image there.
  • The account must have email + password sign-in, because the API signs in with the email and password. A Meta account that signs in only with an emailed code has no password yet: create one in Meta Accounts Center (Password and security), then add the account here. Without a password the add is refused with 400.
  • Use the account only for the API, with no other automation tools on it. Opening it at muse.ai in a browser is fine, but only from the US, Canada, Japan or Singapore (the regions Muse officially supports), or through a VPN in one of them: Meta can switch off video for an account it sees used from elsewhere.

The Muse sign-in page at muse.ai

Add the account

A new account answers 201, a re-added one 200, with health: "OK", sessionExpiresAt and quota. Each account runs 10 jobs at a time unless you set maxJobs (1 to 50) above. Accounts added earlier keep their stored value until you change it. To change it later, post the email with a new maxJobs and no password to POST /accounts.

What to expect

  • The API renews the session itself: before the 30-day session expires, and whenever Muse asks for a new sign-in. You never re-add the account for that.
  • Muse emails the account a login code on each sign-in. Nothing needs to be done with it.
  • Re-adding the account with the same password reuses its live session, so it does not sign in again.
  • Chat can act on the apps connected to the Muse account, such as email or calendar. With Muse’s default setting, some actions, like sending an email, happen without asking. To make Muse ask before each one, set connectors to always_ask with POST /accounts/email/permissions. Connect only the apps you want the API to use.

If the account needs attention

The API pauses an account it cannot use, emails you once, and answers 596 with the reason, also shown in health on GET /accounts:

  • Meta asks for a security check, usually after a sign-in from a new place. Sign in at muse.ai in a browser, complete the check, then add the account again with the same email and password.
  • Muse refused to sign in when the session was renewed, usually because the password changed. Add the account again with the current password.

Temporary problems never pause an account. They answer 503, and a retry works.

Usage limits

Muse meters each account weekly. GET /accounts/email returns the plan and usage in quota: tier, percentUsed, resetsAt and quotaStatus.

Plan Price Weekly allowance
Free $0 not published
Power $20/month 500 million Muse tokens
Maximum $100/month 3 billion Muse tokens

Source: Meta, About Muse subscriptions, October 2026. Availability can differ by region.

  • On the free plan, a video used 2 to 3 percent of the weekly allowance in our tests and an image 0 to 1 percent. Meta does not publish per-job token costs.
  • The allowance resets at resetsAt. Once it is used up, new jobs go to your other accounts, and a job pinned to the account answers 412.
  • Tokens bought or granted on top of the plan show on muse.ai as Additional tokens and never expire. The API keeps sending jobs to an account that has top-up left after its weekly allowance is used up. topupLabel gives the top-up as muse.ai words it, for example 0% used (1B tokens left). topupBalance (left) and topupTotal (bought) are Muse’s own counters, not token counts: an account with 1B tokens left reads 40000000.
  • Muse also limits the videos an account makes over the last 24 hours, apart from the weekly allowance. When it says the limit is reached, video jobs skip the account for an hour. See Video limit.