Billing & workspaces

Billing on Guuey is per app — each deployed agent carries its own plan (the model itself is in Plans & billing). The Console splits the money surfaces accordingly: each app’s own billing panel holds the actions; the top-level pages give you the whole picture.

Usage

Usage in the sidebar shows one number per agent: generations used this month. It’s deliberately one number — it is the same meter the runtime increments and the quota gate enforces, so what you read here is what you’re held to.

The app’s billing panel

Open an agent → Billing (or /apps/<app-id>/billing). This is where the actions live:

• Choose or switch the plan — checkout runs through Stripe. Upgrades apply immediately and prorated; downgrades take effect at the end of the billing period. Cancel takes effect at period end, and can be resumed before then.
• Trial state — a free app’s 7-day trial countdown shows here, on the overview banner, and on the wallet card — all reading the same flag, so they can’t disagree.
• Usage meters — per-meter usage for the current period, projected from the same numbers the invoice is built from. The panel is explicit about what’s billable: a meter your plan holds at its included allowance says the plan “pauses at its included quota” rather than quoting a rate nothing will invoice — meaning requests past the allowance are refused until the month rolls over (the pod keeps serving; this is not the trial-expiry pause).
• Spending cap — a monthly USD budget with two modes. Hard (the default) refuses requests that would spend past the cap until the month rolls over or you raise it; soft keeps serving and bills the overage — soft requires a live payment method. Leave the budget blank for the plan default. Details in Metered usage and the spending cap.

Billing (the wallet view)

Billing in the sidebar is the owner-level view of the active scope’s wallet: every app subscription in one list, the workspace’s MCP hosting subscription beside it, and the way into Stripe’s Customer Portal for invoices and the payment method. Deliberately, everything else here is a link — plan changes and caps live on each app’s own panel, the pod limit on its Settings page, hosting actions on MCP Registries → Billing — so no field has two writers.

Account Settings

Settings in the sidebar is about you:

• Profile — display name, email, and account deletion (with a pending-deletion window you can cancel).
• API keys — your personal guuey_user_* keys, the credential kind guuey login mints for CLI use on your own machine. Create and revoke them here.
• Workspace — the workspaces you belong to, and where you create a new one.
• Notifications — coming soon; the panel says what it will cover.

For CI, don’t use a personal key: apps deployed from a repo take an app service token — see Agents as code.

Workspaces

A workspace is a shared scope with its own wallet, agents, and MCP registry. From Settings → Workspace, open a workspace to manage it:

• Members — invite by email; roles are Owner, Admin, and Member. Members read; admins edit, invite, and delete apps.
• Incoming transfers — agents being transferred into the workspace await acceptance here.
• API Keys — workspace keys (guuey_wkz_*) for CI and automation. A workspace key authenticates as the workspace; revoking one stops any pipeline using it immediately.
• Provider keys — the workspace’s own AI-provider keys (BYOK). Apps in the workspace use these unless an app sets its own under Behavior → Model.
• OAuth clients — register client credentials (redirect URIs, and scopes for profile, email, and app read/write) for the day your own application signs users in with Guuey. Registration is live; the sign-in and token endpoints are not yet, and the page says so — credentials you register are kept and start working when they ship.
• Audit — the workspace’s event log, filterable by event family and time window, exportable as CSV.