Usage and limits
RunMat has three weekly allowances. Each one is per person:
| Allowance | What it counts | Free | Professional |
|---|---|---|---|
| MCP client calls | Calls from Claude Code, Codex and other MCP clients that change something | 100 a week | 5,000 a week |
| Agent credits | Work you hand to RunMat Agent | 20 a week | 500 a week |
| Simulation | Floating-point operations in simulation meshing and solving, wherever they run | 50 GFLOP a week | 100 TFLOP a week |
Enterprise allowances are set in the contract. Your model provider may meter its own usage separately; those limits and charges are managed by that provider.
See your usage
Open Usage from the account menu (your initials in the top bar), or Settings › Usage. The You section shows your Agent credits, promotional credits, MCP client calls and simulation allowance for the week. The Organization section shows cloud storage, purchased Agent credits and credits by member. Usage history lists past weeks. Owners and admins see usage for everyone in the organization.
When a cluster is selected in the Run menu, Resources… also shows the simulation allowance you have left.
What counts as an MCP client call
An MCP client call is counted when an agent asks RunMat to change something: editing or creating a file, running code, or starting a study. Running inline code, a Project file or a selected range each counts as one call. A run that returns an error, times out or is cancelled after it starts still counts once; automatic retries of the same call are not counted again.
Calls that only read are not counted:
- installing the plugin or signing in;
- checking RunMat status or limits;
- listing or reading Project files;
- inspecting an existing run result; or
- opening and interacting with a figure that has already been produced.
MCP client calls do not use Agent credits.
Agent credits
Agent credits pay for work you hand to RunMat Agent in RunMat Desktop and the browser. Your weekly credits are used first, then any Agent credit packs your organization holds.
Simulation
RunMat counts the floating-point operations that meshing and solving a simulation perform. A GFLOP is a billion operations, and a TFLOP is a thousand GFLOP. The count is the same on any computer, CPU or GPU, and wherever the work runs: RunMat Desktop, the browser sandbox, the CLI, a compiled program or a cluster. A faster computer doesn't use more. RunMat Simulation Usage Accounting defines how each operation is counted.
Free's 50 GFLOP a week is enough for about 2 to 4 bracket bending studies, or similar thermal studies. Professional's 100 TFLOP a week covers about one complex battery pack study, with multiphysics and a reasonably small mesh. Both depend on the mesh and the physics.
Plain .m code that does not run a simulation isn't counted and works offline. Writing and checking studies, importing geometry, viewing results, reusing an existing mesh or result, and waiting aren't counted either. A new load case solved on an existing mesh counts only its new solving work.
Simulation needs you to be signed in and connected to RunMat, and it does not run offline. The browser sandbox asks you to sign in before it meshes or solves.
Before a run starts, RunMat shows an estimate. Adaptive meshing, nonlinear convergence and iterative solvers can need more work than estimated, so each run has a spending cap, and RunMat asks before it continues past it. After a run, a receipt lists the measured work for meshing, assembly, factorization and solving. A cancelled or failed run uses the work it completed, and a retry after an infrastructure failure doesn't count work again.
An approved academic institution runs simulations without usage charges. Approval follows verification of the institution's eligibility; academic status alone doesn't establish it. Request verification.
Computers and clusters
On Professional, each person can register up to three computers with RunMat Server and use them together as a cluster. RunMat Server refuses a fourth. To use a different computer, remove one from your registered computers to free its slot. Simulation work on any of them uses that person's allowance.
For more computers or larger clusters, Enterprise covers as many nodes as your contract states. Free use has no limit on the number of computers.
Refills
Each allowance refills 7 days after you first use it. The 7 days start with your first call, credit or simulation after a refill, not on a fixed day of the week.
When an allowance runs out, you are not charged automatically. The rest of RunMat keeps working, including plain .m code. RunMat doesn't start new meshing or solving work beyond your remaining simulation allowance. If you want more before the refill, a billing admin can buy a pack.
Packs
| Pack | Price |
|---|---|
| 100 Agent credits | $10 |
| 10 GB of storage | $5 a month |
TFLOP packs add simulation on Professional; their size and price will be listed on the pricing page. Packs are shared across your organization and last 180 days. There is no pack for MCP client calls.
Fair use
To keep RunMat fast and reliable for everyone, RunMat applies reasonable limits on Project storage, file sizes and how many runs can start at once. These limits exist to prevent abuse; normal use doesn't reach them. If you reach one, RunMat tells you what happened, and you can contact us.
To free up space, you can ask your agent to list your Projects, show how much storage each one uses and delete old ones. RunMat asks for confirmation before deleting a Project and its saved revisions and artifacts.