Endpoint
Base URL:https://api.runcomfy.net/prod
The balance lives on the core API host rather than being mirrored on
model-api and trainer-api, because there is only one wallet to report. Authenticate with the same Bearer token used everywhere else — see Authentication.
Get the balance
Request example
Response example
balance_microdollars(integer): Remaining balance in millionths of a US dollar. This is the exact stored value — use it for arithmetic and threshold checks.balance_usd(number): The same figure in dollars, rounded to cents for display.currency(string): AlwaysUSD.
RunComfy stores money as microdollars: 1 USD = 1,000,000 microdollars. Comparing against
balance_usd loses sub-cent precision, so gate automation on balance_microdollars.What the balance covers
The reported figure is your spendable balance across all products. It excludes retired legacy playground packs, promotional credit that is restricted to specific tools, and any pack that has expired — so it matches what the platform will actually let you spend. A zero balance is a normal response, not an error. It means work will be refused until you top up in your Profile.Minimum balances
Products refuse to start work below a floor, so a positive balance is not by itself enough to guarantee a job starts:
Running out mid-run also has consequences: a Serverless deployment that exhausts the balance is disabled and torn down, and a training job stops with a
FAILED status. Polling this endpoint before and during long jobs is the cheapest way to avoid both.
Checking cost alongside balance
Balance tells you what is left; it does not tell you what a run cost. For that, ask the request itself:From an AI assistant
The MCP server exposes this as theget_balance tool, so an assistant can answer “how much credit do I have left?” directly. See Tool Reference.