Settings & billing

/dashboard/settings is the only surface in the Account group. Profile and Organization keep their state when you switch between them, so a half-typed edit is not thrown away by a click.

Your personal details, shown across the Console and to your team: display name, company, phone, website, timezone and a short bio. Email is displayed but not editable here, because it is the identity the auth provider holds.

Below the form, two read-only facts worth knowing when you are debugging an access problem: which auth provider signed you in, and the first eight characters of your user id.

An organization is what owns things. Keys, request traces and billing history attach to it rather than to a person, which is what makes them survive somebody leaving. Everyone starts with a personal organization.

The tab opens on a list of the workspaces you belong to with your role in each. Selecting one shows its profile — name, description, website, industry, size — and its members.

Owner and admin are the two roles that count as administrative; API key creation, revocation and scope edits all require one of them. Three rules constrain the members list: you cannot change your own role, only an owner can act on another owner, and the role dropdown offers Owner only when you are one. Role changes apply optimistically and roll back visibly if the server refuses.

Admins invite by email with a role attached, and the picker prints what that role means before the invite is sent. An invite expires seven days after it is created; pending ones are listed with their expiry and can be revoked.

When the invite email cannot be delivered, the Console says so and hands you the link instead of failing silently — the invite itself was created either way, and the link is copyable from the pending list.

Beyond the personal organization, creating workspaces is limited to one additional organization on every plan, and to five on the legacy enterprise tier. Exceeding the limit returns a refusal naming the limit rather than a generic error.

The seat count a plan is sold with is a separate number and is not enforced here: nothing blocks an invite past it today. Seats per plan are listed on Pricing & plans.

Two choices. Use Lobstack AI is managed mode: no provider key of your own, and every request debited from the plan's allowance at the published Lobstack rate. Bring your own key switches to BYOK, where your key pays the provider, nothing is marked up, and the recorded cost is informational rather than billable. BYOK is also sold as a plan of its own, metered on requests rather than dollars, because there is no spend of ours to cap.

Beneath that, a single checkbox selects auto — Token Intelligence picks a model per request — or you search the catalog and pin one, grouped by provider. Turning auto on also switches the runtime to managed mode, because routing across providers needs keys for all of them. The routing itself is described on the Token Intelligence page.

What does exist is scattered across two other places. The Overview surface names the current plan on its allowance card, inside the Spend band, next to what the period has consumed and what is left. The initial subscription is taken during onboarding, and Stripe's webhook keeps the subscription row, the plan tier and the allowance in step afterwards.

Usage carries the full allowance panel for the billing period, in whichever unit the account was sold — dollars of model spend, requests on BYOK, or messages on a legacy subscription — and the top-up buttons for plans that sell them. Plan prices, allowances and the three meters are on Pricing & plans.