| Do viewers need accounts? | They can watch without one. Try/Use requires an account (to store keys, preferences, and limits). |
|---|
| How are API keys handled? | Bring‑Your‑Own‑Keys are stored encrypted. At run time we mint scoped, short‑lived tokens for only the requested provider capabilities. Raw keys never reach the app code. |
|---|
| What runs inline vs remotely? | Inline apps are manifest‑driven Actions/Agents. Anything needing custom runtimes runs remotely via the adapter. iOS/Chrome are discovery‑only with deep links. |
|---|
| Is there revenue sharing? | Planned. We’ll expose paid boosts and premium app access; creators get a transparent split. |
|---|
| Mobile readiness? | Creators flag mobile support; we also auto‑audit cards at phone breakpoints and show a “mobile‑ready” badge and filter. |
|---|
| What about scraping/headless browsers? | Not inline. Use a remote adapter with your own Playwright service and declare the capability. |
|---|
| Are there rate and spend limits? | Yes. Users set daily caps and per‑run limits; apps have compute ceilings; heavy tasks must run via remote adapters. |
|---|