Console
Workspace console
The console at /app is where a team runs its workspace: switch tools on, link connectors, create keys, invite members, reload credits and watch every call. This page walks through each area.
Home#
Get started is the default tab while the workspace has no successful tool call. It shows the endpoint and default key, harness snippets for Claude, Codex, any MCP client and the CLI, a live "listening" block that turns green on the first call, and a checklist (key, harness, first call, connector). After the first call, Dashboard becomes the default: calls and spend over 24 hours, 7 or 30 days, a stacked chart by tool, spend by API key, the live call stream and the credit meter with runway.
Tools & Connectors#
- Native tools are cards with an on/off switch and a configure drawer: monthly budget (with optional pausing), tool settings and the functions exposed.
- Connectors show their link state (not linked, linked, needs attention). The drawer has four tabs: Credentials (connect, set the default, disconnect), Functions (expose or hide each action), Guardrails (rate limit, daily cap, allowed keys, require approval for writes) and Activity (recent calls and held requests for this connector).
- Datasets list what the workspace may query with the price at its rates; subscription datasets are subscribed and cancelled here.
- The MCP manifest view shows exactly what
tools/listreturns right now, so you can check what an agent sees before it runs.
Toggles are optimistic with an undo toast; every change is written to the audit trail with the member's name.
Activity#
Three tabs. Tool calls lists every metered call (time, function, key, status, latency, units, cost) with filters by tool, key, status and range, live refresh, paging and a CSV export; clicking a row opens its metering detail. Approvals is the queue of held writes with the request payload, an optional note, and Approve & run / Deny for members who may decide; decided requests stay for the audit trail. Credit ledger shows every non-usage credit movement: grants, reloads, refunds, adjustments, expiries.
API keys#
Settings → API keys. One key per agent keeps spend and access easy to reason about.
- Create with a name, access ("everything enabled" or selected tools), an optional monthly cap and an optional expiry (30, 90 or 365 days). The plaintext is shown once in a reveal banner.
- Edit access and cap at any time; rotate to issue a fresh key with the same settings and revoke the old one; revoke to stop it immediately.
- The table shows month spend against cap, last use and an expiry warning two weeks out. Revoked keys stay listed for the record.
- Owners and Admins manage every key; Developers create and manage their own; Billing and Viewer members see the list.
Members and roles#
Settings → Members. Seats are free; you only pay for what agents call. Invite by email (several at once) with a role; the invitation link expires after seven days and can be resent or revoked. When the host has no email delivery configured, the console shows the link to copy instead.
| Role | Can |
|---|---|
| Owner | Everything: tools, keys, members, billing, approvals, renaming and closing the workspace. The last Owner cannot leave. |
| Admin | Tools and connectors, all keys, members (except promoting to Owner), approvals. Billing is reserved to Owners and Billing members. |
| Developer | Tools and connectors, their own keys, activity. |
| Billing | Billing and credits, activity. |
| Viewer | Read-only access to the whole console. |
A member can belong to several workspaces and switch between them from the sidebar. Removing a member ends console access at once; keys they created keep working until revoked.
Billing and auto-reload#
Settings → Billing & credits shows the prepaid balance, runway at the current burn rate, spend over 30 days and the credit breakdown by bucket.
- Reload a preset or any custom amount within the host's bounds, from a saved card. The summary shows credits added and the balance after; every paid reload has a numbered receipt.
- Payment methods are stored by the payment provider; the console keeps only brand, last four digits and expiry. Set a default, add more, remove any.
- Invoice for amounts at or above the invoice threshold: the order waits for the bank transfer and credits arrive when an operator confirms payment.
- Auto-reload: when the balance drops below a threshold, add a fixed amount from the default card, capped by a monthly limit. Month-to-date auto-reload spend is shown against the limit.
- Alerts: an email to the receipt address when runway falls under seven days, and a console banner under a balance you choose.
- Credit history lists reloads, grants and invoices with status, receipt links and a CSV export.
Approvals#
When a connector requires approval for writes, an agent's write call answers 202 approval_pending and the request lands in Activity → Approvals (a badge in the sidebar and a notification count the pending items). Owners and Admins see the payload, add a note, and approve (the action runs now with the workspace credential and is billed) or deny (the agent receives a denial and nothing is written). Requests expire after LeanTools.Tenant.ApprovalExpiryMinutes. Agents poll the outcome at GET /api/v1/connectors/approvals/{id}; see Connectors and approvals.
Workspace settings#
Settings → Workspace: rename the workspace, set its country (used for tax treatment on receipts), see the endpoint and identifiers, leave the workspace, or close it. Closing revokes every key, removes every member and forfeits unused credit; it asks you to type the workspace name to confirm.
For operators#
The host (operator) portal at /host manages accounts, packages and rate cards, the service catalogue, platform settings, billing orders (confirming invoice payments) and contact requests from the public site. Self-service sign-up can be switched off with the setting LeanTools.Tenant.AllowSignup; the public MCP URL and docs URL shown in the console come from LeanTools.Tenant.PublicMcpUrl and LeanTools.Tenant.DocsUrl.