Direct MU pricing
The current display catalog derives package value from the configured $0.05 selling price per Matrix Unit.
Usage / top-ups
Add capacity without turning usage into a mystery.
Top-ups are planned as bounded prepaid Matrix Unit packages. The launch catalog is transparent about price, package size, and whether purchase is actually enabled.
Prepaid and bounded
A future checkout should add a defined package to a workspace without creating an open-ended spend path.
No simulated checkout
The current API reports purchaseEnabled=false until payment capture and subscription controls are approved and integrated.
Usage still reconciles
Top-up balance does not change the live metering rules: reserve, measured work, and terminal settlement remain visible.
Direct MU pricing
The current display catalog derives package value from the configured $0.05 selling price per Matrix Unit.
Prepaid and bounded
A future checkout should add a defined package to a workspace without creating an open-ended spend path.
No simulated checkout
The current API reports purchaseEnabled=false until payment capture and subscription controls are approved and integrated.
Usage still reconciles
Top-up balance does not change the live metering rules: reserve, measured work, and terminal settlement remain visible.
The workflow
From one URL to evidence you can act on.
- 01
Choose a package
Review Matrix Unit quantity, one-time display value, and the workspace plan context.
- 02
Confirm the payment path
Only an approved payment integration should capture funds or add balance.
- 03
Use with live metering
Runs continue to drain authoritative measured usage and release unused reserve.
Current catalog values
The backend display catalog currently exposes 250 MU for $12.50, 500 MU for $25.00, 1,000 MU for $50.00, and 2,500 MU for $125.00 when the configured selling value is $0.05 per MU. The catalog is intentionally derived from the pricing snapshot rather than hard-coding a conflicting credit conversion.
For the underlying unit model, read the Matrix Units guide and compare monthly Free and Starter allowances.
Why a top-up is not a promise of unlimited runs
A top-up adds usage capacity; it does not make a run free, fixed-price, or unlimited. The actual charge still follows measured work and the run’s failure policy. Unused holds are released, while qualifying infrastructure failures can receive correction treatment.
Teams planning larger workloads should first understand Standard Adaptive coverage and worker capacity boundaries.
The safe launch boundary
The public page can explain package value now, but it must not imply that a payment was captured or balance was added when the payment provider is not connected. The product therefore exposes a display-only catalog and a clear unavailable state rather than a fake checkout button.
Explore the QA library
View all capabilitiesFind the testing guide that matches your next question.
Questions teams ask
Can I buy a top-up today?
The current backend catalog is display-only and reports purchaseEnabled=false. Checkout should be enabled only after an approved payment integration is connected.
Are top-ups priced in dollars or internal cost?
The customer-facing catalog uses the configured selling value per MU. Private provider and infrastructure cost data is not exposed.
Do top-ups change failed-run treatment?
No. Failure treatment remains based on authoritative measured work, released reserve, and qualifying infrastructure incident correction.
Turn your next deploy into a proof, not a guess.
Start with one authorized URL. Matrix QA walks the journey and returns the evidence your team needs to decide what ships.