AD scraping-api-pricing
Compare web scraping API, SERP API and headless browser plans by monthly cost and conditions. Use when the user asks which scraping, crawling, search results (SERP), proxy or browser API plan fits a workload or a budget, for example "cheapest plan for 100k JavaScript pages a month", "SERP API for 20k Google searches in Germany under $100", "are failed requests billed", "compare Firecrawl and ZenRows". Covers Firecrawl, ScrapingBee, ZenRows, Bright Data, Oxylabs, Zyte, Scrapfly, ScrapingAnt, Scrapingdog, SerpApi, Serper, DataForSEO, SearchCans, Brave Search API, Tavily, Apify and Spider. Each answer carries the sentence from the official pricing page and its check date; a term the page does not state is reported as unknown, not guessed.
Compare web scraping API, SERP API and headless browser plans by monthly cost and conditions.
As a process D 49/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 49/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 20 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1055 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +3Description length 745: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 20 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.