Simmit is a public API for running SimulationCraft in the cloud, enabling you to run and process sims from anything that can make an HTTP request. Discord bots, sites, scripts, whatever you're building.
You submit the same simc inputs you'd run locally, and Simmit runs SimulationCraft for you on managed VMs.
The path of a sim
POST your .simc profile with a preferred build channel (latest, nightly, or weekly). Simmit returns a job ID and a stable URL to track progress.
Simmit scales VMs against queue depth. A cold boot after idle takes about 60s; a warm pool starts sooner.
A worker VM gets assigned your job and pulls the prebuilt binary for the build channel you picked.
SimC runs using your input.
SimC runs in stages using your input, culling weak profilesets.
SimC output artifacts are uploaded to stable URLs: JSON by default, HTML/CSV if you ask for it, plus logs and your input every time. Retained for 30 days.
A job webhook event posts to your endpoint when the job settles. You can also poll the API for job status and final results.
Quick overview
GET /v1/simc/usage under plan.vcpuPerJob.GET /v1/simc/builds lists the current build per channel.runtime.multiStage. Similar to AutoSimC.410 after the retention window.plan.creditsPerSecond). Credits are reserved at job submit, and reconciled to actual runtime on settle.Credit system
A credit is Simmit's unit of compute, metered per second of SimC runtime. The meter starts when SimC starts and stops when it exits, at your account's metering rate (plan.creditsPerSecond). The rate tracks the speed of the machine your sims run on, so credit spend is predictable across different hardware.
The metering exists because of what an API changes. A sim is a compute job on a real machine, and when a person clicks a button to run one, that person is the limit: they only click so often. An API hands the trigger to a script, and the limit goes with it. Your balance stands in for the person. Simmit checks it before accepting a job, reserves the job's maximum cost up front, and settles to actual runtime when it finishes, so a script can only ever spend what's already there.
SimulationCraft does the simulation; Simmit meters the seconds it runs. Credits are only consumed for actual SimC runtime; service orchestration, queue management, build setup, artifact uploads, and every second the pool sits idle between jobs are Simmit's costs.
New accounts start with credits to test against, and verified accounts get a monthly grant on top. Rates and amounts are on Pricing; reservation and settlement mechanics are in How credits work.
Keep reading