Credits and caching

Tessryx doesn't charge per request or per page view. It charges for compute (the work of actually running your logic), measured in credits. Understanding the model takes two minutes and saves you from ever being surprised by a bill.

#What a credit is

A credit pays for an execution: running your logic once. That's a page render, an API route answering a request, a scheduled job, a test run in the editor, or your agent doing work over MCP. However it's triggered, the work is what costs; a credit covers up to 10 seconds of it, rounded up.

Most executions are tiny. A typical page render finishes in milliseconds, so it's one credit. Something heavy (a big fan-out, an AI step) uses more, and concurrent iterations each count. Each plan includes a monthly pool of credits; see Plans and limits for the numbers.

#Two things are always free

• Building. Drafts, edits, and unpublished versions: saving your work never costs a credit. You spend only when logic actually runs: live traffic, scheduled jobs, and the previews or test runs you trigger in the editor (those execute the real workflow, see below).
• Cached views. This is the big one.

#Caching is the lever

When a page has a cache window, the first visit runs the workflow and the result is stored at the edge. Every visit within the window is served from that stored copy, instantly, and for free. The workflow only runs again when the window expires.

The effect is dramatic. A marketing page cached for an hour runs a handful of times a day no matter how much traffic it gets, so it costs almost nothing and shrugs off spikes. The trade-off is freshness: a cached page can be up to its window out of date. Your agent sets a sensible window per page; pages that must be live-to-the-second simply cache for zero.

A good pattern is to cache the page shell hard and load the fast-changing bits (a price, a count) separately, so the page feels live without re-running the whole thing. Your agent builds this for you where it helps.

What still costs credits: cache misses (the first visit, or after a window expires); form submissions and other actions (these are never cached); scheduled runs; the previews and test runs you trigger in the editor (they execute the real workflow, and can have side effects like sending email); and runs that fail. A run is metered whether it succeeds or errors, so a broken workflow still costs each time it runs.

#If you run out

You are never billed for overage. Credits are prepaid, and if you exhaust them, live runs simply pause until you top up or upgrade (restored instantly, with nothing deleted and nothing owed). Cached pages and published files keep serving in the meantime. Running low prompts you to act; it never charges you automatically.

Credits have expiry rules (a month's allowance, and any top-ups you buy). The exact terms are in Plans and limits and the Billing Policy.