BatScrape’s initial integration focus is Apify. Our first task is to make source-specific Actors useful and understandable: clear inputs, documented output, and listings that explain their limits.
An additional interface would introduce another set of expectations. We want the underlying scraping workflow to be clear before expanding that surface.
Follow the Actor workflow
The intended starting point is the published Actor listing. Users should be able to understand its task, provide the required input, and inspect the resulting dataset.
Until individual listings are available, scraper buttons on this website point to the BatScrape Apify profile. That destination will be updated per scraper as development progresses.
Separate ideas from availability
Agent tools and other interfaces may be useful topics for future exploration. They are not released BatScrape integrations. In particular, this article does not announce an MCP server, a separate REST API, or direct database connectors.
The integration page reflects our current Apify focus. We’ll update that page when there is an additional supported integration to describe.
Let concrete needs guide the next step
Useful feedback starts with a task: which source, what records, and how the output will be used. Those details help us prioritize Actor development before adding another way to call the same unfinished workflow.
BatScrape Team
Building BatScrape
