Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.rigbox.dev/llms.txt

Use this file to discover all available pages before exploring further.

Every Rigbox account has limits on workspaces, resources, and AI credits based on your plan tier. This page covers what’s available and how to check your usage.

​
Plan tiers

FreePro
Workspaces210
Apps per workspace520
Max RAM per workspace1 GB4 GB
Max vCPUs per workspace14
Max disk per workspace4 GB10 GB
AI credits / month2502,000
Snapshots per workspace310
SSH keys520
These are representative limits. Check your actual limits with the API - they may differ based on promotions or custom arrangements.

​
Check your limits

Query your current plan limits and usage: 
curl https://api.rigbox.dev/api/v1/users/me/limits \
  -H "Authorization: Bearer YOUR_API_KEY"
The response includes both the maximum allowed and current usage for each resource type. See Get User Limits for the full response schema.

​
Workspace resources

When creating a workspace, you specify RAM, vCPU, and disk allocation. These are validated against your plan limits: 
curl -X POST https://api.rigbox.dev/api/v1/workspaces \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "<WORKSPACE_NAME>",
    "image": "dev",
    "ram_mb": 2048,
    "vcpu_count": 2,
    "disk_size_mb": 4096
  }'
If the request exceeds your limits, the API returns 402 Payment Required with a message indicating which limit was exceeded.

​
Resizing

You can resize a workspace after creation. The workspace must be stopped first: 
curl -X PUT https://api.rigbox.dev/api/v1/workspaces/{id}/resources \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"ram_mb": 4096, "vcpu_count": 4}'
See Update Workspace Resources for details.

​
AI credits

AI credits fund requests through the managed AI proxy. Each credit maps to approximately $0.01 of upstream provider cost, though the exact rate depends on the model and token count.

​
Check your balance

curl https://api.rigbox.dev/api/v1/users/me/credits \
  -H "Authorization: Bearer YOUR_API_KEY"

{
  "remaining": 1800,
  "total": 2000,
  "mode": "managed"
}

​
View usage breakdown

curl https://api.rigbox.dev/api/v1/users/me/ai-usage \
  -H "Authorization: Bearer YOUR_API_KEY"
Returns daily usage broken down by workspace, provider, and model.

​
When credits run out

  • API requests through the proxy return 402
  • Non-AI services in your workspace continue running
  • Switch to BYOK mode for unlimited usage with your own keys

​
Rate limits

API requests are rate-limited per user. Limits vary by endpoint class:
Endpoint classRequests / minute
Authentication120
Workspaces180
Apps240
When rate-limited, the API returns 429 Too Many Requests. Implement exponential backoff in your client: 
import time
import requests

def api_call(url, headers, max_retries=3):
    for attempt in range(max_retries):
        resp = requests.get(url, headers=headers)
        if resp.status_code == 429:
            wait = 2 ** attempt
            time.sleep(wait)
            continue
        return resp
    raise Exception("Rate limited after retries")

​
Capacity

Before creating a workspace, check if the platform has capacity: 
curl https://api.rigbox.dev/api/v1/capacity

{
  "available": true,
  "total": 50,
  "used": 12
}
This endpoint is public - no authentication required. Rigbox also tracks per-node runtime capacity internally, including bridge IP leases for running VMs. Each compute node has 253 active VM bridge IPs available (172.16.0.2 through 172.16.0.254), and stopped or deleted workspaces release their active IP lease.

​
Learn more

Architecture

How the platform is structured

Managed AI Proxy

How credits and the AI proxy work