Base URL
All API requests should be made to:Authentication
All endpoints require authentication using your API key. You can provide it in one of two ways: Option 1: Authorization HeaderGet 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:Response Format
All responses are returned as JSON. Successful responses include the requested data, while errors return an error object:HTTP Status Codes
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
Subscription Plans
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 a429 response with the message:
MCP Integration
For AI assistants and IDEs, Crawleo also provides a Model Context Protocol (MCP) endpoint:MCP Integration
Learn how to connect AI assistants directly to Crawleo.