Customer workflow
Read how RankMax uses DataBlue for search-data workflows.
Read the RankMax story →NEW - Scrape any site to LLM-ready JSON - 1,000 one-time signup credits














No proxies to rotate, no headless browser to babysit, no HTML to parse. Send a URL, get back clean structured JSON — ready to drop straight into your LLM or RAG pipeline.
import requests r = requests.post( "https://api.datablue.dev/v1/scrape", headers={"Authorization": "Bearer wh_your_api_key"}, json={"url": "https://example.com", "formats": ["markdown", "links"]}, ) print(r.json()) # clean, LLM-ready JSON
{
"success": true,
"data": {
"markdown": "# Example Domain\n\nThis domain is for use in...",
"links": ["https://www.iana.org/domains/example"],
"metadata": {
"statusCode": 200,
"sourceURL": "https://example.com",
"title": "Example Domain"
}
}
}Data APIs for AI agents
Give agents structured search, commerce, advertising, video, and app data through one API platform. DataBlue handles retrieval and normalization behind one key.
Explore all 37 APIsPick a sample query to animate illustrative JSON. No API request is sent; timings, status, token savings, and credit values are example data, not measured results.
Explore a customer story, inspect the contracts, and understand the costs.
Read how RankMax uses DataBlue for search-data workflows.
Read the RankMax story →Check authentication, supported inputs, and response fields before integrating.
Explore the documentation →Compare billing units and credit weights across the public catalogue.
Compare API rates →Visitors arrive with very different contexts. Self-select the on-ramp that fits where you are today.
New to web scraping? Build your first scraper in 5 minutes. We handle proxies, CAPTCHAs, geolocation, and JS rendering.
Switching from Firecrawl, SerpAPI, or a homegrown scraper? Migrate in under 10 minutes — drop-in compatible response shape.
Need enterprise reliability for millions of scrape and search requests with strict uptime, dedicated capacity, and custom contracts.
Five blocks that explain why DataBlue beats the field on the things that actually matter when you turn websites into LLM-ready data.
Use documented JSON fields from source-specific data APIs, or choose a web extraction workflow for your own schema. Available fields depend on the endpoint and source response.
<div class="yuRUbf MjjYud xpd vt6azd hlcw0c" data-ved="2ahUKEwi9..."><a href="/url?q=https://runnersworld.com&sa=U..."><h3 class="LC20lb MBeuO DKV0Md">The 12 Best Running Shoes of 2026</h3></a><cite class="qLRx3b tjvcx">runnersworld.com</cite> <!-- + 4,810 more lines -->
{ "position": 1, "title": "The 12 Best Running Shoes of 2026", "link": "https://runnersworld.com/best-running", "domain": "runnersworld.com", "snippet": "Our editors tested 60+ pairs…", "rich_snippet": { "rating": 4.7 }, "sitelinks": [ 4 items ] }
Set any location down to the city, any language, any device. DataBlue scrapes and searches from that exact location, so you see the prices, content, and results a real local user would, critical for localized scraping, rank tracking, and international research.
# pull mobile SERP for biryani in Madurai, in Tamil result = datablue.serp( query="best biryani", location="Madurai, Tamil Nadu, India", google_domain="google.co.in", hl="ta", # interface language gl="in", # country device="mobile" )
Retrieve structured data for research, monitoring, and agent workflows. Choose the endpoint for your source, then check its documented refresh behavior and response fields.
Each endpoint has a visible live-catalog weight before you run it. Monthly plan credits reset with the billing period, while top-up credits remain available as overflow until you use them.
| API / workload | Billing guidance |
|---|---|
| Scrape, crawl & extract | Check baseline output and additional components |
| Commerce & quick-commerce | Check the selected endpoint’s output unit |
| Ads, YouTube & App Store | Check the selected endpoint’s output unit |
| SERP Lite page | 1 credit per delivered result page |
| SERP Advanced page | 2 credits per delivered result page |
Our infrastructure is built for high-volume workloads. Auto-retry, residential proxy rotation, smart routing, and CAPTCHA solving — all invisible to you. You send the request, we return the data.
Concurrency is plan-based and visible before you run, with higher tiers unlocking more active jobs and request throughput.
Use the active Python and Node.js clients, or call the same API directly with cURL from any stack.
from datablue import DataBlue client = DataBlue(api_key="wh_your_api_key") # Scrape any URL -> clean, LLM-ready JSON result = client.scrape( "https://example.com", formats=["markdown", "links"], ) print(result.markdown) # Crawl an entire domain in one call status = client.crawl("https://example.com", max_pages=50) for page in status.data: print(page.url, len(page.markdown)) # Async client for app workers and API routes from datablue import AsyncDataBlue async with AsyncDataBlue(api_key="wh_your_api_key") as async_client: async_result = await async_client.scrape( "https://example.com", formats=["markdown"], )
Choose the sources and outputs that fit your workflow.
Build research agents that browse Google live, pull the top 10 results, and synthesize the findings with an LLM. Fresh, structured search data without HTML token overhead.
Power your own rank tracker, internal SEO dashboard, or client reporting tool. Pull thousands of positions daily, monitor SERP feature changes, alert on competitor moves.
Retrieve product and marketplace data from supported commerce sources. Compare location-specific price and availability from Blinkit, Zepto, and Instamart in India.
Research public ad creatives, YouTube metadata, and Apple App Store listings with source-specific APIs. Ads transparency data is not private campaign performance data.
We've all been there. Usage pages that do not match invoices. Hidden multipliers that change unit economics after launch. Raw HTML when you needed structured data. DataBlue was built around visible endpoint weights, success-only billing, and clear credit buckets.
Monthly credits and top-ups behave differently.
Monthly plan credits reset with your billing period. Top-up credits do not expire and are used after your monthly credits.
Costs are visible before you run.
SERP Lite, Advanced SERP, Maps, and other APIs use explicit admin-managed weights. The public pricing page shows the active catalog.
Structured JSON · LLM extraction · MCP support — every plan.
No "AI tier" upsell. No feature gates between you and clean data.
Usage is fully transparent.
You see exactly which queries you ran, when, and what they cost. No mystery "infrastructure fees" or "premium proxy charges" buried in fine print.
Built by a team that's shipped developer tools for 10+ years. We use DataBlue ourselves every day to power our own products like Japan Pro. It's production-grade because our own revenue depends on it.
Connect to live web, search, commerce, ads, video and app data through your preferred interface.
Build DataBlue into your applications with an API key and documented endpoints.
Explore API docsDataBlue account and available credits required. Client availability and workspace permissions vary; see setup guides.
One credit balance for search, scraping, commerce, quick-commerce, ads, YouTube and App Store APIs. Choose a plan for your volume; each endpoint has its own billing unit and credit weight.
Paid plans start at USD 29 / month (Lite, billed monthly)
Example: Google SERP
Google SERP Lite: 1 credit per delivered result page. Google SERP Advanced: 2 credits per delivered result page. Multi-page requests are billed per delivered page.
Compare billing units, plan capacity and effective costs for all APIs →Answers about API output, integration and billing.
Bring web, search, commerce, ads, video, and app data into your AI workflows through one platform. Explore the current plans and one-time signup allowance in the pricing catalog.