Skip to main content
Esheria uses workspace credits across API, CLI, and MCP traffic. Credits are a workload/value unit—not LLM tokens—and the same plan, pack, feature, rate, and balance controls apply on every surface.

Production Plans

Enterprise plans include contracted support, throughput, SLA, and data-rights terms. Taxes, premium/custom content, and negotiated services may be additional.
Existing balances are grandfathered. Esheria does not remove or retroactively debit credits when publishing a new catalog or pricing rule.

Top-up SKUs

Use esheria billing plans or GET /api/v1/billing/plans as the source of truth. The response includes exact prices, available SKUs, workspace plan and pack policy, and the active pricing-rule catalog.

Checkout

Checkout accepts one server-owned SKU. You cannot submit the price, credits, quantity, grant expiry, plan, or entitlement.
The API creates an internal order before redirecting to Stripe. Payment webhooks validate the Stripe Price and line item against that order. Credit grants never come from browser, CLI, or Checkout metadata values.

Metering

Production pricing version: 2026-07-14-v2. The API reserves credits before work starts, charges successful work once, and releases failed requests. Usage rows retain every referenced pack, the pricing rule/version, request and response units, final charge, and trace_id. An in-process reconciler releases stale reservations and safely reclaims due or interrupted Stripe events.

Entitlements And Replays

  • Workspace settings choose the packs available under the plan.
  • A token inherits those packs by default or narrows to a subset.
  • Every pack in a multi-pack graph/customer request is checked.
  • Full export and hosted operator workflows also require plan features.
  • Authentication and current authorization run before an idempotent response can be replayed. Replay records are isolated by workspace and token.

Renewals, Refunds, And Disputes

Recurring invoice credits are derived from Stripe Price-to-plan mappings and granted once per paid invoice, including concurrent duplicate deliveries. Failed and stale-processing Stripe events remain retryable. Self-service Checkout refuses a second current subscription for the same workspace. Refunds reverse the proportional credits tied to the refunded payment. Disputes temporarily reverse the affected value. If those credits were already used, Esheria records credit debt instead of directly consuming an unrelated grant. A won dispute clears that debt first and restores any remaining credits.

Errors

MCP intentionally does not expose billing mutation, Checkout, or token management tools. Configure billing and tokens in the Dashboard or CLI first.