Billing & workspaces
read as.mdBilling 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 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 Plan & usage page
Section titled “The app’s Plan & usage page”Open an agent → Plan & usage (or /apps/<app-id>/plan). 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).
- Export usage — download one month of the agent’s usage as CSV: managed-LLM cost at the provider’s list price (per model), tokens, renders, sessions by where they happened, and pod and storage time. It is per agent, never per end user, and each export lists what it cannot attribute.
guuey usage exportgives the same file from the CLI. - 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.
- High effort: not available yet. When it opens, it’s one switch for a no-code app, on or off. Off is the default, and new generations use the default level. On, new generations switch to high, and each one that isn’t a cache hit carries a paid add-on. It needs the app’s own active paid plan and a live deployment. If it’s missing either, the switch says which. Until it opens, an app with both reads “Not available for this app.” In the Console, owners and admins see it on this page.
Billing (the wallet view)
Section titled “Billing (the wallet view)”Billing in the sidebar is the active scope’s wallet — the control tower for money and the account: the next invoice as Stripe previews it (one per app subscription — plan fee, usage so far, credits applied, the card it charges), the invoice history with Stripe’s hosted page and PDF for each, the payment methods on file, credits (balance and top-up), the workspace’s MCP hosting subscription, and every app subscription in one list. Adding or replacing a card and tax details happen in Stripe’s Customer Portal (Manage in Stripe). Deliberately, everything else here is a link — plan changes and caps live on each app’s own Plan & usage page, the pod limit on its Settings page, hosting actions on MCP Registries → Billing — so no field has two writers.
API keys
Section titled “API keys”API keys in the sidebar is where you get a key. It opens with your personal guuey_user_* keys, the credential kind guuey login mints for CLI use on your own machine; create and revoke them here. A personal key works on every agent you own, and on your team’s agents as far as your workspace role allows.
Below them, Workspace keys is for CI on an agent a team workspace owns; you don’t need one to work on your team’s agents yourself. It lists each team workspace you belong to. An owner or admin gets a link to that workspace’s key page; other members see that an owner or admin creates them. Workspace keys themselves are managed per workspace (see Workspaces).
Account Settings
Section titled “Account Settings”Settings in the sidebar is about you:
- Profile — display name, email, and account deletion (with a pending-deletion window you can cancel).
- 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
Section titled “Workspaces”A workspace is a shared scope with its own wallet, agents, and MCP registry. One account can create up to 20 workspaces, counting its personal workspace. This is an abuse guard rather than a plan limit, so contact support if you need more. From Settings → Workspace, open a workspace to manage it:
- Members — invite people by email as Admin or Member. Each workspace also has an Owner. Owners and admins can edit and delete any of the workspace’s agents, invite people and read conversation transcripts. By default only owners and admins can create agents, and an owner or admin can let members create them too or limit it to owners. Members can view the workspace’s agents, and the member who created an agent can deploy it and change some of its settings. A fourth role, Viewer, grants no edit rights: viewers cannot create agents, cannot be given that right, and cannot see the workspace’s hosted MCP servers. The Console does not offer Viewer, but an owner or admin can assign it through the API.
- Incoming transfers — agents being transferred into the workspace await acceptance here.
- API Keys — workspace keys (
guuey_wkz_*) for CI and automation. Each key is held by the owner or admin who created it, and it stops working when that person leaves the workspace, is removed, no longer has the owner or admin role, or deletes their account (keeping CI running). Revoking a key 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.