DocumentationBilling and Credits
Learn how API requests are charged and how credits are calculated based on payload size.
This document explains the billing model and how credits are deducted when you execute transformation requests via our API or the platform.
Standard Pricing
The core metric for our billing system is Credits.
For most standard use cases, 1 API Request = 1 Credit.
When you send a POST /api/v1/transform request to process your JSON or XML data, the system evaluates the complexity and size of the request. By default, a single execution deducts exactly 1 credit from your account's balance.
AI Mapping Suggestion
Using the AI mapping suggestion feature (suggesting field mappings between source and target schemas) costs 10 credits per request.
Payload Size Considerations
To ensure fair usage and maintain high-performance execution across the platform, requests with large data payloads consume additional credits.
The standard 1 credit covers request body sizes up to 2 Megabytes (2MB).
Overage Calculation
If your request body exceeds the 2MB threshold, additional credits are charged based on the total size of the payload. The rule is:
- +1 extra credit for every additional 2MB (or fraction thereof).
This means the system divides the total payload size by 2MB and rounds up to the nearest whole number to determine the final credit cost.
Calculation Formula
Total Credits = Math.ceil(Payload Size in MB / 2MB)Examples
Here are some examples of how credits are calculated based on different payload sizes:
| Request Payload Size | Calculation | Total Credits Charged |
|---|---|---|
| 800 KB (0.8 MB) | Math.ceil(0.8 / 2) | 1 Credit |
| 1.99 MB | Math.ceil(1.99 / 2) | 1 Credit |
| 2.1 MB | Math.ceil(2.1 / 2) | 2 Credits |
| 3.5 MB | Math.ceil(3.5 / 2) | 2 Credits |
| 5.0 MB | Math.ceil(5.0 / 2) | 3 Credits |
| 9.8 MB | Math.ceil(9.8 / 2) | 5 Credits |
Monitoring Your Usage
You can monitor your remaining credit balance and track your API usage history directly from your Dashboard under the Billing or API Keys sections. If your account runs out of credits, subsequent API requests will return a 429 Too Many Requests or 402 Payment Required status until your balance is topped up or your subscription renews.