Skip to main content

ScrapingBuddy / Products

SMS.
CAPTCHA.
Web data.

Three focused tools. One account.
From a single verification to your next research workflow.

Explore the collection

SMS Verification

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.

From number to messageFictional example
  1. 01 / Choose

    Country & service

    Country
    United Kingdom
    Service
    Example app

    Review availability and the live quote.

  2. 02 / Receive

    Your temporary number

    +44 7700 900123

    A number assigned to your order.

  3. 03 / Verify

    The incoming message

    482 916 SMS received

    Read the message and track order status.

For permitted verification and onboarding checks. No number has been purchased in this example.

Before you order: Numbers are temporary, not a permanent phone line or an account-recovery method. Stock and message delivery can vary.

View live prices

CAPTCHA Solving

A 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 pricing

Scraping API

Many 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.

Web researchFictional examples
Your starting pointverde.example/about

Collect the page as Markdown.

Page content
# Verde Studio

Herbruikbare verpakkingen.
Utrecht, Nederland.

Contact: hello@verde.example

Original page content. No AI processing.

Illustrative outputs, not live requests. See each product's API reference for the exact response fields.
  • Content onlyHTML or Markdown. No AI required.
  • AI analysisYour instruction, with optional company context.
  • Deep analysisUp to 30 relevant pages, with optional web search.
  • ClassificationUp to 100 URLs per batch and your answer choices. CSV/TSV import in the dashboard.

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

Need the dataset,
not the work behind it?

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.

Site-specific access

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

Data you can use

Agreed fields, pagination, coverage checks, deduplication and consistent output for your systems.

Recurring delivery

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

One account. Pay for what you use.

Each product has its own usage rules. Use the dashboard first, or integrate through its API.

SMS Verification

Live price per order

Country and service determine the price. Review the current quote before you purchase.

Check availability
CAPTCHA Solving

Usage-based task pricing

Successful tasks cost provider cost + 50%. Each new task reserves $0.015; unused credit is released when settled.

CAPTCHA billing
Scraping API

$0.00045 / page

Per provider-completed page. AI and web search add provider cost + 50% when used. At least $1 available credit to start.

Scraping billing

Dashboard runs and API requests are paid. Credit holds and final charges depend on the product; review its billing guide before starting.

Integration & reliability

Before you automate.

Talk through your use case
How do I retry a timed-out request without paying twice?

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.

Does a successful HTTP response mean the work succeeded?

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.

Can separate API keys increase my account's request limits?

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.

What happens to my balance if only part of a job succeeds?

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.

How should an automated workflow handle an unknown AI result?

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.

What should I send for a site-specific feasibility assessment?

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.