Scraping API PricesAll products / Search1API
Search1API pricing
How Search1API combines search, crawling, extraction, and page-based credit additions, plus the terms still left open.
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 Search1API counts
Nothing to count: Search1API 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.
- × 1
Attempts you are billed for
100,000 requests
Search1API does not bill failed fetches, so failures cost nothing here.
- ∅
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 Search1API 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 Search1API plan
| Plan | Monthly | If billed yearly | Prepaid pack | Included | Simultaneous sessions |
|---|---|---|---|---|---|
| Basic | $19.00 | n/a | n/a | 25,000 credit | n/a |
| Professional | $99.00 | n/a | n/a | 150,000 credit | n/a |
| Enterprise | $499.00 | n/a | n/a | 1,000,000 credit | n/a |
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 | 1 credit | search | source |
| crawl.page | 1 credit | page | source |
| request.ai_extraction | 10 credit | request | source |
What Search1API does not publish
- The reviewed public page exposes a yearly toggle but not the exact annual effective prices in its loaded text. Source: https://www.search1api.com/pricing
- The reviewed pricing page does not publish overage prices or numeric concurrency for paid plans. Source: https://www.search1api.com/pricing
What Search1API is
Search1API is a web-access API for applications and AI agents. Its public product list combines multi-engine web and news search, webpage crawling, screenshots, sitemap generation, trend discovery, whole-site DeepCrawl, and prompt-based structured extraction. It is for teams that want search results and follow-on page access behind one key rather than only a traditional Google SERP response. Sources: Search1API and Search1API quickstart, retrieved 2026-07-27.
Tavily, Exa, and Firecrawl are the three nearest named competitors. Tavily and Exa center application retrieval around web search, while Firecrawl centers page scraping, extraction, mapping, and crawling. Search1API is distinguished by putting multi-engine search, screenshots, sitemap and trend utilities, deep crawling, and extraction in one public endpoint list. Sources: Search1API, Tavily credit documentation, Exa pricing, and Firecrawl pricing, retrieved 2026-07-27.
How billing works
One unit is a credit. Basic search, news, crawl, sitemap, and trending calls each have a 1-credit base treatment, while screenshot, structured extraction, and DeepCrawl have their own replacement request rates. Deep search is additive: it consumes 1 search credit plus 1 credit for every result page crawled successfully. The mistake to avoid is counting one deep-search query as one unit. Its final cost depends on how many result pages are actually crawled. Source: Search1API pricing, retrieved 2026-07-27.
What Search1API does not publish
- Exact effective annual amounts. The public page exposes a yearly selector but not a complete annual rate table in its readable pricing text. Source reviewed: Search1API pricing, retrieved 2026-07-27.
- A paid-plan overage price or a numeric paid-plan concurrency entitlement. Source reviewed: Search1API pricing, retrieved 2026-07-27.
- A complete failed-request billing rule across search, crawl, screenshot, extraction, and DeepCrawl. The free offer describes successful basic searches, but that does not define every endpoint. Sources reviewed: Search1API free search and Search1API pricing, retrieved 2026-07-27.
- Whether unused paid credits roll into another billing period. Source reviewed: Search1API pricing, retrieved 2026-07-27.
Who it suits
Search1API suits agent and research products that need both discovery and page retrieval and can log the endpoint and successful crawl count for each job. It is less suitable for workloads that need a fixed cost per deep-search call, or for procurement that requires published overage, concurrency, and failure rules before signup. The reason is the additive page meter and the limited public operating terms. Sources: Search1API pricing and Search1API quickstart, retrieved 2026-07-27.
Answer
What Search1API 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.