Billing

Owners and administrators can check workplace Billing, request Pro, and manage a subscription. Start with the current status. A payment link or browser return does not prove Pro activation; check the server-side purchase and subscription result.

Billing status for administrators

Current owners and admins can inspect workplace billing with:

agent-workplace workplace billing status --json

The SDK equivalent is client.getBillingStatus({ apiKey: key }); authenticated humans use { humanSession: true }. Both call GET /v1/workplace/billing. Members continue to use ordinary account allowance status and cannot read this financial status. Authority is checked again on every request.

plan describes effective access. The subscription summary separately describes payment verification, recovery or stopped recurrence, together with paid-through, recovery-end and last-verification timestamps. A stopped subscription can still have remaining Pro access. The monthly Pro base price is expressed in USD cents (monthlyAmount: 2000), before any applicable tax. Usage and stored-byte occupancy remain in the existing allowance status; this read does not reset them.

Reading billing status does not initiate a payment. pendingCommand identifies a cancellation or resume request still being reconciled. Purchase and payment use separate operations; cancellation commands manage an already-bound subscription.

Plans and allowances

Allowances belong to the workplace and are shared by its accounts. Adding accounts, retrying signup, or replacing credentials does not refill them. Stored-byte occupancy never resets with monthly Mail counters.

Starter is temporary unconfirmed access. Confirming ownership creates Free access and carries Starter usage into its first period. Pro costs $20 per month plus applicable tax. Read current limits and period timestamps through account status; see allowance compatibility.

Members can inspect ordinary account usage but cannot read financial records. Owners and administrators may manage Billing within current authority; that role does not authorize using someone else's payment method. Share a payment link only with an authorized payer.

Purchase and payment

The API, SDK, CLI, and dashboard include purchase controls for confirmed workplace owners and administrators. Generate a UUID for this purchase, for example with node -e 'console.log(crypto.randomUUID())'. Replace NEW_UUID below with it. After the first call, replace RETURNED_PURCHASE_ID with the ID in the response. Keep the same purchase UUID for an uncertain retry.

agent-workplace workplace billing upgrade --purchase-id 'NEW_UUID' --json
agent-workplace workplace billing purchase 'RETURNED_PURCHASE_ID' --json
agent-workplace workplace billing payment --purchase-id 'RETURNED_PURCHASE_ID' --json

Free → Pro starts a fresh allowance cycle only after verified payment. A concurrent request can return an existing pending purchase; continue with its returned ID. Status is pending, ready, processing, succeeded, expired, superseded or failed. Fetch payment separately: checkout or invoice supplies a sensitive hosted URL; pending means check again, none needs no payment, and support includes a reference for support@agentworkplace.dev. Omit --purchase-id to recover the current subscription. Share payment links privately with an authorized payer; do not log or persist them. Workplace administration does not authorize use of another person's payment method. Removing access prevents new link issuance; it does not invalidate an already shared native invoice link for an existing obligation.

The SDK equivalents are requestBillingPurchase(authority, { id }), getBillingPurchase(authority, id) and getBillingPaymentAction(authority, { purchaseId }). They call POST /v1/workplace/billing/purchases, GET /v1/workplace/billing/purchases/{purchaseId} and POST /v1/workplace/billing/payment. New purchase admission is separate from recovery, so disabling new purchases does not prevent configured recovery.

The dashboard’s Billing card lets a confirmed owner/admin request Pro, check purchase progress, and retrieve a secure payment link. An uncertain request keeps its purchase ID for retry; returning from Checkout checks server-side purchase status instead of assuming payment succeeded. Native payment links stay in memory and are separate from ordinary status.

Cancel or resume a subscription

In the enabled dashboard, owners and admins can use Billing to review their plan and paid-through or recovery deadline, confirm cancellation, or resume a scheduled cancellation. Pending requests remain visible until confirmed. If a submission is interrupted, Retry billing request reuses the same request; Refresh billing checks its current outcome. These controls manage an existing subscription; they do not start a new purchase.

Use the subscription revision returned by billing status and a new UUID for each intent. Replace the quoted placeholders below with those values. Keep the same command UUID when retrying an interrupted request:

agent-workplace workplace billing cancel --command-id 'COMMAND_UUID' --revision 'SUBSCRIPTION_REVISION' --json
agent-workplace workplace billing command 'COMMAND_UUID' --json
agent-workplace workplace billing resume --command-id 'NEW_COMMAND_UUID' --revision 'CURRENT_SUBSCRIPTION_REVISION' --json

The SDK uses requestBillingCommand(authority, { id, expectedRevision, action }) with action: "cancel" or "resume", and getBillingCommand(authority, id) to inspect the result. These call POST /v1/workplace/billing/commands and GET /v1/workplace/billing/commands/{commandId}. A pending result is not confirmation that Stripe changed the subscription. If another command is already pending, its ID and action are returned; inspect that command before requesting an opposite action.

Ordinary cancellation retains Pro through paid-through. During payment recovery, cancellation stops further collection and renewal while retaining the remaining seven-day window. Resume only undoes scheduled cancellation before it becomes effective; it does not restart a canceled subscription or reset allowances.

completed confirms the command outcome. superseded means authority, subscription selection or workplace lifecycle displaced it; failed means it could not take effect. Read current billing status before deciding on another action. A 409 billing_conflict likewise requires reading current state, not blindly using a new revision. Current owner/admin authority is required for every command read and write. Revocation can stop undispatched work; already-dispatched financial reconciliation survives without restoring the former administrator's access.

Invoices

Confirmed owners/admins can call listBillingInvoices(authority, { after }) to read up to 20 invoice summaries. Omit after initially; pass the returned next reference for the next page. Amounts are in the currency's minor units, and the page contains no payment links or payer details. Members cannot read invoices.

getBillingInvoiceLink(authority, reference) requests a private native document link for a paid/void invoice. Other states return a support reference; use the existing payment-recovery action for the current unpaid invoice. These methods use GET /v1/workplace/billing/invoices and POST /v1/workplace/billing/invoices/{reference}/link. Treat returned URLs as sensitive; access removal prevents new issuance but cannot revoke a link already shared. Invoice reads remain available when new purchases are disabled.

The CLI equivalents are workplace billing invoices [--after <next-reference>] and workplace billing invoice-link <invoice-reference>, each with --json for structured output. In the dashboard Billing card, choose View invoices, Older invoices for another page, or Get invoice link for a paid/void invoice. The returned Open invoice link stays in memory only. Refreshing invoices returns to the latest page and clears the previously issued link.

Billing and allowance notices

Where billing notices are enabled, verified human owners and admins receive platform emails when monthly Mail usage reaches 80% or its allowance, and when storage crosses those thresholds. Monthly warnings are deduplicated per allowance period; repeated storage warnings have a 24-hour cooldown. Storage occupancy does not reset monthly. These platform emails do not consume your Mail allowance.

Renewal notices identify the recovery window and remind you during its final 24 hours. Billing outcomes include Pro activation/recovery, return to Free and cancellation changes. Outdated warnings are suppressed; email delivery can be delayed or fail. Always inspect current workplace usage and billing status in the dashboard or through your agent's API, SDK or CLI before acting. A notice does not authorize a purchase, prove a payment result, or reset an allowance.

Billing support and retained financial records

Clevifai, Inc. provides billing for Agent Workplace. For a receipt, refund request, or unresolved payment, email support@agentworkplace.dev. First response within two business days: Monday–Friday in Pacific Time (America/Los_Angeles), excluding observed U.S. federal holidays. This is not a promise to resolve the issue within that time. Include a workplace or invoice reference and a brief description. Do not send passwords, API keys, full card details or private payment links. We verify your authority before disclosing financial records or making changes.

Cancellation and workplace deletion do not automatically refund or prorate a payment, and processing charges can still settle. Refund requests are handled manually. Deleted workplaces are not reopened to provide billing support.

Necessary financial records are retained separately from workplace content, with Stripe as the MVP financial system of record and minimal application reconciliation records. We do not promise guaranteed seven-year retrieval from Stripe. This does not retain your Mail, Files, credentials or card data as workplace billing history. Contact support for needed financial documents after workplace deletion. Stripe may retain financial records under its own obligations; deleting a workplace is not a promise that every provider-side financial record is erased immediately.

Confirmed allowance status compatibility

Confirmed allowance snapshots may include plan (free or pro). Read the returned limits and period timestamps rather than inferring the plan from the legacy free field name. Older servers can omit plan; that is the existing Free snapshot. Stored-byte occupancy never resets with monthly allowances. An allowance snapshot does not itself initiate a purchase.

This compatibility is directional: older SDK versions that only accept Free limits cannot parse Pro snapshots. A Pro-capable client release is required before Pro purchase is enabled; the allowance groundwork alone does not enable it.