Scraping API PricesAll products / Desearch
Desearch pricing
How Desearch meters search, crawl, social, and forecasting APIs, where its credit plans remain ambiguous, and who fits.
Every available option was priced in advance from published vendor rules. Changing a control only switches between those checked options; nothing is sent anywhere and no account is needed.
Your job
What Desearch counts
Nothing to count: Desearch publishes no rate for a page fetch. Its 3 published billing meters price other work.
What you pay
Successes you want
100,000 pages
Your stated workload. Every vendor on this site is priced against this same number.
- ÷ 0.95
Attempts you are billed for
105,263 requests
Desearch bills failed fetches, so a 5% failure rate is billed work.
- ∅
Cash per month
Not comparable here
no published rate for request.basic
Bars share one linear scale across the 2 counted stages, so a multiplier shows as length. Units differ by stage and are labelled. Cash is not on that scale.
Not comparable. This product publishes no rate for this kind of work.
no published rate for request.basic
This is a finding about what Desearch publishes, not a gap in the data. It stays visible so a definitive market claim cannot quietly ignore it.
Published exact bills for comparable products
Same 100,000 JavaScript-rendered pages a month at a 95% success rate, ranked by what you would actually be billed. Unknown totals never enter the numeric order.
Every Desearch plan
| Plan | Monthly | If billed yearly | Prepaid pack | Included | Simultaneous sessions |
|---|---|---|---|---|---|
| Starter | $179.00 | n/a | n/a | 3,000,000 credit | 150 |
| Business | $429.00 | n/a | n/a | 9,000,000 credit | 250 |
| Business Plus | $849.00 | n/a | n/a | 19,000,000 credit | 350 |
| Scale | $1,599.00 | n/a | n/a | 40,000,000 credit | 600 |
What consumes a unit
This is where a bill actually grows. One operation is not one billed unit, and the multiplier is published here rather than on the pricing page.
| Operation | Costs | Per | Source |
|---|---|---|---|
| search.query | 0.1 usd | 100 search | source |
| search.deep | 0.4 usd | 1000 result | source |
| crawl.page | 0.5 usd | 1000 page | source |
What Desearch does not publish
- The public pages do not map bundled request credits to the dollar-denominated per-product rates. Sources: https://www.desearch.ai/pricing and https://www.desearch.ai/credit-plans
- Failure billing and unused-credit rollover are not stated on the reviewed pages. Sources: https://www.desearch.ai/pricing and https://www.desearch.ai/credit-plans
What Desearch is
Desearch is an API family for agent applications that covers AI search, X search, web search, page crawling, and forecasting. The products return different objects: cited AI-search items, X posts, structured web searches, crawled pages, or one forecast response. A buyer is therefore choosing several context sources behind one account, not one generic search endpoint. Sources: Desearch and Desearch API pricing, retrieved 2026-07-27.
Tavily, Exa, and SerpApi are the nearest named competitors. Tavily presents search, extraction, crawling, and research for agent web access; Exa offers search, page contents, crawling, and deeper research products; SerpApi focuses on structured results from Google and other search engines. Desearch is easier to tell apart by its public X-search and forecasting meters alongside web search and crawl. Sources: Desearch API pricing, Tavily, Exa, and SerpApi, retrieved 2026-07-27.
How billing works
Self-serve usage is priced by each product’s output unit rather than by one universal request. AI Search is metered by returned items, X Search by returned posts, Web Search by searches, Web Crawl by pages, and Forecasting by request. Separate production plans bundle “request credits” across the API family and add plan-specific concurrency. The buying mistake to avoid is assuming one bundled request credit maps directly to one self-serve search, page, post, item, or forecast. The public pages show both systems but do not publish that conversion. Sources: Desearch API pricing and Desearch credit plans, retrieved 2026-07-27.
What Desearch does not publish
- A conversion table between bundled request credits and the dollar-denominated output meters on the self-serve API page. Sources reviewed: Desearch API pricing and Desearch credit plans, retrieved 2026-07-27.
- Whether failed API calls consume self-serve spend or bundled request credits. Sources reviewed: Desearch API pricing and Desearch credit plans, retrieved 2026-07-27.
- Whether unused production-plan credits roll into a later billing period. Source reviewed: Desearch credit plans, retrieved 2026-07-27.
- A general card requirement or expiry rule for the signup credit. The reward page states the signup grant but not those terms. Source reviewed: Desearch credit page, retrieved 2026-07-27.
Who it suits
Desearch suits agent teams that deliberately combine web, crawl, social, and forecasting inputs and can measure each output type before selecting a production credit plan. It is less suitable for a buyer who needs one stable “request” definition across every product or must reconcile a procurement quote to public unit rates without a sales call. The reason is the unresolved mapping between output-priced self-serve APIs and bundled request credits, not a judgment about the returned data. Sources: Desearch API pricing and Desearch credit plans, retrieved 2026-07-27.
Answer
What Desearch costs, what it publishes, and what it does not. Every figure sourced and dated.
Recorded 2026-07-26 from the vendor's own pricing page.The published price on this page matched the vendor page when it was rechecked.