SuperPowers Docs
Current product guide

Everything you can do with SuperPowers, in one clean guide.

This page documents the current feature set across the main web app, the iPhone / iPad app, the Apple Vision Pro app, the Android private streamer, the macOS streamer, and the desktop CLI streamer install flow. It is written for real users first: what each app does, how to set it up, what to say, which permissions matter, and how the apps fit together in daily use. This guide is kept in sync with shipped feature changes, including new marketplace, payments, and API surfaces.

Projects + chat All major clients let you organize work into projects and talk to the assistant inside each project.
Powers Create, save, import, publish, install, schedule, and monetize reusable automations driven by prompts and voice commands.
Private devices Connect Android, Mac, Windows, or Linux streamers through WebRTC so Super can see and control your personal devices.
Realtime context Camera or panel snapshots are periodically summarized so the assistant understands what is on screen.
Overview

What SuperPowers is

SuperPowers is a voice-first automation system that combines realtime chat, visual context, browser and device control, reusable prompts called powers, and private device streaming. Depending on which client you use, Super can:

See what you see

Web, iOS, and Vision Pro periodically summarize the live camera or panel view so the assistant can answer questions about what is visible.

Control browsers and devices

Use the web app directly, open browser agents on Apple platforms, or control connected Android and Mac private devices over WebRTC.

Package workflows as powers

Turn useful prompts plus voice commands into reusable powers, publish them to the marketplace, or save them privately in your prompt library.

One account, multiple surfaces Sign in with the same phone or email across the web app, iPhone app, Vision Pro app, Android private streamer, and Mac streamer. That is how your projects, device slots, and connected private-device rooms line up.
Quick Start

Best starting path by platform

Use only the web app

  1. 1
    Open the dashboardGo to app.getsupers.com and sign in with your phone or email.
  2. 2
    Create or choose a projectProjects live in the sidebar and keep chats, powers, and device actions organized.
  3. 3
    Talk or typeUse the mic for realtime voice or the message box for chat. On desktop, Enter sends and Shift + Enter makes a newline.

Add your own device

  1. 1
    Get a device slotUse your plan or unlock more private-device capacity if your account needs additional slots.
  2. 2
    Choose a streamer pathUse the desktop CLI from npm, the Android private streamer, or the Mac streamer depending on the device you want to host.
  3. 3
    Control it from chat or by tapping the streamOnce connected, Super can click, type, scroll, scrape text, take screenshots, and run supported device commands.
Fastest desktop setup You can now install the desktop streamer from the terminal with npm install -g superpowers-ai, then run superpowers login. The CLI signs you in or creates your account with your email or phone, starts the streamer, and prints a control link for /general.
Web dashboard for day-to-day control iPhone app for camera + voice-first mobile use Vision Pro for spatial browser and panel workflows CLI, Android, or Mac streamers for your own private devices
Latest Updates

Recent customer-facing changes

April 8, 2026

  • Text your devices: if your account has text control enabled, you can send instructions like open twitter in device 2 or run the marketing play in all devices.
  • Four-device grid by default: the remote-control area now opens with a four-device grid unless you choose a different layout.

April 7, 2026

  • Desktop streamer from npm: install with npm install -g superpowers-ai, then run superpowers login.
  • Instant control link: after login, the CLI starts the streamer and prints a browser link that opens the control surface directly.

View superpowers-ai on npm

April 6, 2026

  • Chat attachments: use the + button beside the message box to attach images, PDFs, and text files.
  • Keyboard control: when a remote Android, Mac, Windows, or Linux stream is active, browser keyboard input can be sent straight to that device.
  • Theme switch: choose light mode or dark mode from Settings and the app remembers your preference.

April 5, 2026

  • Chrome extension: a browser extension is now available as another setup option.
  • What’s New bell: the web app now includes a notifications button for recent customer updates.

Open Chrome extension

Shared Concepts

The ideas that appear across the whole product

Projects

Projects are the main containers for your work. Use them to separate clients, campaigns, experiments, or internal tools. Most chat threads and private-device flows assume you have an active project selected.

Powers

A power is a reusable automation recipe made of a name, an optional voice command, and a prompt. Powers can stay private or be published to the marketplace for other users. Scheduled powers also appear in supported clients so recurring automations stay visible.

Saved prompts

Saved prompts are your personal prompt library. Opening a marketplace power on web or iOS adds its prompt and voice command to local saved prompts so you can reuse it faster.

Private devices

Private devices are your own Android or Mac streamers connected over WebRTC. They are tied to device slots on your account and are controlled from the dashboard or mobile clients.

Realtime voice

Realtime mode gives you lower-latency voice interaction. When paid realtime is paused or credits are exhausted, the product can fall back to free OpenRouter chat and local text-to-speech where supported.

Integrations

Integrations are powered through Composio. The UI shows service tiles with favicons and green checkmarks when connected. Once a service is connected, powers and voice commands can use it.

Desktop CLI

The published superpowers-ai npm package installs a desktop streamer from the terminal, signs you in or creates your account with your email or phone, starts the local streamer, and prints a control link.

Text-message control

When enabled on your account, supported text messages can trigger actions on your live devices using the same owner and device-routing model as the web controller.

Business login flow When you sign in with an email address, the system can inspect the domain, infer the business, and ask you to confirm the company, description, person name, email, and domain before continuing.
Feature Matrix

Which app does what

Feature Web iPhone / iPad Vision Pro Android Private Streamer macOS Streamer
Projects + chat Yes Yes Yes Embedded control panel mode Yes
Powers + marketplace Yes Yes Yes Via embedded control panel Voice prompt sheet + project chat; marketplace is centered on web / mobile clients
Integrations modal Yes Yes Marketplace / studio integration path plus voice-connected Composio tools Via embedded control panel Yes
Camera or panel context summaries Yes, every 10 seconds while eligible Yes, every 10 seconds while eligible Yes, every 10 seconds while eligible No local assistant camera loop; it streams the device No local camera loop; it streams the desktop
Private device hosting Yes Yes Yes Yes Yes
Browser / panel agents Browser-like power surfaces Yes Yes, in spatial panels Embedded web control panel mode No dedicated browser-agent layer
Tap-to-control remote stream Yes Yes Yes N/A Yes
Fullscreen WebRTC Yes Yes, with double-tap Spatial focus workflow N/A Main panel only
x402 paid APIs Yes, full setup plus live device API listing No dedicated native setup flow No dedicated native setup flow No No
Web App

How to use app.getsupers.com

The web app is the main command center. It gives you the most complete blend of projects, chat, powers, marketplace access, integrations, private-device control, camera context, and on-screen WebRTC controls.

Main navigation

  • Projects sidebar: create projects, switch contexts, invite others, and manage account/project context without unrelated settings crowding the list.
  • Top-right controls: model picker, powers, private-device control, and a new Settings gear live above the stream area.
  • Chat composer: on desktop, Enter sends, Shift + Enter inserts a newline, and the + button lets you attach images, PDFs, and text files.
  • Mute: the mute button blocks mic input and also stops outbound realtime requests from being sent while muted.
  • Settings + updates: the Settings modal now includes light mode and dark mode, and the bell icon opens recent customer updates.

Camera and visual context

  • The browser can show a live camera preview.
  • Every 10 seconds, when realtime is enabled and not muted, the app captures the current camera or active stream image.
  • That image is summarized with nvidia/nemotron-nano-12b-v2-vl:free through /tools/vision.
  • The text summary is silently fed into realtime so the assistant understands what is on screen without automatically speaking back.

Power Studio

Create and save powers

  • Give the power a name.
  • Add a voice command such as post to twitter.
  • Write the prompt describing what the power should do.
  • Optionally mark it for a remote device flow.
  • Optionally enable x402 if you want to charge per run using USDC on Base.
  • Use Publish to marketplace if you want other users to see and install it.

Import Claude Code / OpenClaw skills

  • The Import Claude Code/OpenClaw Skills button accepts .txt, .md, and .markdown files.
  • You can pick individual files or, where supported, an entire directory.
  • Power Studio also accepts a direct skills.md URL. Paste a raw file URL, or a GitHub .../blob/... URL that points to the file, then click Load skills.md URL.
  • Each URL import fetches the file fresh and replaces the previous import from that same URL, so clicking it again updates the saved skills instead of leaving stale duplicates behind.
  • The app combines all imported text files into one saved prompt with a source-file header.
  • Large imports are trimmed automatically so the saved prompt stays usable.

Marketplace

Install and track powers

  • The marketplace shows My Powers and All Powers.
  • The web marketplace now opens full-screen, with denser Live Device APIs and My Powers cards so you can scan more items at once.
  • The old inline x402 setup section is gone. Use the small Wallet + x402 button next to Refresh to open the dedicated setup modal instead.
  • Each public power displays an Opens count.
  • Installed powers show a visible checkmark.
  • When you click Open, the power's prompt and voice command are also saved locally to your prompt list.
  • On mobile web, the Powers entry point now stays reachable in both portrait and landscape, including Chrome on iPhone.

Creator workflows

  • Published powers can be reopened, edited, unpublished, or republished.
  • Marketplace creator rewards are surfaced in PHONECLAW on the marketplace screen.
  • The marketplace now also shows x402 readiness, live device API inventory, and monetized power pricing where available.
  • The Power Studio and marketplace are linked, so you can jump directly from an empty state into creating a new power.

Paid powers on web

Creator setup

  • Connect a Base-compatible payout wallet.
  • Set a price for the device API or power.
  • Choose which public powers the live device is allowed to run.
  • Keep the web host and private device connected while you want paid runs to work.

What buyers get

  • Clear pricing in Base USDC.
  • A payment challenge when payment is required.
  • Execution on the creator's live connected device after payment succeeds.
  • Optional directory visibility for public paid powers.

WebRTC stream controls

Record

Use the red record control to capture the active WebRTC stream. When you stop, the recording is analyzed with Gemini 2.5 via OpenRouter and converted into editable step-by-step instructions.

Fullscreen

Open the active stream fullscreen without covering it with large bottom controls. Mobile landscape keeps the stream in WebRTC mode and rotates the layout appropriately.

Close active

Close the active stream quickly from the top control row. Connected sessions remain managed through the private-device room list.

Keyboard control

When a remote device is active, browser key presses can be forwarded directly to Android, Mac, Windows, and Linux streamers.

Four-device grid

The remote-control area now opens with a four-device grid by default, so multiple live devices are easier to manage immediately.

Text-message control

If enabled for your account, you can send supported text commands and have them forwarded to your live devices through the same control stack.

Hand tracking on web Hand tracking is enabled by default but can be turned off in the sidebar. The Minority Report-style dial is currently visual guidance only; it should not trigger commands by itself. It works best in landscape.
Realtime fallback behavior If paid realtime is unavailable, the web app can fall back to openrouter/free for chat and control. Browser text-to-speech can read responses aloud, and the mic is briefly muted during speech to avoid feedback loops.

Support, payments, and private devices

  • Support modal: opened from the sidebar, with a Calendly embed and quick links like YouTube, Discord, and the full docs at app.getsupers.com/docs.
  • Connect Private Device: shows your purchased device count and room code, plus purchase actions for PayPal and crypto.
  • Crypto device unlock: the crypto purchase path includes wallet connection and PHONECLAW balance checking.
  • iPhone visitors: the page can detect iPhones and try to redirect users into the App Store / iPhone app flow automatically.
iPhone / iPad App

The native Apple mobile app

The iOS client is the main native mobile experience. It combines AR camera context, chat, browser-agent surfaces, powers, integrations, private-device control, and a native onboarding flow backed by Superwall.

Onboarding and account flow

  • The app includes a native onboarding sequence and routes users through the Superwall paywall during onboarding.
  • Sign in with phone or email.
  • If you use an email, the app can inspect the domain, infer the business, and present a confirmation sheet.
  • After business detection, the assistant can greet the user personally and describe the inferred business.

Core UI

  • Projects live in a sidebar with search and creation tools.
  • Header actions include Marketplace, Integrations, Power Studio, stream controls, credits, add credits, invite, and private-device entry points.
  • The app supports browser-style power windows and fullscreen web views in addition to camera-based AR overlays.

Voice, visual context, and mute behavior

  • Realtime voice is available directly in the app.
  • The app periodically summarizes the camera feed every 10 seconds using the same nvidia/nemotron-nano-12b-v2-vl:free image model path used by the web app.
  • The assistant receives those summaries silently so it has scene context without forcing a reply.
  • Mute parity is built in: muting blocks outgoing voice requests, output, and forced mic capture.
  • When realtime is paused or blocked, the app can speak assistant replies through native text-to-speech while suppressing the mic to avoid hearing itself.

Private devices and WebRTC on iOS

  • You can create private-device rooms, reuse saved room IDs, and connect Android or Mac streamers.
  • WebRTC overlays support double-tap fullscreen.
  • When fullscreen is active and the device rotates, the stream stays in WebRTC mode and rotates with the interface.
  • Marketplace powers opened on iOS also get added to your local saved prompts, and installed powers show a checkmark.

AR and gesture features

  • The iOS app includes AR-driven hand-pose and open-palm detection for its floating power / command surfaces.
  • Browser windows, browser-status planes, and power surfaces can live inside the AR scene alongside camera context.
  • This makes the iPhone / iPad app feel closer to a spatial control panel than a plain chat app.
Browser-agent workflows on iOS The native iOS client is not only a camera app. It also supports browser sessions, fullscreen web views, browser JS execution, and browser-window voice commands inside the app.
Apple Vision Pro

The spatial version of SuperPowers

The Vision Pro app carries the same core system into a spatial panel with immersive passthrough, browser-powered workflows, power modals, voice tools, and panel-context summaries.

What you see in the main panel

  • A web-powered main panel inside a rounded spatial surface.
  • Quick buttons for Marketplace, Studio, Commands, Mute / Unmute, and Prompt.
  • Optional overlays like maps and the powers menu.
  • Onboarding and signup overlays if the session is not set up yet.

How voice works

  • Voice prompt text is stored locally and can be appended into the assistant prompt.
  • Mute blocks requests, output, and mic forwarding.
  • Fallback speech uses native AVSpeechSynthesizer when needed.
  • Voice commands can open marketplace, open Power Studio, control browser windows, and interact with private-device streams.

Panel context and browser agents

  • Every 10 seconds, while voice is available and not muted, the current panel view is captured and summarized.
  • The summary is sent into voice context as a silent Camera update, even though in Vision Pro it is really a panel or browser view.
  • The app supports browser windows, focusing windows, scrolling, clicking, typing, opening fullscreen browser sessions, and returning them to 3D space.
  • Marketplace and Power Studio are surfaced as modal flows controlled from the spatial panel.
Best use case Vision Pro is strongest when you want a heads-up, hands-light control surface for projects, powers, browser workflows, and connected private devices, without sacrificing passthrough context.
Desktop CLI Streamer

Install the streamer from npm

The desktop CLI is the fastest way to turn your own Mac, Windows, or Linux machine into a private streamer without walking through a separate app UI first.

Install and sign in

  1. 1
    Install the packageRun npm install -g superpowers-ai.
  2. 2
    Log in or create your accountRun superpowers login and enter your email or phone plus the verification code.
  3. 3
    Open the printed control linkThe CLI starts the streamer and prints a link that opens the control surface directly in the browser.

Useful commands

CLI commands
npm install -g superpowers-ai
superpowers login
superpowers start
superpowers stop
superpowers whoami
superpowers logout
What the CLI does for you After login, the CLI can start the local streamer right away, keep retrying the host connection, and give you a control link that opens the standard browser controller without asking you to sign in again.
Android Private Streamer

Your private Android device host

The Android private streamer is the Android app you install on your own phone to let Super stream and control it remotely over WebRTC. It can also switch into an embedded client mode that loads the main control panel for the same account.

Host mode screen

  • Account field for phone or email.
  • Send code and Verify sign-in flow.
  • Status rows for signaling, room, streaming, and Moondream.
  • Enable Accessibility, Disconnect, and Open Control Panel buttons.
  • A device-unlock purchase button appears when the account has no available device slot.

Client mode

  • The app can switch from streamer mode into a WebView control panel.
  • That control panel loads the main web app with the current owner ID prefilled.
  • Back to Streamer returns to host mode.
  • Reload refreshes the embedded control UI.

Permissions and reconnect behavior

  • Accessibility is required for text entry, tapping, long pressing, multi-clicking, scrolling, and scraping UI text.
  • Screen recording is required for WebRTC streaming.
  • Microphone may be requested for audio capture.
  • Notifications can be requested where needed by the app flow.
  • After asking for screen-recording permission, the app waits 10 seconds and tries to click Start now automatically through the accessibility layer.
  • The app runs an auto-rejoin loop every 15 seconds so it can reconnect when the host refreshes or a room temporarily disappears.

Remote commands the Android streamer supports

Navigation

Open app, open URL, Home, Back, and scrolling.

Touch actions

Single tap, 5-second hold / long press, and rapid multi-click bursts such as 10 to 20 taps.

Text and extraction

Type text, send text, scrape targeted text, scrape page text, and capture screenshots.

Private streamer disconnect policy The private Android streamer is treated like a persistent personal device. It should reconnect after host refreshes, and it no longer needs post-disconnect cleanup behavior like automatic Twitter reinstall or browser-cache clearing.
macOS Streamer

Your private Mac desktop host

The macOS streamer is the desktop companion for streaming and controlling your own Mac. It includes projects, chat, a model picker, Composio integrations, voice command settings, and a WebRTC panel that can be remote-controlled by tapping the live stream.

Main app layout

  • Sidebar: projects, credits, device counts, unlock-devices button, logout.
  • Top row: model picker, voice toggle, Commands, Integrations, Private Device, Cloud Agent / Stop Stream.
  • Chat panel: native project chat with message history and send box.
  • WebRTC panel: shows the remote stream and accepts tap-to-click on the live video.

Private-device flow

  • Use Private Device to display the room code for pairing.
  • The sheet includes the Android streamer download and a tutorial link.
  • Cloud Agent starts hosting the room if you have a device slot.
  • The app now includes auto-reconnect logic so it can recover when the remote host refreshes or the signaling room drops.

What the Mac streamer can do remotely

Capability What it means in practice
Open apps and URLs Launch installed apps by name or bundle, or open web links.
System-wide input Click, long press, multi-click, scroll, type text, and send keyboard shortcuts through accessibility and CGEvent APIs.
Terminal hooks Open Terminal, focus it, type directly into it, and optionally press Enter.
Perception helpers Take screenshots, run object-targeted click detection, and scrape visible UI text from the frontmost app.
macOS permissions required The Mac streamer needs Accessibility for automation and Screen Recording for streaming and screenshot capture. Without those, remote control commands and desktop capture will not work.
Powers and Marketplace

How powers work from creation to install

Create a power

  • Add a title that you can recognize later.
  • Add a voice command if you want to trigger it by speech.
  • Write the prompt in plain language.
  • Choose whether it is mainly for remote-device workflows.
  • Choose whether to expose it through x402 and set a Base USDC price per run.
  • Choose whether to publish it to the marketplace for everyone.

Install a power

  • Open the marketplace and click or tap Open.
  • The power is marked as installed with a checkmark.
  • The marketplace open count increments.
  • The prompt and voice command are copied into your local saved prompts so you can reuse or edit them later.

Enable a live device API

  • Click Use wallet to connect a Base-compatible 0x... payout wallet for the creator account.
  • Turn on x402 for the user profile in the marketplace status area using the checkbox. The toggle now persists immediately.
  • Set the device's Base USDC price, provide a Base payout wallet, click Save x402, and keep the web controller host connected to a live WebRTC room.
  • You can save the Base wallet and price before the enable toggle is turned on.
  • Use the marketplace cards to select which public powers your API will accept.
  • Once a device is attached, the room appears in the marketplace as a live API target.

What x402 adds

  • Public powers can be sold per run in Base USDC.
  • Device APIs and powers become callable like paid endpoints.
  • Each x402-enabled user now has a supported-powers allowlist that controls what their live device API will run.
  • The backend returns an HTTP 402 challenge when payment is missing or invalid.
  • After settlement, the run is pushed directly to the live device host over WebRTC.

Stream-to-steps workflow on web

  1. 1
    Record a live streamUse the WebRTC record button in the web app while the target task is happening.
  2. 2
    Let Gemini 2.5 analyze itThe recording is sent through OpenRouter using Gemini 2.5 to produce step-by-step instructions.
  3. 3
    Edit and saveThe generated steps appear in an editable modal. Click Add to Saved Prompts when it looks right.

Paid device API flow

  1. 1
    Connect a payout walletAdd a Base-compatible wallet and set your device API price from the marketplace or Power Studio.
  2. 2
    Enable the powerChoose which public powers your live device is allowed to run for paid requests.
  3. 3
    Keep the host liveYour web host and private device need to stay connected so the paid run has a live target.
  4. 4
    Share the paid APIOnce payments are enabled, buyers can trigger the power against your live device using the published paid API.

What creators need

  • A valid Base payout wallet.
  • A price set for the live device API or power.
  • A live web host with an attached private device.
  • The supported paid powers enabled for that device.

What buyers see

  • The creator name and price before payment.
  • The device or power being requested.
  • A normal payment challenge if payment is required.
  • The result after the live device finishes the run.
Example power prompt
When I say post launch update, open X, draft a short update about today's release, include one clear CTA, and post it.
Voice and Realtime

How speech, fallback, and mute work

Normal realtime behavior

  • Voice can run in realtime where the client supports it.
  • Scene summaries from camera or panel context are silently added so Super understands what you are looking at.
  • Business welcome prompts can be spoken automatically after login and account confirmation.
  • Realtime metering auto-recovers after a browser reconnect or backend restart instead of surfacing a stuck meter-session error.

Fallback behavior

  • When realtime credits are blocked, the web app can fall back to openrouter/free.
  • Web uses browser text-to-speech for spoken fallback.
  • iOS and Vision Pro use native speech synthesis for fallback.
Mute means more than silent output On current web, iOS, and Vision Pro builds, mute is designed to stop outgoing realtime requests as well as audio output, so the assistant is not still listening and acting while you think it is muted.

Useful things to say

General

General voice examples
Open Marketplace
Create a power called invoice follow-up
Open profile
Add credits

Device control

Device examples
Focus device 1 full screen
Open Terminal and type npm run dev
Long press the submit button for 5 seconds
Click the follow button 15 times
Private Devices and WebRTC

How personal device streaming works

Private devices let you connect your own Android phones or Macs to Super. This is separate from cloud devices and is designed for personal hardware you control.

  1. 1
    Get a device slotYour account needs an available device slot. This can come from direct purchase or the eligible crypto path where supported.
  2. 2
    Generate a roomFrom web, iOS, or Vision Pro, open the private-device flow and generate or reuse a room code.
  3. 3
    Pair the streamerEnter that room on the Android private streamer, start hosting from the Mac streamer, or use the desktop CLI for Mac, Windows, or Linux.
  4. 4
    Control the streamUse chat, voice, text-message commands where enabled, keyboard input, or direct taps on the WebRTC view. On web, top controls also let you record, fullscreen, or close the active stream.

What happens on disconnect

Both Android private streamer and Mac streamer now focus on reconnecting to the same room instead of dropping permanently when the host refreshes or the signaling room temporarily disappears.

What you can do from the stream view

Tap or click the stream to send normalized pointer actions. The assistant can also focus a device by number, open it fullscreen where supported, and dispatch device-specific commands over the data channel.

Integrations

Connecting external services

Integrations are handled through Composio. The product shows recognizable service tiles with favicons and green checkmarks when a service is already connected.

Common built-in tiles

Gmail, Google Drive, Google Calendar, Slack, Notion, GitHub, Linear, and Jira are surfaced prominently in the main UIs.

How connection works

Open the Integrations modal, tap the service, and the app opens the login or connection flow. Once complete, the tile shows as connected.

Why it matters

Connected services become available to powers, scheduled commands, and assistant workflows so Super can act across your tools.

Composio catalog The UI highlights the most useful day-one integrations, but the backend tool surface can support a much wider Composio catalog beyond the first visible row of services.
Payments, Credits, and Devices

How credits and device access are unlocked

Credits

  • The apps surface credit status and can direct you to add credits through profile or payment flows.
  • After payment, credits may take a short period to appear.
  • If realtime credits are unavailable, free model fallback may still let you chat and control devices, depending on the client and model selection.

Device slots

  • Private devices consume device slots.
  • Purchase links are surfaced in the app when no slot is available.
  • On web, the Connect Private Device modal includes a PayPal purchase option and a crypto purchase path.
  • The current web lifetime-deal countdown is set to end on March 23, 2026 at 12:00 AM in the visitor's local browser time.

Wallet and PHONECLAW details

  • The web app supports connecting Phantom and OKX Solana extension wallets.
  • Wallet flows can verify whether the connected wallet holds the required value of PHONECLAW.
  • When eligible, the wallet path is used to unlock device access in the private-device flow.
  • Wallet connection and verification are separate from the older support and lifetime-deal surfaces; the current private-device purchase flow is the main place where this matters for users.
  • These Solana wallets are for private-device unlocks and credit additions; x402 creator payouts now use a separate Base-compatible 0x... wallet.

x402 payment readiness

What you need

  • x402 must be enabled on the server.
  • The creator must save a valid Base-compatible 0x... payout wallet.
  • The creator must enable x402 and choose a device API price plus payment token.
  • The power must be public if it is going to be sold through /x402/run.

Status indicator meanings

  • x402 enabled: payments are turned on for paid runs.
  • Payments ready: the app has enough information to accept paid requests.
  • Wallet linked: the creator has a payout wallet attached.
  • Live devices: the count of connected device APIs currently available to paid callers.
  • Supported powers: how many marketplace powers the current x402 device API is willing to run.
Permissions and Privacy

What each permission is for

Permission Where it matters Why it is needed
Camera Web, iOS Live camera preview plus periodic scene summaries for assistant context.
Microphone Web, iOS, Vision Pro, Android streamer Voice input and, on some device streamers, audio capture.
Screen Recording Android private streamer, macOS streamer Required for WebRTC desktop or phone streaming and for screenshot capture on Mac.
Accessibility Android private streamer, macOS streamer Needed for taps, typing, long presses, multi-clicks, scraping text, and other UI automation.
Notifications Android private streamer Requested for app workflow support where needed.
Automatic visual summaries Web, iOS, and Vision Pro intentionally send periodic visual snapshots for summarization so the assistant understands the current scene. The product is designed to summarize what is visible and feed the text into the assistant rather than forcing a spoken reply each time.
Troubleshooting

Fast answers to common issues

I am muted, but the assistant still seems active. Why?

On current web, iOS, and Vision Pro builds, mute is intended to block outgoing realtime requests as well as audio playback. If something still seems active, unmute once, then mute again to reapply the request block and mic suppression state.

Why does a private device say room not found?

The room may have been refreshed or dropped. Current Android private streamer and Mac streamer builds include an auto-reconnect loop to retry the room instead of failing permanently. Wait for the reconnect cycle or recreate the room from the host client.

Why can I not control my Android or Mac device?

Most control actions need Accessibility permission. Streaming itself also needs Screen Recording on Android and macOS. If those permissions are missing, taps, typing, screenshots, and text scraping will fail even if the room is connected.

Why is a marketplace power not showing as installed?

Open the power from the marketplace. Installed powers are tracked locally and should show a checkmark on web and iOS after the open action saves the prompt and voice command into your saved prompt list.

What happens if I run out of realtime credits?

Depending on the client, the app can fall back to free OpenRouter chat and local text-to-speech. The web app is designed to default toward the free path when paid realtime is unavailable, rather than blocking basic chat entirely.

Why is my paid power or device API not working?

Most paid-run issues come down to one of four things: the payout wallet is missing, the price was not saved, the power is not enabled for the device, or the web host and private device are not both live. Re-save the marketplace settings, make sure the device is attached, and try again.

How do I make a power available for paid runs?

Open the power in the marketplace or Power Studio, make it public, turn on payments, set the price, and mark it as supported for the live device that should run it.

Why did a paid request fail after payment?

That usually means the live host disconnected, the private device dropped, or the power was no longer available to that device. Reconnect the host and device, then retry the run.

Why is my device not showing up in Live Device APIs?

Today the x402 live-device list only includes active web-controller rooms. Make sure you enabled x402, saved a Base-compatible payout wallet, set a device API price, and kept the web host connected to a live WebRTC room with an attached device.

What if the x402 checkbox in the marketplace does not stay on?

If the toggle flips back off, the most common causes are a missing Base wallet, an unsaved price, or editing the power while signed into the wrong account. Save the wallet and price first, then enable payments again.

Why does x402 say the device API has not enabled that power?

The live x402 device API now uses an allowlist. Open the marketplace while signed in as the device owner, enable x402, and click the support toggle on the public power you want that device API to accept.

How do I get human help?

Open the Support modal from the web app sidebar. It includes a Calendly embed for booking help plus quick links to Discord, YouTube, and the docs at app.getsupers.com/docs.