> For the complete documentation index, see [llms.txt](https://docs.robincompute.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.robincompute.org/core-concepts/credits.md).

# Credits

RobinCompute bills inference in credits. A credit is worth exactly $0.01 USDG: you buy credits with USDG, then spend them on requests.

Credits exist to separate everyday spending from on-chain settlement. Rather than your wallet prompting for a USDG transfer on every message of a conversation, you deposit once and draw the balance down across as many jobs as you like. No per-message approvals.

***

## Properties at a glance

| Property         | Value                                                     |
| ---------------- | --------------------------------------------------------- |
| Value            | 1 credit = $0.01 USDG                                     |
| Purchased with   | USDG (ERC-20) on Robinhood Chain                          |
| Transferable     | No; credits are bound to the purchasing wallet            |
| Expiry           | Never                                                     |
| Minimum purchase | 100 credits ($1.00 USDG)                                  |
| Refundable       | Yes; unspent credits can be withdrawn as USDG at any time |

Non-transferability is a design choice, not a limitation. It rules out a secondary credit market and keeps the accounting trivial: one wallet, one balance.

***

## Funding your balance

**In the web app:**

1. Connect an Ethereum wallet (MetaMask, Rabby, or Robinhood Wallet) at `robincompute.org/app`
2. Choose "Add credits" in the top navigation bar
3. Enter how much you want
4. Confirm the USDG transaction in your wallet

Your USDG goes straight to the `job_escrow` contract, which books the balance under your wallet address. RobinCompute sponsors the deposit's gas through ERC-4337, so you never need ETH. Robinhood Chain confirms blocks every \~100ms, so the balance typically reflects the deposit within a second.

**Through the API:** There is no purchase endpoint. Credits are funded from the web app or with a wallet payment QR.

**With a payment QR:** The purchase screen can generate an EIP-681 payment QR code for any compatible mobile wallet. Scan it and the exact USDG amount and the `job_escrow` deposit address are pre-filled.

***

## Pricing tiers

| Tier     | Model range                 | Cost per request   |
| -------- | --------------------------- | ------------------ |
| Lite     | 1B to 3B parameter models   | 2 credits ($0.02)  |
| Standard | 7B to 8B parameter models   | 8 credits ($0.08)  |
| Pro      | 13B to 27B parameter models | 18 credits ($0.18) |
| Max      | 70B+ parameter models       | 40 credits ($0.40) |

These per-request prices cover completions up to roughly 500 output tokens. Beyond that, billing switches to a rate per 1,000 output tokens:

| Tier     | Per 1,000 output tokens |
| -------- | ----------------------- |
| Lite     | 1 credit ($0.01)        |
| Standard | 4 credits ($0.04)       |
| Pro      | 9 credits ($0.09)       |
| Max      | 20 credits ($0.20)      |

Whatever a request costs is locked in escrow up front. A failed or timed-out job returns the locked credits to your balance with no action on your part.

***

## Checking your balance

**Dashboard:** The web app shows your balance in the top navigation bar, always.

**API:** Call `GET /v1/account` with your API key. You get back `credits_remaining` and `usdg_value`.

```json
{
  "wallet": "0x7c41f9b8d2a6e3054cf18a9b62d47e0c93f5a1b8",
  "credits_remaining": 1420,
  "usdg_value": 14.20,
  "last_topup_at": "2026-06-15T09:43:00Z"
}
```

**On-chain:** The balance itself lives in the `job_escrow` contract, keyed by your wallet address. You don't have to take our dashboard's word for it: query the Robinhood Chain JSON-RPC directly (`https://rpc.mainnet.chain.robinhood.com`), or look it up on Blockscout at `robinhoodchain.blockscout.com`.

***

## Low balance alerts

Set a threshold and a webhook fires whenever your balance dips under it; the event is `credit.low`, documented on the \[Webhooks]\(

) page.

In the web app, a warning banner appears once you fall below 100 credits.

***

## Getting unused credits back out

Credits are not a one-way door. To turn leftovers back into USDG:

1. Open Settings in the web app
2. Choose "Withdraw credits"
3. Enter an amount, or withdraw everything
4. Confirm the transaction in your wallet

One transaction moves the USDG out of the `job_escrow` contract and back to your wallet. No withdrawal fee, and ERC-4337 sponsorship covers the gas.

***

## Credits vs $RCOMPUTE

Two unrelated instruments, two different jobs.

|           | Credits                              | $RCOMPUTE                         |
| --------- | ------------------------------------ | --------------------------------- |
| Purpose   | Pay for inference jobs               | Stake, govern, earn protocol fees |
| Value     | Fixed at $0.01 USDG                  | Market price                      |
| Earned by | Purchasing with USDG                 | Providing compute, staking        |
| Spent on  | Inference requests                   | Staking (locked, not spent)       |
| On-chain  | Balance in the `job_escrow` contract | ERC-20 token balance              |

Using RobinCompute requires no $RCOMPUTE, and providing compute requires no credits. The two never intersect.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.robincompute.org/core-concepts/credits.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.