The Free Tier

One token budget. Included 1×. Frontier 10×. Resets every UTC day.

Every account gets ~300 free tier runs per UTC day (10,000 per month pace) plus **300,000 free tier token units per UTC day** (~10 million per month pace) on platform-provided included models (GLM 4.7 Flash, Gemma 4 26B). Frontier models (GLM 5.3, Kimi K2.7 Code, Kimi K2.6, DeepSeek V4.1 Flash) debit ten times from the same daily token pot.

Bring your own API key (BYOK) and those calls skip the token pot entirely.

How long the allowance lasts

It is a standing term, not a launch offer: no expiry, no campaign end date, refilled every UTC day for as long as the product exists. There is nothing to claim, nothing that runs out, and no clock counting down on it.

That is not the same as saying it can never change. Two things about the band stay revisable, and both are published rather than quiet:

• Its size — the runs and token units granted per UTC day, stated on the pricing page.
• Its model list — which included and frontier models the platform key covers, also on the pricing page, which says "when this list changes, this page changes with it".

A change to either is announced. "Announced" means published on the pricing page in the same release that changes it, not a notice period — we do not promise a number of days' warning, only that a change is never silent. What does not change is the shape: the allowance is refilled daily and is not attached to a promotion that ends.

What counts as a free tier run

A free tier run is a run of a workflow you built and still own, where nothing beyond the run itself can spend platform money. Two things make a run free:

• Your own workflow. You imported it and you hold it. A workflow you bought from someone else is paid at its listed price; the allowance never covers another builder's run fee.
• No platform money at risk beyond the run. Your own API keys skip the platform entirely, so those calls are always outside the meter. Included models on the platform key draw on the daily token units described above. A workflow stays inside the allowance when that model is its only connection. Use the OpenRouter Chat Model node and attach no OpenRouter key of your own. Any other step that needs a credential — whoever supplies that key — or a workflow that pauses for a human approval, means the run is billed from your Workflow balance instead.

Runs that do not count toward the free allowance:

• Runs of workflows you bought — those pay the builder's listed price.
• Trial runs — the builder sponsors these; you pay nothing and the counter does not move.
• Pay-as-you-go runs — someone else's system pays per call; the allowance is yours, not theirs.
• Resumed runs — a Send-and-Wait resume is billable in full.
• Runs paid from your prepaid balance — when you choose to pay rather than use the allowance, the run is not free.

Scheduled and webhook runs of your own workflow both draw on the same daily counter. The check is per-execution, not per-trigger.

How the counter works

The allowance is a day-bucketed counter in your account storage, keyed by (wallet, UTC day). The day resets at 00:00 UTC, not at midnight in your local timezone. A run that crosses 00:00 UTC is charged against the day it started.

• ~300 free tier runs are granted per UTC day (~10,000 per month pace).
• Unused runs do not roll over — a quiet day does not double the next day's allowance.
• The counter shows on your producer dashboard as runsRemainingToday.
• Each execution page says how many free tier runs you have left after that run.

What happens at 0

When the counter reaches zero, on-demand runs continue to work normally — they just cost your prepaid balance or your credit card on-ramp. The allowance is a discount, not a cap. You cannot exceed your daily free allowance; you simply stop getting the discount once it is exhausted.

Past the allowance on a Workflow balance. For workflows you own, each run past the daily ~300 (a webhook run or a scheduled run alike) costs $1 per 10,000 from your Workflow balance — not the workflow's listed price. That covers the run itself. Your own API keys are never billed back to you, but AI calls on included models — past today's token units — are billed at published token rates ($0.15 / $1.50 per 1M) on top. Top up in USDC; deposits are 1:1.

Keep a working balance, not just the cost of one run. Before each AI call on an included model, the platform sets aside the most that single call may cost, and returns what the call did not use as soon as it finishes. A balance smaller than that amount is refused at the first AI call, even though the call itself costs far less.

Scheduled workflows behave differently. A scheduled workflow activated under the allowance waiver with no Workflow balance still draws from your daily free counter. On the 301st fire in a UTC day, the run falls through to the Workflow balance; if the balance is also dry, the schedule is deactivated with status insufficient-budget. The same happens when the day's free tier token units are spent on a workflow that uses an included model: the fire falls through to the Workflow balance, and a balance that cannot cover it deactivates the schedule. The schedule does not fall back to your prepaid balance or card on-ramp for autonomous fires. To resume, top up the workflow's Workflow balance and press Reactivate from the dashboard.

The allowance has a platform-wide daily breaker that counts grants only (not denials). On a heavy day the platform can refuse new grants once the global cap is hit, but that affects only the granting of free runs — paid runs always work. Scheduled and webhook runs both count toward it.

Why scheduled runs are included

The allowance covers your own workflow however it fires. A scheduled run and a webhook run of the same workflow are the same run to the meter, because neither costs the platform anything beyond the run itself.

A scheduled run that would need a platform key outside the free tier model band skips the allowance and bills the Workflow balance. There is no free run that spends platform money beyond the run and the daily token units.

Frequently asked

Does the allowance work in trial mode? The allowance and the trial are separate systems. A trial run is Builder-funded and free regardless of the allowance counter.

What if I run out at 23:55 UTC? The next free tier run is the following day at 00:00 UTC. There is no grace period; the bucket boundary is sharp.

Can I see the counter from the API? Yes — GET /api/v1/users/:address/stats returns runsRemainingToday for the current UTC day. The MCP equivalent is in the user-stats tool.

Is the allowance per wallet or per account? Per wallet (the address you sign in with). Two wallets under the same person get two separate daily allowances.