Credits (Dollarinos)
Dollarinos (Ds) are the compute credits used to run skills on clanker.engineer.
What are Dollarinos?
Dollarinos are in-app compute credits with no monetary value. They’re used to pay for AI processing when executing skills.
Note: Dollarinos are purely for tracking compute usage within the platform. They cannot be exchanged for real currency.
Subscription Tiers
| Mode | Monthly Ds | Price | Pack Discount |
|---|---|---|---|
| BYOK Mode | — | $0 (own key) | — |
| PAYG Mode | — | $0 (buy packs) | — |
| Based Mode | 2,000 Ds | $29/month | 20% off credit packs |
Sign-up is with GitHub, and every mode needs a card on file before it can run anything — BYOK included. There is no free compute: a new account starts in BYOK Mode with no credits, and the card is saved with a $0 setup, not charged.
Cost Calculation
Execution costs are based on token usage, at the rate for the model that served each call. The table below is the fallback rate, used for a model with no rate of its own; most models are cheaper per token.
| Token Type | Fallback cost |
|---|---|
| Input tokens | 1 Ds per 1,000 tokens |
| Output tokens | 5 Ds per 1,000 tokens |
| Minimum balance required to start | 10 Ds |
Example
For an execution with:
- 2,000 input tokens
- 5,000 output tokens
On the fallback rate, cost = (2,000 / 1,000 × 1) + (5,000 / 1,000 × 5) = 2 + 25 = 27 Ds
The result is rounded up to whole Ds: 27 Ds.
How usage is measured
Execution usage is metered where model calls leave the sandbox, from the token usage the model provider reports for each call — not from what the running skill says it used. A skill cannot lower its own bill.
- Failed, cancelled and timed-out runs are charged for the model calls they actually made before they ended. Only two kinds of run are free: runs that use your own provider key (BYOK), and runs that made no model calls.
- If a response’s usage cannot be read, that call is charged a conservative default instead.
- Cached input tokens are weighted rather than charged at the full input rate: cache reads count at 10% and cache writes at 125% of the input rate.
- Chat is billed per model step as it happens, not once at the end. A turn that errors, or stops to wait for your approval of a tool, is still billed for the steps it completed.
Checking Balance
Via Mobile App
Your balance is shown in the header of the app and on the Account screen.
Via MCP
{
"tool": "get-credit-balance",
"arguments": {}
}
Via REST API
GET /api/v1/billing/balance
Response:
{
"balance": 450,
"totalSpent": 150,
"canExecute": true,
"isAdmin": false
}
Purchasing Credits
Need more Ds? Purchase additional credit packs:
| Pack ID | Dollarinos | Price | Savings |
|---|---|---|---|
pack_100 | 100 Ds | $1.00 | — |
pack_250 | 250 Ds | $2.25 | 10% |
pack_500 | 500 Ds | $4.25 | 15% |
pack_1000 | 1,000 Ds | $8.00 | 20% |
pack_5000 | 5,000 Ds | $37.50 | 25% |
Via Mobile App
- Go to Account > Credits
- Select a pack
- Complete purchase via Apple Pay or credit card
Via REST API
POST /api/v1/billing/purchase
Content-Type: application/json
{
"packId": "pack_500",
"email": "[email protected]",
"successUrl": "https://next.clanker.engineer/payment-success",
"cancelUrl": "https://next.clanker.engineer/payment-cancel"
}
Balance Reservation
When you start an execution:
- System estimates the maximum cost
- Reserves that amount from your balance
- After completion — including a failed, cancelled or timed-out run — charges the actual cost of the model calls made
- Returns unused reservation
This prevents overdrafts during long executions.
Monthly Reset
Based Mode subscribers receive their monthly allocation on the 1st of each month:
- Unused Ds do not roll over
- Purchased packs do roll over
- Balance = Monthly allocation + Purchased packs
Transaction History
View your credit transactions:
Via REST API
GET /api/v1/billing/transactions
Response:
{
"transactions": [
{
"id": 1,
"type": "execution",
"amount": -27,
"description": "README Generator execution",
"createdAt": "2024-01-15T10:31:30Z"
},
{
"id": 2,
"type": "purchase",
"amount": 500,
"description": "500 Ds",
"createdAt": "2024-01-10T14:00:00Z"
}
]
}
Low Balance Handling
When your balance is insufficient:
- Execution is rejected with
INSUFFICIENT_CREDITSerror - You’ll receive a push notification (if enabled)
- Purchase a pack or wait for monthly reset
Best Practices
- Monitor usage - Check balance regularly in the app
- Optimize prompts - Shorter, focused prompts cost less
- Check before executing - Verify balance before large executions
- Review transactions - Understand where your credits go