> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jinba.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Credits

> How tool executions are metered, who pays for them, and how to check the balance and buy credits in the Jinba Toolbox console

Tool executions in Jinba Toolbox are metered in **credits**. Every organization has its own balance; executions draw from it and purchases add to it.

## How Credits Are Consumed

* **One successful execution costs one credit.** This applies to runs through the REST API, the public endpoints, MCP and the Jinba Flow integration alike.
* **Failed runs are free.** The balance is checked before a run starts, but a credit is only deducted when the run succeeds.
* **Test runs are free.** Running draft code from the tool editor's Test panel does not consume credits.
* **The caller pays.** When an organization executes another organization's public ToolSet, the credit is taken from the caller's balance. Publishing a public ToolSet never costs the provider anything.

Credits never expire.

## Free Credits

A personal organization starts with **500 free credits**. They are added automatically the first time its balance is loaded, and appear in the transaction history as **Free credits**. Team organizations receive no free grant; their members use the team's purchased balance.

## Checking the Balance

The bottom of the console sidebar shows a **Credits** widget with the current balance. Click it to open the **Credits** page, which has three sections:

* **Credit Balance** -- the current balance. A **Low credit balance** warning appears below 100 credits.
* **Purchase Credits** -- the available credit packages (see below).
* **Transaction History** -- every change to the balance, ten at a time with **Load more**. Entries are labelled **Tool execution**, **Credit purchase**, **Free credits**, **Refund** or **Adjustment**.

The balance is also available from the API: `GET /v1/orgs/:orgId/credits`.

## Purchasing Credits

| Package | Price | Per credit |
| - | - | - |
| 1,000 credits | \$10 | \$0.010 |
| 5,000 credits | \$45 | \$0.009 |
| 10,000 credits | \$80 | \$0.008 |

Click **Purchase** on a package to be taken to Stripe Checkout. After payment you return to the Credits page with "Payment successful! Your credits have been added to your account." and the new balance; a cancelled checkout shows "Payment was canceled. No charges were made."

> [!NOTE]
>
> Purchasing requires the **Owner** or **Admin** role. Members can see the balance and history but a purchase attempt is rejected. On deployments without Stripe the page shows "No credit packages available at the moment." instead of packages, and credits are granted by the platform administrator.

## Insufficient Credits

When the balance is lower than the cost of a run, the run is refused before any code executes.

* The REST API and the public endpoints return `402`:

  ```json theme={null}
  {
    "type": "insufficient-credits",
    "title": "Insufficient Credits",
    "status": 402,
    "detail": "Insufficient credits. Current balance: 0, required: 1",
    "currentBalance": 0,
    "required": 1
  }
  ```

* Over MCP, the tool call returns an error result (`isError: true`) whose text is `Insufficient credits. Current balance: 0, required: 1`.

## Related

* [Security & Access Control](/en/pages/toolbox/advanced/security) -- which roles can purchase credits
* [Discovering Public ToolSets](/en/pages/toolbox/console/explore) -- using other organizations' tools with your own credits
* [REST API](/en/pages/toolbox/developer/api) -- the credits endpoint and error format


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.