Site-specific access
Specialist CAPTCHA and anti-bot handling, including DataDome and Akamai, plus authorized login and session workflows.

ScrapingBuddy / Products
Three focused tools. One account.
From a single verification to your next research workflow.
A temporary number.
The message you need.
Choose a country and the app or service you want to verify. Review live availability and pricing, then receive incoming SMS against your order.
Review availability and the live quote.
A number assigned to your order.
Before you order: Numbers are temporary, not a permanent phone line or an account-recovery method. Stock and message delivery can vary.
View live pricesA challenge in.
An actionable answer out.
Send a supported image, text or audio challenge with the required instructions. Receive the answer your application needs to take the next step.
Your application applies the answer. These tasks do not return a universal website verification token.
Separate from scraping: CAPTCHA solving is its own product. It is not automatically applied to requests made through the Scraping API.
Task pricingMany websites.
One research question.
Collect selected public pages without building a scraper for every site. Keep the content, ask AI to extract facts, research a company or classify a list against your own criteria.
Collect the page as Markdown.
# Verde Studio Herbruikbare verpakkingen. Utrecht, Nederland. Contact: hello@verde.example
Original page content. No AI processing.
Public content, clear limits: No CAPTCHA or login bypass in this API. AI results include evidence and limitations; missing evidence is not a confident answer.
Need site-specific engineering?A managed service, not another self-service tool
For recurring, high-volume collection from specific websites, our team builds and maintains the workflow. You define the data you need. We assess the access, coverage and delivery requirements.
Specialist CAPTCHA and anti-bot handling, including DataDome and Akamai, plus authorized login and session workflows.
Agreed fields, pagination, coverage checks, deduplication and consistent output for your systems.
Scheduled collection, monitoring and maintenance as source websites change. Scope and feasibility agreed first.
From daily ticket prices to an entire product catalogue. A custom workflow may lower the total cost at sustained volume; access and throughput are assessed, not assumed.
Account & pricing
Each product has its own usage rules. Use the dashboard first, or integrate through its API.
Country and service determine the price. Review the current quote before you purchase.
Check availabilitySuccessful tasks cost provider cost + 50%. Each new task reserves $0.015; unused credit is released when settled.
CAPTCHA billingPer provider-completed page. AI and web search add provider cost + 50% when used. At least $1 available credit to start.
Scraping billingDashboard runs and API requests are paid. Credit holds and final charges depend on the product; review its billing guide before starting.
Save the request body and Idempotency-Key before creating an order or task. If you already have an ID, check that record first. When replaying creation, reuse the original key and identical input; for SMS, retain the original quote ID too. A new key can create new paid work. Unconfirmed submissions need review, not an automatic replacement.
No. A 2xx response can acknowledge creation or return a saved record that is still processing, failed or under review. Inspect the order or task status and its error fields. For scraping, ready means page content is available; optional analysis can still have failed. A completed classification batch can also contain failed rows.
No. API keys share account-level rate limits, and each product also has its own active-work limits. Coordinate creation and polling across your workers. On HTTP 429, respect Retry-After; an active-task limit may also require existing work to finish. Creating more keys or polling faster does not add capacity.
Billing follows each product's lifecycle, not a blanket all-or-nothing rule. Completed scraping steps remain charged if later research or analysis fails. Confirmed failed CAPTCHA tasks release their reservation. SMS refunds depend on the confirmed order outcome. An uncertain provider response can leave credit held for review; a client timeout is not proof of failure or a refund.
Treat unknown or insufficient evidence separately from a negative answer. In classification, use a label only when the row status is classified; failed, refused, review and insufficient-evidence rows have no answer label. Send those rows to a fallback or review path. Confidence is a model estimate, not a guarantee that the decision is correct.
Share representative URLs, required fields, an example output, target volume and refresh frequency. Include relevant country, language and authorized-access requirements, plus redacted errors from previous attempts. These let us assess coverage, access and delivery requirements before quoting. One successful page fetch alone does not establish a sustainable collection rate or complete dataset.