Start with the source
Share a few representative URLs and explain how you find the records you need. Include listing pages, detail pages and any search conditions that change the result. This helps define the actual collection scope.
Define a usable output
List the required fields, their expected types and a small example of the format your team can consume. Tell us which fields are essential and which may be missing on some source pages.
For recurring work, decide how to identify the same record across runs and how you want changes represented. A full snapshot and a change feed serve different purposes.
Agree on acceptance criteria
A useful test checks populated records, source accuracy and the fields your workflow depends on. Volume, update frequency and completion time should be agreed alongside those checks.
Source coverage and feasibility need to be assessed before scope or delivery can be confirmed. Changes at the source can also affect an ongoing scraper.
What to include in your request
Source URLs and the kinds of pages to collect.
Required output fields and preferred format.
Approximate record count and update frequency.
Your downstream use, such as research, a dashboard or an AI application.
Common questions
Can I start with an existing actor?
Yes. Check the actor directory first. An existing scraper may already provide the source and fields you need.
Can you guarantee every website is supported?
Feasibility depends on the source and scope. Send representative URLs so we can assess the request before agreeing on a build.
How do I request a quote?
Email abotapi@proton.me with your sources, fields, expected volume and frequency. Those details let us discuss the scope.
