Know the boundary before starting
A bounded trial should make both the request allowance and the work outside it clear. Free includes 50,000 authorised memory operations per month and 256 MB retained-memory capacity. No payment checkout is needed to activate it. Prices and standard/launch terms remain on pricing.
Memory request accounting
One authorised remember, recall or agent-context request counts as one memory operation, including a context-cache hit. The quickstart makes three. The normal evaluation runner makes seven billable memory requests and two forget calls; retries or additional checks can change that total.
After the allowance, self-serve requests consume purchased prepaid credit at $99 per million memory operations. With no usable credit, a billable request returns HTTP 402 before the memory operation proceeds. Automatic top-up is disabled until a payment method is configured and the workspace explicitly enables it. Enabled top-up can purchase additional packs: turn it off before treating the wallet as your spending ceiling. Free exhaustion does not silently activate a paid subscription or a postpaid invoice.
For a zero-spend test, use Free, leave top-up disabled and purchase no credit. A credit pack's checkout amount and its usage consumption are different: for example, 100,000 Free-plan operations use 50,000 included operations and $4.95 of already-purchased credit. Buying a Starter pack requires its full $100 checkout amount. Taxes may apply. Credits and any expiry are shown in billing.
Retained memory is a separate plan-capacity allowance. The self-serve published plans currently configure no per-GB overage price; do not assume a storage overage can be bought at the operation rate. Ask for the capacity your workload needs. Enterprise capacity and charges are contract-specific.
Consequence and model costs
The published memory operation definition covers the three memory routes above. Consequence planning, simulation, decision, approval and observation are separate routes; the current runtime does not debit them through that memory-operation meter. Do not estimate a consequence workflow by multiplying every HTTP call by the memory rate, or assume that this is a permanent all-inclusive price for every future workload.
The Free support-escalation example uses generic planning, zero planner model calls, bounded scenarios and no industry pack. maxModelCalls and maxCostEstimate are run-policy bounds, not a universal monetary cap on third-party providers, automation or enabled prepaid top-up. Your own model calls and external tools remain separately billed by their providers. Confirm a production consequence workload's commercial terms before relying on it.
Choose a plan-qualified evaluation
| Test | Starting point | Additional requirement |
|---|---|---|
| Remember, recall and forget synthetic support preferences | Free; REST or supported integration | Backend authorisation and secret handling |
| Generic bounded plan, decision and outcome records | Free decision example | No Enterprise pack; execution stays disabled |
| Install built-in industry knowledge packs | Enterprise | Workspace installation authority |
| Export workspace audit evidence | Pro or Enterprise | Ask support for sanitised samples or agreed evaluation access |
| Regional placement hints | Pro or Enterprise | Best-effort; not legal residency |
| Jurisdictional durable-storage profile | Enterprise | Supported configuration and contractual review |
The existing industry-specific end-to-end guides explicitly begin with an Enterprise pack. Use the Free generic example when that pack is unnecessary; do not assume the exact industry reference works on Free. Requests for a paid-control demonstration do not automatically upgrade a workspace or create an account. Ask for an evaluation review before committing budget.