Skip to main content
OneTest uses a coin-based metering system to track API usage. Every API call made through an API key costs coins, while browser-based (UI) usage is always free.

​
How Metering Works

Free: Browser Usage

All actions through the OneTest UI are free and never consume coins. This includes using the AI assistant, managing tests, and viewing results.

Metered: API Keys

Programmatic access via API keys is metered. Each API call costs coins based on the operation type.

​
Coin Pricing

Every product starts with a weekly budget of 1,000 coins that resets automatically each week.
OperationCostDescription
REST API call1 coinAny API call authenticated with an API key
MCP single action1 coinSingle tool invocation via MCP
Agent loop1 coin per 10 stepsAI agent operations (batched)
Test ingestion1 coinReportPortal agent submissions
JUnit import1 coinJUnit XML file imports
UI operationFreeAll browser-based actions
Pricing is per API call, not per data volume. A single API call that returns 100 test cases costs the same as one that returns 1.

​
Viewing Usage

Navigate to Settings > Usage & Billing to see your current usage.

​
Activity Log

The activity log shows every metered event in real-time:
  • User who made the request
  • Operation type (REST API, MCP action, etc.)
  • Service that handled the request
  • Coin cost for each event
  • Timestamp of the event
Use the date filters to narrow down activity to a specific period.

​
Usage Summary

The summary panel shows at a glance:
  • Coins used this billing cycle
  • Coins remaining in your weekly budget
  • Budget cycle dates (start and end)
  • Usage breakdown by operation type

​
Usage Breakdown

See which types of operations consume the most coins: 
REST API calls:     450 coins (45%)
MCP actions:        300 coins (30%)
Test ingestion:     150 coins (15%)
JUnit imports:      100 coins (10%)

​
Export Activity

Export your activity log as CSV for reporting:
  1. Go to Settings > Usage & Billing
  2. Set the date range (up to 3 months)
  3. Click Export CSV
The export includes: timestamp, user, event type, source, service, operation, and coin cost.

​
Managing Budgets

​
Weekly Budget

Each product has a configurable weekly coin budget:
  • Default: 1,000 coins per week
  • Minimum: No minimum
  • Maximum: No limit
The budget resets automatically at the start of each weekly cycle.

​
Overage Protection

By default, API requests are blocked when the budget is exhausted. You can change this behavior:
  • Block on exhaustion (default): API calls return 429 Too Many Requests when coins run out
  • Allow overage: API calls continue working beyond the budget limit

​
Hourly Rate Limit

Set a maximum number of requests per hour to prevent runaway scripts or misconfigured integrations:
  • Default: Unlimited (0)
  • Configurable: 1 to 10,000 requests per hour

​
Adjusting Settings

To change budget settings:
1

Go to Settings

Navigate to Settings > Usage & Billing
2

Edit Budget

Adjust the weekly coin budget, overage policy, and hourly rate limit
3

Save Changes

Click Save to apply the new settings

​
Budget Top-Up

If you run out of coins mid-cycle, you can add more:
  1. Go to Settings > Usage & Billing
  2. Click Top Up
  3. Enter the number of coins to add
  4. Coins are added immediately to your available balance
Top-up coins are added to the current cycle only. They don’t carry over or change your weekly budget.

​
Usage History

View historical usage by week to identify trends:
  • Weekly snapshots showing total coins used and event counts
  • Breakdown by operation type for each week
  • Up to 12 weeks of history

​
FAQ

By default, API requests return 429 Too Many Requests. UI access is never affected. You can either:
  • Wait for the weekly reset
  • Top up coins manually
  • Enable overage to allow continued access
No. The AI assistant is accessed through the browser UI, which is always free. Only programmatic API access via API keys is metered.
The budget resets automatically 7 days after the cycle start date. The exact dates are shown on the Usage & Billing page.
Yes. The activity log shows which user made each request. Export to CSV and sort by user to see per-user consumption.