Skip to main content

Overview

Crawleo uses a credits-based billing system that gives you flexibility and predictability in your API usage. Credits are deducted from your monthly allowance based on which API endpoints you use and their configuration.

Credit Costs

Bing Search API

Optimized for LLM and RAG pipelines with auto-crawling and content extraction.
Each page of search results (controlled by max_pages parameter) costs 10 credits. For example, searching with max_pages=3 will cost 30 credits.

Google Search API

Structured Google SERP data for SEO, lead generation, and competitor research.
Each Google Search request costs a flat 10 credits regardless of result count. Supports web, news, images, places, and shopping search types.

Crawl API

Failed requests cost 0 credits. You only pay for successful responses.
Use browser rendering (render_js=true) only for JavaScript-heavy sites that require dynamic content. Default HTTP requests are the most cost-effective.

Headful Browser API

Premium crawling using a real headed browser with advanced anti-bot evasion, dedicated GPU rendering, and SOAX residential proxies.
The Headful Browser API is designed for sites protected by Cloudflare, Akamai, DataDome, or other advanced bot-detection systems where the standard Crawl API is insufficient.
At 50 credits per URL, use the Headful Browser API only when necessary. Always try the standard Crawl API (render_js=false or render_js=true) first. Failed requests cost 0 credits.

Subscription Plans

Free Plan

$0/month
  • 500 credits/month
  • 500 page crawls
  • 50 searches
  • Email support
  • Zero data retention

Developer

**20/month(or20/month** (or 200/year)
  • 100,000 credits/month
  • 20 concurrent requests
  • Email support
  • Zero data retention

Pro

**100/month(or100/month** (or 1,000/year)
  • 1,000,000 credits/month
  • 50 concurrent requests
  • Email + Dedicated support
  • Zero data retention

Scale

**200/month(or200/month** (or 2,000/year)
  • 2,500,000 credits/month
  • 100 concurrent requests
  • Email + Dedicated support
  • Zero data retention

View All Plans

Compare plans and subscribe at crawleo.dev/pricing

Usage Examples

Bing Search API Examples

Google Search API Examples

Crawl API Examples

Headful Browser API Examples

When using Crawleo via MCP (Model Context Protocol), the same credit costs apply:

Response Fields

Every API response includes credit usage information:
credits_used
integer
Number of credits consumed by this API call.
credits_remaining
integer
Your remaining credit balance for the current billing period.

Monitoring Your Usage

Track your credit usage in the Crawleo Dashboard:
  • View current credit balance
  • See usage history and trends
  • Set up usage alerts
  • Monitor API call patterns

Optimizing Credit Usage

  • Start with HTTP requests (1 credit) for most static sites
  • Use browser rendering (10 credits) only for JavaScript-heavy sites
  • Test with HTTP first before enabling JavaScript rendering
Only request the number of search pages you need. Each additional page costs 10 credits.
Crawl multiple URLs in a single request when possible to reduce overhead.
Cache crawled content on your side to avoid re-crawling the same URLs.

Rate Limits

In addition to credits, each plan has concurrent request limits: If you exceed your concurrent request limit, you’ll receive a 429 response:

Upgrading Your Plan

Need more credits? Upgrade your plan at any time:
  • Upgrades take effect immediately
  • Unused credits don’t roll over
  • Pro-rated billing for mid-cycle upgrades

Contact Sales

Need a custom plan or have questions? Contact our sales team.
Last modified on April 16, 2026