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. Trials, monthly or annual payment intervals, invoice dates, and trial expiry do not reset it.
Month-end anchors recover when a shorter month intervenes: January 31 → February 28/29 → March 31.
Included credits
Section titled “Included credits”Each package includes this allowance per Billing Cycle:
| Package | Included credits |
|---|---|
| Free | 1,000 |
| Startup | 10,000 |
| Growth | 100,000 |
| Enterprise | Unlimited |
A Growth annual agreement may show a clearly labelled annual net contract allocation divided by 12. This is a monthly allocation of the annual commercial reference, not a change to the Billing Cycle. Enterprise deal value and profitability remain unknown unless they are supplied. Neither case promises profitability.
What uses credits
Section titled “What uses credits”Usage is charged only for measured inference cost, converted at 480 credits per USD (a 20% markup on the dollar cost incurred). Billing shows the customer credit charge without disclosing Marketrix’s provider cost. Failed or stopped work still uses credits for measured inference already incurred, and nothing further.
Reservations and settled usage
Section titled “Reservations and settled usage”Before provider-backed or otherwise deferred work begins, Marketrix temporarily reserves a conservative maximum credit amount. This hold prevents work from starting when the available balance cannot cover its possible usage.
Active reservations are shown separately from settled usage. When reserved work settles, its charge reflects proven completed usage and any unused reserved credits are released.
Reading usage details
Section titled “Reading usage details”Usage is attributed to the most specific supported owner:
- Workspace services is work genuinely shared across the workspace rather than owned by one Application.
- Unattributed legacy usage is historical usage whose ownership cannot be proven.
Token details use ↑ Input for the number of input tokens and ↓ Output for the number of output tokens. Older ranges can explicitly show incomplete token coverage when complete counts are unavailable.