# Envoy for Meta Muse

Use Envoy's agent pages in Meta Muse's browser. Open [https://agent.envoy.money/agent-interactions](https://agent.envoy.money/agent-interactions) and follow the [browser agent guide](https://agent.envoy.money/browser.md). A separate custom API connector has only partial verification; it is not proof of a working account read or purchase. Help for agents: [https://agent.envoy.money/agent-interactions/help](https://agent.envoy.money/agent-interactions/help).

Support revision: `envoy@2026-10`. Last updated: 1 November 2026.

## Connect with a custom connector

Consumer Muse connector registration was verified on 7 October 2026 with `token_endpoint_auth_method: none`. `client_secret_basic` was rejected. Authentication, account reads, token renewal and purchases through that connector are not verified. The connector is not submitted to or approved by Meta. See the [Muse integration notes](https://agent.envoy.money/docs/integrations/muse/).

For a connector you are implementing, use Envoy's current [OAuth guide](https://agent.envoy.money/docs/api/authentication/) and [HTTP quickstart](https://agent.envoy.money/docs/get-started/api-quickstart/). Discover current endpoints through Envoy's resource metadata. Do not invent a callback, client ID or token. Keep credentials in the host's designated credential storage, outside the conversation.

A first read is `POST https://api.envoy.money/tools/get_account` with `{}` through the authenticated connection. Confirm account access only when that read succeeds. A connection or account read does not verify payment support. Do not start a purchase for a setup-only request.

If Envoy asks for new connection consent, follow the reconnect action. Token renewal does not itself approve new spending terms. Preserve any purchase reference and reconcile its status before another purchase action.

## Connect with the agent pages

Complete sign-in in your own browser. Follow [Connect the user's Envoy wallet](https://agent.envoy.money/browser.md#connect-the-users-envoy-wallet). Connect goes through `auth.envoy.money` to `https://envoy.money/agent-login`. The user approves the sign-in in the Envoy app. If the page offers an SMS fallback, enter that sign-in code only when your host permits it. Never retain or repeat it. Stop if the user declines.

After returning, confirm the authenticated account read. Stop there for a setup-only request. Connecting does not approve a purchase or change a saved payment preference.

Keep the same browser profile between tasks. Envoy's HttpOnly cookie holds an opaque handle; tokens stay on the server. Cookie retention is not a promised sign-in lifetime. If the page asks you to connect again, complete sign-in in that browser. A temporary service error alone is not a reason to clear cookies or reconnect. **Disconnect** forgets the browser handle and ends access. Do not copy cookies or invent an integration. See [Signing in and staying signed in](https://agent.envoy.money/browser.md#signing-in-and-staying-signed-in).

## Use the tools on the agent pages

Follow `#next-step` in **Do this now** and relay `#tell-user` without secrets. Use the current page's links and forms. Their `data-tool` and field names identify the operation. `pre#page-data` contains the non-secret instruction and actions; `?format=json` returns the full reply. Keep payment details out of retained records. If Envoy refuses a form, `ul#refused-fields` lists what to fix.

Use the server-derived `#deadline` for your current action. An expected update, payment-link expiry, spending deadline and checkout-code expiry are different. An overdue update does not prove that payment failed. While `#keep-going` is present, follow the page's current action. Waiting pages can update themselves. Do not add a polling loop. A ready page never polls or automatically refreshes, because reading ready status can release credentials.

See [Read a page](https://agent.envoy.money/browser.md#read-a-page) and [Call a tool](https://agent.envoy.money/browser.md#call-a-tool).

## Pay

Start one purchase with `start_purchase`: the merchant URL, total, complete items and the user's own words. Follow the purchase page. The user approves card-backed purchases in the Envoy app. You cannot approve them. If Envoy offers a gift-card payment link, the user opens and pays it. You never open or pay it. The amount due can differ from the gift-card value. Funding is not merchant-order confirmation.

Read who completes checkout. When Envoy completes it, leave the merchant payment page alone and follow the returned status action. Do not report that checkout. When you complete it, wait for `ready` and use only this purchase's released payment details. Redeem a gift-card voucher with its code and PIN as the merchant instructs. A voucher code is not a bank OTP.

For a one-time card, its Checkout code is this card's OTP. Enter the matching `checkout_code` once when the bank page asks for a code or OTP. If the code expires before submission, deliberately check the same purchase and proceed only if ready. A code refresh never extends spending access or funds a new card. If the bank rejects it, do not retry: report `failed` with `failure_reason: otp_failed`. The bank sends the user no code for this card, so never ask the user for one.

After your checkout attempt, use **Report the result**. Preserve the hidden `checkout_attempt_id` when present. Report `paid` only when the merchant confirmed payment. Otherwise report `failed`; if completion is unclear, use `failure_reason: other`. After any report, do not pay or cancel; follow Envoy's reconciliation action.

Keep card details, gift-card codes, PINs and checkout codes out of replies, files, memory, logs and feedback. Never start a second purchase or use another payment method while an outcome is unknown, because the user could pay twice. Never collect a payment or bank OTP in chat. Envoy sign-in codes and merchant sign-in questions are separate tasks.

Follow [Pay for a purchase](https://agent.envoy.money/browser.md#pay-for-a-purchase) for the shared procedure.

For a gift card, an app task can mean balance approval or an in-app payment; do not infer the funding source or captured amount. The app shows what the user pays. Follow [the six gift-card facts](https://agent.envoy.money/docs/payments/gift-vouchers/) for references, money, voucher progress, actors, permitted actions and checking times.