Skip to content
supastack
Browse documentation

For AI agents: fetch the complete documentation index at /llms.txt, the full documentation corpus at /llms-full.txt, the agent skill at /skill.md, or this page as Markdown at /docs/mobile/usage.md (or send Accept: text/markdown).

Usage and credits

Metered limits, prepaid credit, and the billing surface.

Read the usage state

GET /api/mobile/usage returns the AI budget as microunit decimal strings — budgetMicrounits, committedMicrounits, heldMicrounits, and keyMode — the prepaid credit balance, per-meter rows with label, used, limit, cap, planLimit and description, and the current period bounds. Presentation marks a meter warning at eighty percent and danger at one hundred.

Values are decimal strings, not JSON numbers — parse them before comparing or formatting so large budgets stay exact.

Prepaid credit ledger

GET /api/mobile/credits returns the workspace's prepaid balance and its last fifty ledger rows. The balance feeds Settings → Billing and the home usage card; ledger reference ids are withheld from the client payload.

Home and billing surfaces

The home screen reuses GET /api/workspace/metrics — the same stat grid the web dashboard renders: monthly AI spend, task and thread counts, members, pending invitations, plan status, and unread notifications. Its usage card shows the AI row plus finite-limit meters, and quick-action tiles link to chat, assistant, content, commerce, notifications, feedback, and settings.

Settings → Billing shows the plan, expiration, credit balance, and usage meters, explains store-versus-web billing, and links to the paywall. A server schedule sweeps workspaces every fifteen minutes and notifies owners and admins once a month at eighty and one hundred percent of the AI budget.

Verification and troubleshooting

Check a meter near its cap, an exhausted credit balance, and a workspace on the default budget. A blocked action must point at the meter that denied it, not at a generic error.

Frequently asked questions

14 questions

What is supastack?

supastack is a modular foundation for building AI-powered SaaS products. It brings together common infrastructure so you can focus on product-specific features.

Does it support web and mobile?

Yes. supastack includes Next.js and Expo apps as starting points for web and mobile experiences.

What authentication is included?

Better Auth covers email OTP, magic-link, and social sign-in; email/password stays available at the API layer and through the Auth.js credentials engine for products that need it. Personal workspaces are provisioned with the account so product records stay scoped from day one.

How does it support AI?

supastack includes configurable multi-provider AI, usage tracking, budgets, and encrypted bring-your-own-key support.

How are subscriptions handled?

For products built on the kit, Stripe billing, subscriptions, and entitlements form the paid-access foundation. Provider secrets stay server-only.

Where does my product-specific code live?

Product-specific features remain in a separate codebase while the product configures and integrates supastack’s foundation modules.

How does supastack pricing work?

The kit is a one-time purchase with lifetime updates: Single Stack at $249 — your pick of Next.js (Web), Expo (iOS & Android), or Tauri (macOS & Windows Desktop) — Dual Stack at $398 with any two repos, or the Full Bundle at $399 with all three repos and the full monorepo, plus $75 per extra developer seat. No kit subscription. Checkout on this site delivers your license key by email, with repository access via GitHub invite.

How do workspaces scope my data?

User-owned records are scoped by workspaceId. Identity, entitlements, AI usage, billing events, and audit entries stay inside the personal workspace boundary.

How do background jobs work?

Trigger.dev is the explicit job runtime. The JobRunner contract only promises enqueue, status, and cancel—workflow semantics stay Trigger.dev-specific and explicit.

How is email different from outreach?

Transactional email covers product workflows such as completion notices. Cold outreach and campaigns are product concerns outside this kit’s email module.

How do mobile purchases work?

Mobile includes native purchases and restore through RevenueCat, with access verified by your server. Configure the store accounts and complete device testing before release. Web billing remains separate.

Where do AI provider keys live?

Bring-your-own-key credentials are encrypted and stay server-only. Keys are redacted from logs; usage and budgets remain visible at the workspace level.

Which payment methods does checkout accept?

The Stripe-hosted checkout accepts cards and can also offer Alipay and WeChat Pay once those wallets are enabled on the Stripe account — handy for buyers in China. Wallet authorizations confirm asynchronously, so the license page updates as soon as the payment clears.

Can I get a refund?

After you've got access to the repository, supastack is yours forever, so it cannot be refunded. But rest assured, you get the complete source code with lifetime updates to build and ship unlimited products for yourself or clients. You just cannot resell the code or redistribute the repository as a starter kit or template.

EN
Theme