Token Plan
Learn how tokens work in MrScraper and how to create your own API token for authentication.
MrScraper uses a token-based system for both usage and authentication.
- Plan Tokens measure how much you can use MrScraper's features, such as running or rerunning scrapers.
- API Tokens allow you to securely access the MrScraper API, for example, to rerun an existing scraper programmatically.
Why Token Usage Varies
Token consumption isn't fixed — a few key factors affect how many tokens any given scraper uses:
- Website Complexity: Heavy JavaScript, dynamic content, or multiple requests increase runtime and token usage.
- Page Size and Content Density: Larger pages with long articles or extensive metadata produce more input text for AI models to process.
- Data Volume: Extracting large datasets (e.g., paginated listings) requires more compute and bandwidth.
- AI Processing Load: Complex instructions or large expected outputs increase input and output token usage.
Keep these in mind as you read the pricing tables below — they explain why two runs on the same plan can consume different amounts of tokens.
Understanding Plan Tokens
Each MrScraper billing plan includes a specific number of tokens. Tokens represent the compute resources your scraper consumes — similar to how minutes or data are counted in a phone plan.
The number of tokens used depends on the type of scraper you run.
AI Scraper Token Usage
AI Scrapers consume more tokens due to AI processing and additional factors such as:
| Usage Type | Description | Conversion Rate |
|---|---|---|
| Run Tracking | Each AI agent run consumes 5 tokens for trace tracking. Reruns and manual scrapers consume 0 tokens for this component. | 0 or 5 tokens per run |
| Runtime | Time spent processing your task. | 1 token per 30 seconds of runtime |
| Input Tokens | Amount of text data (prompts or instructions) sent to the AI model. | 1 token per ~1,000 input tokens |
| Output Tokens | Amount of text generated by the AI model (responses or extracted results). | 1 token per ~200 output tokens |
Example
If your AI scraper runs for 90 seconds, processes 5,000 input tokens, and generates 1,000 output tokens, your total token usage would be:
| Component | Calculation | Tokens |
|---|---|---|
| Runtime | 90 ÷ 30 | 3 |
| Input | 5,000 ÷ 1,000 | 5 |
| Output | 1,000 ÷ 200 | 5 |
| Run Trace | Fixed | 5 |
| Total | 18 |
Note
- Each run automatically includes trace tracking for debugging and performance monitoring. - Input and output tokens are based on how much text the AI model processes and generates. - AI Scrapers tend to consume more tokens due to model processing. - Runtime tokens are rounded up using the ceiling rule. For example, if your scraper runs for 40 seconds, it will count as 2 tokens (not 1).
Manual Scraper Token Usage
Manual Scrapers (non-AI) use tokens based on runtime and bandwidth.
| Usage Type | Description | Conversion Rate |
|---|---|---|
| Runtime | Time your scraper runs. | 1 token per 30 seconds |
| Bandwidth | Amount of data downloaded or uploaded. | 1 token per 0.2 MB |
Example
If your manual scraper runs for 40 seconds and uses 1.1 MB of bandwidth:
| Component | Calculation | Tokens |
|---|---|---|
| Runtime | 40 ÷ 30 = 1.33 → rounded up | 2 |
| Bandwidth | 1.1 ÷ 0.2 = 5.5 → rounded up | 6 |
| Total | 8 |
Note
Runtime tokens are rounded up using the ceiling rule. For example, if your scraper runs for 40 seconds, it will count as 2 tokens (not 1).
Marketplace Scraper Token Usage
Marketplace Scrapers use a custom token cost based on factors such as the target domain, workflow complexity, proxy usage, infrastructure requirements, and scraper configuration. Each scraper may use either a fixed token cost or a custom usage calculation depending on how the scraper is designed.
For the complete list of Marketplace Scraper token costs, see the Marketplace catalog.
Generating an API Token
An API Token lets your applications securely interact with the MrScraper API. It serves as your authentication key, allowing you to rerun scrapers that you've already created in the dashboard.
Follow these steps to generate your API token:
- Click your User Profile at the top-right corner of the page.
- Select API Tokens.
- Click New Token.
- Enter a name and set an expiration date.
Note
The API token name is required when calling the analytics endpoint.
- Click Create.
- Copy your new API token and store it securely.
Keep It Secret!
Never expose your API token in client-side code (like browsers or apps). Always store it securely in an environment variable or server configuration.