Skip to main content

​
Base URL

All API requests should be made to: 
https://api.crawleo.dev

​
Authentication

All endpoints require authentication using your API key. You can provide it in one of two ways: Option 1: Authorization Header 
Authorization: Bearer YOUR_API_KEY
Option 2: X-API-Key Header 
x-api-key: YOUR_API_KEY

Get Your API Key

Sign up and subscribe to get your API key.

​
Available Endpoints

Crawleo provides four API endpoints:

Bing Search API

GET /searchBing-powered web search with auto-crawling and content extraction. Optimized for LLM and RAG pipelines.

Google Search API

GET /google-searchGoogle SERP data with knowledge graphs, news, images, places, and shopping. Ideal for SEO and lead generation.

Crawler API

GET /crawlDirect URL crawling with JavaScript rendering support.

Headful Browser API

GET /headful-browserPremium headed browser crawling with advanced anti-bot evasion. For sites that block standard crawlers.
Which Search API should I use? Use the Bing Search API for LLM/RAG workflows — it supports auto-crawling and returns page content in Markdown. Use the Google Search API for SEO monitoring, lead generation, and structured SERP analysis.

​
Output Formats

Both APIs support multiple output formats optimized for different use cases:
FormatCrawler ParameterDescriptionBest For
Raw HTMLraw_html=trueOriginal page sourceFull content preservation
Enhanced HTMLenhanced_html=true (default)Clean HTML (no ads, scripts)Cleaner processing
Markdownmarkdown=true (default)Structured markdownRAG pipelines, LLMs
Use Markdown output (enabled by default) for AI/LLM applications to minimize token usage.

​
Response Format

All responses are returned as JSON. Successful responses include the requested data, while errors return an error object: 
{
  "error": {
    "code": "ERROR_CODE",
    "message": "Human-readable error message"
  }
}

​
HTTP Status Codes

CodeDescription
200Success
400Bad Request - Invalid parameters
401Unauthorized - Invalid or missing API key
403Forbidden - Insufficient permissions
429Credits exhausted or concurrent request limit reached
500Internal Server Error

​
Credits System

API usage is tracked using credits. Each API call deducts credits from your monthly allowance based on your subscription plan.

​
Credit Costs by Endpoint

API EndpointCredits Cost
Bing Search API10 credits per page of results
Google Search API10 credits per request
Crawl API (HTTP request)1 credit per URL
Crawl API (browser rendering)10 credits per URL

​
Subscription Plans

PlanCredits/MonthConcurrent RequestsPrice
Free10,0005$0/month
Developer100,00020$20/month
Pro1,000,00050$100/month
Scale2,500,000100$200/month

Credits & Pricing

View detailed pricing, usage examples, and optimization tips.

​
Concurrent Request Limits

Each plan has a maximum number of concurrent requests. If you exceed this limit, you’ll receive a 429 response with the message: 
Concurrent request limit reached ({limit}). Please wait for other requests to finish.

​
MCP Integration

For AI assistants and IDEs, Crawleo also provides a Model Context Protocol (MCP) endpoint: 
https://api.crawleo.dev/mcp

MCP Integration

Learn how to connect AI assistants directly to Crawleo.
Last modified on April 16, 2026