Home / Web search APIs / Search1API
Search1API pricing
100,000 standard searches a month cost $99.00 on Search1API's Professional plan, with room to grow to 150,000 standard searches on the same plan.
Checked Oct 12, 2026 on Search1API's own pricing page
- Basic
- Professional
- Enterprise
Your workloadType an exact volume or copy a link to this jobEdit
one page of results per search
Fixed for this page; volume is the control.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.
Every Search1API plan
| Plan | Covers | Billed monthly | Billed yearly, per month | Included | Past the allowance | Concurrent |
|---|---|---|---|---|---|---|
| Basic | 10K to 25K search calls | $19.00 | $15.83saves 17% | 25,000 credits | move to a bigger plan | not published |
| Professional fits your volume | 50K to 100K search calls | $99.00 | $82.50saves 17% | 150,000 credits | move to a bigger plan | not published |
| Enterprise | 250K to 1M search calls | $499.00 | $415.83saves 17% | 1,000,000 credits | move to a bigger plan | not published |
Your job
What Search1API bills you for
What you pay
Search1API is also sold as one of the web scraping APIs (100,000 JavaScript-rendered pages a month: no public price) and one of the AI extraction APIs (100,000 AI extraction operations a month: $499.00 on Enterprise).
About this price and its sources
How Search1API combines search, crawling, extraction, and page-based credit additions, plus the terms still left open.
Cite this price
100,000 standard searches a month cost $99.00 on Search1API's Professional plan, with room to grow to 150,000 standard searches on the same plan. Price read from https://s1.dev/pricing on Oct 12, 2026. Scraping API Prices, https://scrapingapiprices.com/search1api-pricing
How the bill builds up
- Base rate1 creditper request
- × JavaScript renderingNot requiredNot part of this workload
- × Premium proxyNot required
- ÷ Success rate1Failure billing is not published; this is an assumption
- = Billed units per search1 creditFrom this bill’s calculation
- = per 1,000 searches$0.99Professional, billed monthly
Credits and multipliers
JavaScript rendering
Billed failures
Success rate
Concurrency
Free tier
Renews monthly The bill at your volume
100,000 search calls · $99.00
Read the chart as a table
| Volume | Bill | Offer |
|---|---|---|
| 10,000 | $19.00 | Basic |
| 25,000 | $19.00 | Basic |
| 50,000 | $99.00 | Professional |
| 100,000 | $99.00 | Professional |
| 250,000 | $499.00 | Enterprise |
| 500,000 | $499.00 | Enterprise |
| 1,000,000 | $499.00 | Enterprise |
Follow each billed unit
-
Successes you want
100,000 standard searches
Your stated workload. Every vendor on this site is priced against this same number.
- ÷ 1
Attempts you are billed for
100,000 standard searches
Failure billing is not published. This workload assumes no failures, so the missing rule does not change the bill.
- × 1
What the meter counts
100,000 credits
One attempt is one billed unit for this workload.
- =
Cash per month
$99.00 /mo
Professional: the cheapest way to buy this volume, not just the first plan big enough.
Bars share one linear scale across the 3 counted stages, so a multiplier shows as length. Units differ by stage and are labelled. Cash is not on that scale.
100,000 standard searches → 100,000 credits → Professional $99.00/mo = $0.99 per 1,000 searches
What makes it cost more
One page is not always one billed unit. These are Search1API's published charges for each kind of work.
| Work | Costs | Per | Source |
|---|---|---|---|
| A search | 1 credit | request | source |
| AI extraction | 10 credits | request | source |
Cheaper for this job
Same 100,000 standard search calls with one default-depth result set per call, ranked by what you would actually be billed. APIs without a full public price aren't ranked.
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 (Search1API pricing, Jul 27, 2026).
- A paid-plan overage price or a numeric paid-plan concurrency entitlement (Search1API pricing, Jul 27, 2026).
- 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, checked Jul 27, 2026.
- Whether unused paid credits roll into another billing period (Search1API pricing, Jul 27, 2026).
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, checked Jul 27, 2026.
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, checked Jul 27, 2026.
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, checked Jul 27, 2026.
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, checked Jul 27, 2026.