Manage Account Usage
How do I manage the account running Daily invoice digest? Use Settings → Account for personal details, Organization for members, and Subscription plan for billing. Organization members share one usage balance. Only administrators manage billing.
Confirm the account before changing it
Section titled “Confirm the account before changing it”MCP authorization offers My Controller account and Separate agent account. The latter creates its own user and organization, as does CLI signup. It does not add an assistant to your existing organization.
In the app: check the read-only Email address under Settings → Account → Personal details.
With an assistant: these commands concern the account, so no workflow pin is needed. Read the current identity with:
cai auth status --jsoncai doctor --jsonMCP uses account_status with no parameters. Inspect account.kind, user.organizationName, and user.organizationRole.
account.kind is member, agent (separate, unclaimed), or claimed (separate, email verified). account.claim.available is true only for agent. CLI status returns data.user.email and data.user.organizationId, but an unclaimed account has a synthetic email. Use doctor’s Account check to recognize it.
If you intended an existing account, run cai auth login --json for that account, then repeat the identity check.
Claim a separate account you intend to keep
Section titled “Claim a separate account you intend to keep”Claiming verifies the owner’s email on the current account. It does not merge accounts, and an email registered elsewhere is refused. Claiming removes the unverified cap from the plan allowance. Publishing is already available. Read the effective allowance from account_status.usage.planAllowanceCents, rather than assuming a fixed unclaimed allowance.
Use the owner-supplied email as <address>:
cai signup email <address> --jsonMCP uses account_claim_start with email instead of <address>.
Check that CLI data.email matches the intended address.
Use the six-digit code from that email as <code>:
cai signup verify <code> --jsoncai auth status --jsonMCP uses account_claim_verify with code as a six-digit string. Call account_status afterward to verify identity and allowance.
The retry rules differ between the two paths:
| Path | Codes and resends | Failed attempts and delivery |
|---|---|---|
| CLI | Codes last three hours; up to three same-email codes coexist. Changing email invalidates older codes. | Three bad attempts block verification for ten minutes. A successful send response does not prove email delivery. |
| MCP | Only the newest code works; check expiresAt (15 minutes). Wait 60 seconds between sends; maximum three per 30 minutes. | Five failures block verification for 15 minutes. A reported delivery failure invalidates that code. |
In the app: after claiming, use Forgot password? on the login page to establish a password. Completing the reset revokes all CLI credentials, so run cai auth login --json again on each machine.
Manage personal details and membership
Section titled “Manage personal details and membership”Under Settings → Account → Personal details, choose Edit beside Name or Password, then Save. Changing an existing password also revokes every CLI credential, so reauthorize with cai auth login --json.
Open Settings → Organization. Administrators choose Invite member, enter Email address, select Member (default) or Admin, then Send invite. Admins manage membership and billing.
Existing users are refused: “An account already exists for this email. Existing users cannot join organizations yet.”
Only admins see Invited or Expired invitations. Hover an invitation row for the reload icon (Resend invite) or the trash icon (Revoke invite). Change another member’s role in their row’s selector. Role changes, resend, and revoke apply immediately, without Save or confirmation. Sending can report success even when the email never arrives. A resend replaces the link and expiry, so use the newest link.
Your own row has no role or deactivation controls. The last active admin cannot be demoted or deactivated, so promote another one first.
Review dependent work first. Then hover a member row, choose the account-off icon (Deactivate member), and confirm Deactivate. Access is removed first, then trigger teardown and connection deletion run. Cleanup can fail partway, and retrying deactivation cannot resume it. Contact support to finish cleanup or restore access.
Profile and membership changes have no public CLI/MCP operations, so assistants guide the administrator through the app.
Read usage before adding credit
Section titled “Read usage before adding credit”Open Settings → Subscription plan → Resource usage. Admins see Usage balance, and members see Your usage / Available in plan. Included remaining combines unused plan and bonus allowance. Total remaining adds Purchased credits. Read these remaining amounts, not the used/total fraction. When a breakdown exists, admins can switch Plan usage / Members, which includes deactivated members with usage this period.
MCP account_status returns the plan, balances, and period dates. Every amount under usage is in cents, so remainingTotalCents: 350 means $3.50. CLI auth status supplies identity, not usage, so use the app for billing readback.
Subscriptions use Stripe billing periods. Without one, or after cancellation, monthly periods follow the organization’s creation date. Record the dates and remaining balance before a digest test, then check usage and the result afterward.
Daily invoice digest spends the shared pool, and so do its billable development tests. Controller AI agent conversations also incur runtime charges. Reasoning in your external assistant is accounted separately.
The ordinary usage check requires a positive starting balance, not the eventual cost. Usage can exceed that balance. The remaining balance then shows zero, and the next operation that checks balance is blocked.
Choose a plan or purchase usage credit
Section titled “Choose a plan or purchase usage credit”Use your account’s current prices and enabled features under Subscription plan. Admins get Manage plan for paid plans (Stripe’s customer portal) and Upgrade plan when available (plan picker, then Stripe). Members see past-due warnings but cannot fix billing. An admin must use Manage plan to update payment details.
Only admins can purchase credit. Choose Buy usage credit, select $50, $100 (preselected), $250, $500, or $1,000, then Continue to checkout. Check the selected amount before continuing.
Credit joins the organization’s pool after Stripe confirms payment. It is spent after included allowance and rolls forward until used. Return to Resource usage and confirm the balance. If it is unchanged, wait and reload. An updated balance below the purchase amount reflects uncovered current-period overage, so compare usage before buying again.
Credit does not raise the organization-wide limit on active published workflows, and it does not extend history or restore access. Republishing an already-active workflow consumes no additional slot.
No public CLI or MCP operation buys credit or changes plans. Assistants use account_status for readback and direct admins to the app.
For credential management, see Assistant access and security.