Credits
Verts uses a credit-based billing system. You purchase credits and spend them on file processing operations.
How Credits Work
- Purchase credits - Buy credit packs from the dashboard or via API
- Execute operations - Each operation has a credit cost based on complexity
- Credits are deducted - Credits are deducted when operations complete successfully
Credit Pricing
Credit packs are available in various sizes:
| Pack | Credits | Price |
|---|---|---|
| Starter | 1,000 | $5 |
| Standard | 5,000 | $20 |
| Professional | 25,000 | $75 |
| Enterprise | 100,000 | $250 |
Operation Costs
Operation costs vary based on the action type and input parameters:
| Operation | Base Cost | Variables |
|---|---|---|
| File Inspection | 1 credit | - |
| Image Resize | 2-5 credits | Output size |
| Image Upscale | 10-50 credits | Scale factor |
| Format Conversion | 2-10 credits | Output format |
Use the Calculate Action Cost endpoint to get exact pricing before executing an operation.
Managing Credits
Check Your Balance
View your current credit balance with the Get Credit Balance endpoint:
curl https://api.verts.dev/v1/account/credits \
-H "Authorization: Bearer YOUR_API_KEY"
Response:
{
"credits": 4500,
"low_balance_warning": false
}
Purchase Credits
- Via Dashboard - Go to Settings → Billing → Buy Credits
- Via API - Create a checkout session with Create Checkout
curl -X POST https://api.verts.dev/v1/billing/checkout \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"pack_id": "standard"}'
View Transaction History
Track your credit usage with the Get Credit History endpoint:
curl https://api.verts.dev/v1/account/credits/history \
-H "Authorization: Bearer YOUR_API_KEY"
Low Balance Warnings
When your balance falls below 500 credits, low_balance_warning becomes true in the balance response. Consider setting up monitoring to:
- Alert when balance is low
- Automatically purchase more credits
- Pause non-critical operations
Failed Operations
Credits are only charged for successful operations. If an operation fails:
- Before processing - No credits deducted
- During processing - Credits are refunded
- Invalid input - No credits deducted
Credit Reservations (Async Operations)
For asynchronous operations, credits are reserved when the job is submitted and committed when it completes:
- Submit job - Credits are reserved (held)
- Processing - Credits remain reserved
- Success - Reserved credits are committed
- Failure - Reserved credits are released back to your balance
Related Endpoints
- Get Credit Balance - Check current balance
- Get Credit History - View transaction history
- Get Credit Packs - List available credit packs
- Create Checkout - Purchase credits
- Calculate Action Cost - Get operation pricing