# Agent creation economics — outcome pricing

Create for free. Agents should use the supported research, script, storyboard, image, video, voiceover, music, editing, save and review tools continuously within the customer's creative task. Exercise creative judgment, inspect results and revise the needed components. Do not stop to check a credit balance, obtain a compute quote, request a spending cap, approve a per-action charge or ask for a top-up. Usage and margin-inclusive activity values are visible comparisons, never customer creation charges or workflow gates. Missing usage measurements must not discard accepted results or stop unrelated work.

Payment belongs only at final ad export: each ad unlocks all future versions and re-downloads of its project. One-time packs do not expire. Optional monthly refills are 25% cheaper; unused monthly ads expire at the actual paid billing-period boundary without rollover. Already-unlocked ads stay unlocked. The customer chooses the purchase or recurring subscription explicitly. Creating never buys or subscribes automatically.

Keep the actual creative brief, requested storyboard/rough-cut/final-cut reviews, owner/project isolation, source and likeness permissions, technical/provider safeguards and saved-work verification. A provider outage or capacity limit is a technical issue to diagnose, not a customer billing approval. Preserve accepted work and reconcile uncertain jobs before retrying. Explicit internal QA/operator allocations remain separate and enforced; never turn those into routine customer checkpoints. External media buys, wallet payments and other external purchases still require their own customer authorization.

# Browser connection and customer handoff

Version: 2026-10-14.11. Load before a Browser Bridge handoff or connection recovery. Required: core. This public procedure is available before sign-in and requires no MAIN/provider call.

## Existing connection first; verify host continuation separately
Keep a working authorized session. Do not sign out or request another code because MAIN is unavailable. Production observation on October 14 verified that a Muse Bridge request can be approved, consumed and visibly connected while Muse's Browser worker remains paused at “awaiting approval.” That is a host-resumption failure, not a failed account connection. Do not tell the customer to approve again or provide another password. Promise automatic continuation only after the current host has demonstrated a supported wait/wake path. Otherwise explain its supported resume action before the handoff; one connection-complete notification may be necessary. Never describe that assisted resumption as an unassisted continuation pass. Continue ordinary authorized product work independently of MAIN after account verification.

## Browser Bridge: a complete human handoff, then automatic continuation
Use an existing authorized sign-in first. Before starting Browser Bridge, verify that the host can deliver a clickable link in the customer's native chat and monitor the requesting browser while the human connects. If either capability is missing, explain the limitation and use the host's supported secure sign-in or browser takeover instead; do not start a code-only dead end. Verify an actual supported bounded wait, state notification or wake method before requesting a code; an advertised tool, prior host claim or old connection is not a capability pass. If its wait action is refused, stop Bridge before starting a request. A scheduled check after expiry is delayed recovery, not immediate continuation; do not promise it as an actively monitoring task. Use an existing verified session or supported secure sign-in instead when the host cannot complete this handoff. Stay in the same requesting browser, enter the intended existing account, and supply the current Muse chat return link in Assistant return link (or agentReturnTo in the connection URL) when available. Read the current request's agent-browser-chat-handoff field or verified approval-link href. Immediately post that exact code-prefilled approval link as a clickable Markdown link in the customer's native chat, followed by: “Open this link on your computer. Check the account and access, then select Connect browser. Return here after confirmation; I will verify the connection and continue.” No copying or pasting is required. Do not substitute a screenshot, remote-browser copy button, code-only message or vague instruction. Clicking a link inside a remote browser opens a remote tab; its clipboard is also remote. Never claim either delivered a tab or copied text to the customer's computer. The current request exposes no copy buttons and never needs clipboard access. The code remains available only as a manual fallback; do not include device codes, session tokens or passwords in chat. If a native clickable chat link cannot be delivered, report the host limitation rather than asking the customer to copy from the remote viewer.

Keep the browser task alive while the human connects. Monitor the same requesting page’s connection state until verified sign-in/account completion, denial or expiry. The page checks automatically; successful completion has data-connection-state=connected and emits ruliad:agent-browser-connected after account verification. Resume the current authorized task automatically after that verified result. Do not end with “tell me when approved” or request another “done” message. An external host that cannot monitor/wake its task must disclose that host limitation before using this handoff; the website does not control an external chat scheduler. A human approval is separate from requesting-browser sign-in; verify the latter rather than substituting a page reload or code lookup. Preserve receipts, source protection, requested creative reviews and separate internal QA allocations across the connection. Ordinary creation has no quote, balance or spending checkpoint; export purchases and external media buys remain explicit customer choices. A code change, wrong owner, stale response, denied/expired request or unverified permission blocks that connection only; never approve automatically when a code is pasted or a link is opened.