Plans, billing, usage, and limits

Usable can apply a personal subscription or an organization subscription depending on account context. Prices, included usage, and product limits can change, so use the current billing UI and deployed subscription responses as the authority.

Find the effective plan

Open the relevant billing page:

• personal billing: /dashboard/billing;
• organization billing: the organization's billing page.

The effective subscription resolves whether the signed-in user operates under an organization or personal plan. A feature gate can depend on that effective tier rather than the personal subscription shown elsewhere.

Verify:

• tier name and status;
• billing source: personal or organization;
• current period and next billing date;
• cancellation or pending-change state;
• usage and included allowance;
• invoice list;
• organization member count where billed per seat.

Personal and organization responsibility

Personal subscriptions are managed by the account holder. Organization subscriptions are managed by authorized organization owners, with usage and eligible features applying to members through the organization context.

Organization billing can be quantity/member based. Adding or removing members can affect subscription quantity and proration. Confirm the current checkout or billing summary before approving membership changes.

Do not assume workspace ownership alone grants authority to change an organization subscription.

Plan-gated features

Some controls require a specific plan in addition to a role. For example, released Hosted Zone management requires a Pro organization and organization owner/admin access.

When a feature is unavailable, distinguish:

• plan gate;
• organization role;
• workspace role;
• beta/availability gate;
• unsupported Hosted Zone behavior;
• transient billing-state projection.

Do not broaden user permissions to solve a plan gate.

Read usage correctly

Usage pages can show generation, embeddings, storage, credits, request counts, or organization/member breakdowns depending on the released billing model.

Check:

• measurement unit;
• billing-period dates;
• included amount and consumed amount;
• whether a limit is hard, soft, or informational;
• whether organization allowances scale with member count;
• whether usage is personal or billed through an organization;
• update time.

Do not copy internal conversion constants into user documentation. Use the values displayed by the current environment.

Change a plan

1. Open the correct personal or organization billing page.
2. Confirm you are the authorized billing owner.
3. Review tier, price, interval, included usage, and feature gates.
4. Review member quantity and proration for organizations.
5. Complete the payment flow.
6. Refresh the page.
7. Confirm subscription status, effective tier, billing period, and invoices.
8. Recheck the feature that required the plan.

Billing operations are session-oriented. Do not assume personal access tokens are accepted for subscription changes.

Invoices and payment state

Treat visible subscription and invoice state as authoritative after a change. Draft invoice references can be replaced during recovery and should not be stored as durable integration identifiers.

If a payment or tier change is pending, avoid repeating the action until you have refreshed the current state. Keep payment-provider secrets and card data out of fragments, logs, screenshots, and support messages.

Limits that change

Use these sources in order:

1. current dashboard billing/pricing pages;
2. the deployed API contract at https://usable.dev/api/docs;
3. current subscription/tier responses for the signed-in environment;
4. current public release documentation.

Examples in older fragments can describe a previous billing model. Do not publish a copied price or quota without checking the target environment on the day of publication.

Operational monitoring

Organization owners should review plan state, billing period, usage trend, member quantity, invoices, plan-gated services, and approaching limits. Define who receives billing notifications and who can approve plan changes.

Troubleshooting

Billing data looks stale

Refresh the billing page, confirm the current account/organization, and compare visible tier, period dates, and invoices. Wait for an in-progress payment or projection before repeating the action.

A plan change succeeds but the feature is still gated

Confirm effective tier, organization context, required role, and whether the feature needs a new session or deployment-specific enablement.

Usage is higher than expected

Confirm measurement period, billing source, organization member count, background integrations, and whether the value is cumulative or current-period usage.

I cannot change organization billing

Only the authorized organization role can manage it. Ask the organization owner rather than a workspace owner.

Related pages

• Organizations and membership
• Operate Hosted Zones and Leaf workspaces
• Security, privacy, and data lifecycle
• Requests, responses, pagination, and errors