Billing & Pricing

Early Beta Access allowances and how limits behave, plus reference for the planned Production, Growth, and Enterprise plans, which arrive after the beta.

The current terms are always the ones the API reports: GET /api/v2/public/pricing-policy (unauthenticated), the pricing page, and Settings → Plan & Billing in the console. They are read from the API’s release setting, so they match what the API enforces. This page explains Early Beta Access, the terms in force while mode is early_beta.

While Early Beta Access is active, Anlyon is free within hard limits, with no credit card, no subscription, no automatic upgrade, and no overage charges. Paid plans arrive after the beta. See the beta policy for the full terms. Nothing on this page converts, charges, or resets a workspace when the terms change.

Early Beta Access

Every workspace starts on the Free plan with these allowances:

Halt, isolation, and approvals are included. So are environment protection, controlled promotion between environments, and the email notification channel. A new workspace starts with one protected environment of kind production, and you can create staging and development kinds up to the total. There are no separate charges for traces, spans, or approval decisions. Other rate, retry, payload, and resource limits are unchanged from the standard Free plan: 30-second delivery timeout, 1 MiB payload, up to three retries, and 300 requests per minute per workspace, counted in one-minute windows.

Resets versus persistent limits

• Reset monthly at 00:00 UTC on the first of each month: action executions, egress and email alerts.
• Do not reset: combined storage, seats (including pending invitations), environments, and action definitions. These are limits on what you hold. They free up when you remove things.

When you reach a limit

Requests stop at a hard limit and return the machine-readable error QUOTA_EXCEEDED. Nothing is charged, and nothing is upgraded automatically.

There is no guaranteed response time and no guaranteed limit increase. Inspecting and deleting your own data always works.

Verified accounts and pauses

Costly operations (memory processing, hosted action execution, and file or cache writes) require a verified workspace owner email. If we ever have to protect the service, new expensive work can be paused platform-wide and returns EXPENSIVE_WORK_PAUSED (HTTP 503). Signing in, viewing, and deleting your data keep working while paused.

Usage and alerts

Use the console’s Settings → Plan & Billing and Settings → Usage pages, or:

• GET /api/v2/billing/plan: current limits, subscription status, and access: the workspace’s mode (early_beta or standard), whether paid plans can be bought (paidPlansAvailable), the next UTC reset (usageResetsAt), and overageBilling: false / automaticCharges: false during beta.
• GET /api/v2/billing/plans: available plans, allowances, and prices. Paid plans report purchasable: false until paid plans open.
• GET /api/v2/billing/quota: execution, message, storage, and egress allowances.
• GET /api/v2/billing/usage/current: current usage.
• GET /api/v2/billing/budget: workspace overage alert configuration.
• GET /api/v2/public/pricing-policy: unauthenticated. The platform’s current mode and published allowances, used by the public pricing page.

The quota response adds allowances with includedUnits, usedUnits, overageUnits, and projectedOverageCents. During Early Beta Access every dimension is a hard cap, so overageUnits and projectedOverageCents are zero.

Per-key budgets and safety controls are separate admission controls. They are not invoices, and they do not cap the money an approved action moves, model tokens, or all downstream delivery work.

Planned paid plans

The plans below are planned and arrive after the beta. The prices are not guaranteed and may change before paid plans open. This reference is kept so you can see what is intended.

The Free column is the standard Free plan that applies once Early Beta Access ends. During Early Beta Access a workspace has the allowances at the top of this page, with environment protection, controlled promotion and email alerts included.

Planned overage, for paid plans only:

A confirmed outbound response counts as an execution, including a non-2xx destination response. Halt-blocked requests, validation failures, denied or expired approvals, and other never-dispatched attempts do not count. Uncertain timeouts stay reserved but uncounted until reconciled. A replay does not add another execution.

Anlyon Vigil reviews and approvals have no overage on any plan. They are hard caps: at the limit, approvals still reach people, without a suggestion.

Change your plan

Until paid plans open, the console shows no checkout, and the API refuses the request before any payment system is contacted:

{
  "success": false,
  "error": {
    "code": "PAID_PLANS_UNAVAILABLE",
    "message": "Paid plans arrive after the beta. Nothing was charged. Your workspace keeps its Early Beta allowances."
  }
}

POST /api/v2/billing/upgrade (owner session) and POST /api/v2/billing/create-setup-intent return this with HTTP 403 for any workspace without an existing subscription. Going back to Free is never blocked.

When paid plans open, choosing Production or Growth in the console collects payment details with Stripe Elements. A workspace receives paid access only after the subscription becomes active, and adding a card alone never upgrades a workspace. POST /api/v2/billing/upgrade takes { "plan": "production", "paymentMethodId": "pm_example" } and may return a clientSecret requiring payment confirmation. Do not treat an incomplete subscription as paid access. Enterprise is contact-sales only. The earlier paygo identifier remains readable but cannot be purchased.

Existing subscriptions are unaffected: invoices (GET /api/v2/billing/invoices), card updates, and cancellation (POST /api/v2/billing/cancel, effective at the billing-period boundary) stay available.

See the beta policy for how paid plans will be introduced, and the error-handling guide for quota responses.

Allowances for earlier namespaces

The namespaces that predate governed actions keep their own allowances during Early Beta Access. They apply to existing workspaces that still use them.

Durable messages and the memory-processing allowance reset at 00:00 UTC on the first of each month. Memory storage and stored memories do not reset. They free up when you remove memories. When memory processing reaches its allowance, wait for the reset. Existing data is kept and stays readable.

Memory processing

There is no public embedding-token or LLM-token charge, and no token meter. Memory and semantic-cache processing run against an internal provider-cost allowance ($0.25 per month during Early Beta Access). Larger inputs and model-assisted processing use more of it, so it is not a promise of unlimited operations. When it is reached, processing stops until the next UTC month. Stored memories are not deleted. Pending file uploads reserve storage capacity until confirmed or cleaned up.