MUSE RADAR / EVENT BRIEF

Meta Business Agent Adds Practical Guides—Check the Number, Permissions and Test Path First

On October 6, Meta reorganized Business Agent guidance into build-from-scratch and add-a-capability paths, with explicit WhatsApp number, onboarding, dual-token-permission and testing prerequisites. This is a concrete enterprise-platform follow-up, not proof that Muse API or Muse Code is generally available.

Meta Enterprise Platform 公告中的 Meta 官方配图
Meta Newsroom

Meta now documents an executable Business Agent path

Meta's September 28 Enterprise Platform announcement grouped Muse, Meta Business Agent, Muse API and Muse Code under one enterprise direction without a universal setup path. The October 6 documentation update makes the Meta Business Agent branch concrete: guides are split into Build an agent and Add a capability, then mapped to the business outcome a team wants.

Build guides cover phone onboarding, instructions, knowledge, connector tools, human handoff and tests. Existing agents can add a focused capability such as live inventory, a multi-turn cart, identity verification or an interactive message without rebuilding the whole configuration.

Three prerequisites prevent misleading success responses

Meta lists three baseline requirements: an eligible WhatsApp Business number with Business Agent configured in WhatsApp Manager, a completed Agent Onboarding API call for that number, and an access token carrying both whatsapp_business_messaging and whatsapp_business_management.

A token with messaging alone may authenticate successfully while reads such as connector logs or evaluation results return an empty 200 response instead of an obvious error. Do not treat 200 as proof that data exists; verify the management permission, number scope and entity ID first.

Secure-storage illustration from Muse's official design material
Muse official design material · Background illustration, not a Meta Business Agent screen

Increase test risk in deliberate stages

The Quickstart can produce test replies in three API calls before billing, webhooks or live conversations are configured. After configuration, choose among the Agent Test API, scored evaluation runs and allowlisted live conversations. Meta explicitly recommends trying to break the agent instead of testing only a happy path.

Begin with one read-only task, such as looking up a test order and returning named fields. Verify that the connector stays read-only, stops on missing data and avoids over-sharing before adding writes, handoff or interactive messages. Our connector and activity-log guides help scope and review the test, but they do not replace Meta eligibility or official evaluation.

This does not make Muse API or Muse Code generally available

The verified change is a Meta Business Agent documentation and operating path for eligible WhatsApp Business numbers. It does not provide universal Muse API or Muse Code keys, pricing or region coverage, so those parts of the original enterprise-platform event remain open questions.

Maintain separate access checklists for each product. Business Agent now has concrete number, token, connector and test checks; Muse API and Muse Code still require their own official documentation and account entry points. A platform-level announcement does not mean every named product opened at once.

Source notes

Meta for Developers · official · 2026-10-06Meta for Developers · Meta Business Agent changelog ↗

Event date and our publication date are shown separately. Community reports describe individual experiences.