Billing and Credits
Marketrix tracks each workspace’s included credits and usage within a Billing Cycle.
Billing Cycles
Section titled “Billing Cycles”A Billing Cycle runs for one calendar month from the workspace’s original creation day and time. Its start and end are exact UTC boundaries. Monthly or annual payment intervals and invoice dates do not reset it.
Month-end anchors recover when a shorter month intervenes: January 31 → February 28/29 → March 31.
Plan limits
Section titled “Plan limits”Credits are the per-Billing-Cycle allowance. Applications and concurrent simulations are standing caps, not cycle allowances.
| Package | Applications | Included credits | Concurrent simulations |
|---|---|---|---|
| Free | 1 | 1,000 | 1 |
| Startup | 3 | 10,000 | 5 |
| Growth | 25 | 100,000 | 20 |
| Enterprise | Unlimited | Unlimited | Unlimited |
Every feature is on every plan; plans differ only in these limits, and Enterprise adds RBAC and SSO. Every new workspace starts on Free. See what each plan includes.
Creating an Application past the cap is refused. Starting a simulation past the concurrency cap is not — it waits as Queued until a slot frees.
What uses credits
Section titled “What uses credits”Usage is charged only for measured inference cost, converted into credits at a fixed rate. 10,000 credits are $25, so a credit is $0.0025. Billing shows the credits charged, not the underlying provider cost. Stopped work keeps the credits for measured inference already incurred, and nothing further. A failed User Study or QA Run is credited back in full for that run — you’re not charged for work that didn’t complete.
Usage Credits
Section titled “Usage Credits”Every workspace except Enterprise, Free included, can buy Usage Credits: prepaid credits that keep your work going after the plan’s included credits are used up. Enterprise usage is unlimited, so it doesn’t need them. A workspace admin buys them from the Usage Credits card on the Workspace tab of Settings, through Stripe Checkout, in one of four amounts:
| Amount | Usage Credits | Service fee |
|---|---|---|
| $50 | 20,000 | $2.35 |
| $100 | 40,000 | $4.38 |
| $200 | 80,000 | $8.43 |
| $500 | 200,000 | $20.61 |
$1 buys 400 credits, the same rate as plan credits. The service fee is added on top to cover card processing, and sales tax is added at checkout. Add card saves a card without buying anything, and a purchase also saves the card it was paid with. A saved card pays only for Usage Credits and never becomes the plan’s payment method.
Each Billing Cycle spends the plan’s included credits first, then Usage Credits. Usage Credits carry over from cycle to cycle until used. Work already under way when the balance runs out still finishes, so the balance can dip below zero; a negative balance is paid from your next purchase.
Auto-reload
Section titled “Auto-reload”Auto-reload is off by default. A workspace admin turns it on in the Usage Credits card and picks one of the four amounts. Auto-reload charges the newest saved card when work needs credits after the plan’s included credits are used up. It only reloads while the Usage Credit balance is below 10% of that amount. It buys as many of that amount as it takes to cover any usage that went below zero. There is no monthly spending limit; turn it off to stop reloads.
Auto-reload switches itself off when a reload can’t be completed, for example when a charge is declined or no card is saved. The reason appears in Workspace Activity on the Workspace tab of Settings.
Reaching your allowance
Section titled “Reaching your allowance”Nothing is held back before work starts. Your remaining headroom is the cycle’s remaining included credits plus your positive Usage Credit balance.
A User Study or QA Run pauses instead of failing once both the plan’s included credits and your Usage Credits are used up. Everything it already produced is kept, and it never resumes on its own. To continue, a workspace admin can buy Usage Credits or turn on auto-reload, or you can wait for the next Billing Cycle or upgrade the plan. Then click Resume on a User Study or Resume QA Run on a QA Run. Only the work that never began starts.
Chat, the widget, direct Simulations, and Knowledge don’t pause. Once headroom is used up, starting new ones is refused with a message to buy Usage Credits, turn on auto-reload, or upgrade the plan.
Reading usage details
Section titled “Reading usage details”Usage is attributed to the most specific owner: an Application’s usage is labeled with its name, and work started outside any Application, such as persona work, is labeled Workspace. The current plan and payment method live under Workspace Settings, and this Billing Cycle’s usage meter under Usage.
Token details break a total into buckets that do not overlap — Input (fresh), Cache read, Cache write, Output (text), and Reasoning. They add back up to the Total. Cached and reasoning tokens sit inside the raw input and output counts a provider reports. Showing those raw counts alongside the detail would count the same tokens twice at different prices. A bucket reads as empty when that detail was not captured rather than measured as zero, and a range can state that only some calls reported cache detail.