Envoy in Meta Muse
Use Envoy's browser pages in Meta Muse and distinguish that path from an unverified connector.
Use Envoy's browser agent pages when Meta Muse drives a browser. No plugin or MCP installation is needed. Follow that guide to connect the existing Envoy account and complete a read-only account check.
Support revision: envoy@2026-10. Last updated: 28 October 2026.
The browser entrypoint is https://agent.envoy.money/agent-interactions. The agent completes sign-in in its own browser. Keep that browser profile between tasks. If Envoy asks to connect again, follow the current sign-in page; a temporary service error alone is not a sign-out.
The separate HTTP connector has only partial evidence. Registration with a public client was verified on 7 October 2026. Runtime compatibility, connector submission and Meta approval are not verified. Those results do not establish a working account read or purchase in Muse.
Compatibility
The technical submission form captured on 22 September 2026 offers Raw API and OAuth with PKCE, with fields for an API URL, an optional OpenAPI URL, a documentation URL and access requirements. These are submission choices, not proof of runtime support.
| Area | Envoy today | Consumer Muse status |
|---|---|---|
| API transport | HTTPS JSON POST /tools/{tool} | Calling Envoy from the consumer agent is unverified |
| Schemas | OpenAPI and the tool reference | OpenAPI import and supported features are unverified |
| OAuth | Authorization code with S256 PKCE, scope agent, resource https://api.envoy.money/mcp, public client (token_endpoint_auth_method: none) | Registration with none verified 7 October 2026; client_secret_basic was rejected. Callbacks and resource forwarding are unverified |
| Account read | get_account takes {}; the owner comes from the token | A successful read from a fresh consumer task is unverified |
| Session lifecycle | Private token storage, serialized refresh, explicit disconnect | Refresh, lost-reply handling and disconnect are unverified |
| Credential handling | Authorized ready status can release the purchase's payment details; host permissions still apply | Keeping credentials out of retained tool history is unverified |
Meta's architecture article, published 8 September 2026, describes third-party OAuth tokens stored outside the agent runtime and inserted into outgoing requests. That does not establish which hooks an Envoy connector receives or how returned card details are handled.
Start with an account read
- Use the API quickstart and OpenAPI. They own the request shapes and examples.
- Follow OAuth with PKCE with the callback and client that Muse's own integration flow supplies. Do not invent a Muse callback or client ID. Register with
token_endpoint_auth_methodset tonone; the registration endpoint rejects any other value, and Muse then shows "The provider rejected the automatic app registration" before sign-in. - Have the owner approve the Envoy connection. This does not approve a purchase. The user approves card-backed purchases in the Envoy app. If Envoy offers a gift-card payment link, the user pays it themselves.
- In the actual consumer Muse agent, make one call:
POST /tools/get_accountwith{}. Usedataonly whenokistrue; otherwise follownext. A scripted call, a Muse Code session or another host's result does not count. - Verify fresh-task access, token renewal and disconnect separately. After a lost refresh reply, reconnect instead of replaying the token; see Reconnect and resume your task.
Keep purchases separate from the account read
A successful account read, OAuth connection or Meta approval does not show that purchases work in consumer Muse. Before any purchase there, verify that the one-time card reaches only the checkout and never enters replies, files, task memory, logs or retained tool history. See request protection.
Access and review
Meta's 8 September launch announcement describes a US rollout. Consumer-agent availability for a particular account or in India is unverified. Envoy separately requires an existing account; see availability.
The Muse Connector Platform describes functional, security and legal review plus end-to-end testing before directory admission. Ask the platform for the reviewer setup and the technical test process.
MCP as a fallback
Consumer Muse MCP compatibility is unverified. Muse Code's MCP support is a separate product. Use the browser path above unless your exact connector has been verified. App builders can read the remote MCP connection guide for Envoy's protocol; that guide does not prove Muse compatibility.