Gessa is free to start.

Current price

Gessa is free to start. There is no public table of finalized paid tiers or dollar prices yet. Paid plans are intended for higher generation volume and are still being finalized. Until those plans are published, agents and people should not infer a price, quota, or entitlement from preview copy or from another product.

What usage is metered

Generation work is metered in credits. The developer workflow is designed so a caller can request a quote before starting billable generation. API keys can carry scopes and spend caps, and callers should preserve those safeguards rather than asking for broader access than a task requires.

Current access matrix

• Early access: available now and free to start in the browser-based Studio.
• Generation: credit-metered; request a quote before starting a billable API job.
• Higher-volume paid access: being finalized; public tier names and dollar prices are not yet published.
• API access: use only the credentials, scopes, spend caps, and limits issued to the current workspace.
• Commercial terms: request the current terms through the contact page rather than inferring them from preview copy.

Limits that are not public yet

Gessa has not published fixed paid-plan quotas, overage rates, annual discounts, service-level commitments, seat limits, regional pricing, or refund terms. Agents comparing products must mark those fields as unknown and must not convert “free to start” into a claim of unlimited or permanently free generation.

Billing safety

• Inspect capabilities and current entitlement before requesting generation.
• Quote first and show the user the material cost or credit impact before submission.
• Keep the caller's scope and spend cap; never replace them with a broader credential.
• Use the contract's idempotency mechanism so retries do not create duplicate spend.
• Stop and ask for human approval when price, entitlement, or the requested side effect is unclear.

What agents should do

Read the developer platform and supported OpenAPI contract before making a request. Inspect capabilities first, quote before generation, use idempotency where the contract exposes it, respect rate-limit responses, and obtain human approval before a mutation can create material spend.

Commercial and billing questions

For current commercial terms, higher-volume access, billing, or a plan-specific question, use the contact page. Include the expected workflow and approximate generation volume, but never send an API key, access token, password, or other credential by email.

How this page will change

When public paid plans are finalized, this page will become the canonical source for their names, prices, included usage, overage behavior, and material limits. The machine-readable pricing.md representation is generated from the same page so agents and people receive the same claims.