The BatScrape core
Core owns auth, metering, quota, audit and cursors. Actors inherit all of it, so a new source ships as a schema and a fetch loop rather than a new service.
We run scrapers
so nobody else has to.
A small engineering team that ships the layer underneath.
Trusted by teams shipping data
What BatScrape is for
Make every source answer to one wire contract.
One actor per source, every one of them speaking the same versioned shape. Core carries auth, metering, quota, audit and cursors, so an actor only has to fetch.
The unglamorous part is the product.
Adding a source should cost a schema, not a sprint.
The catalogue should grow without the maintenance growing with it. Golden vectors gate every release, so a site changing its markup breaks a test run, not your pipeline.
The unglamorous part is the product.
Built on boring foundations
Metering, quota, audit and cursor pagination live in the core, so every actor inherits them on day one.
-
One wire contract
Every actor speaks the same shape, versioned and gated.
-
Scheduled runs
Cron your actors and stream results straight to storage.
-
Usage metering
Per-key counters you can read back over the same API.
-
MCP surface
The whole catalogue, exposed as tools your agent can call.
-
Cursor pagination
Resume a run exactly where the last one stopped.
Stats
Small numbers, and every one of them measured.
What the platform looks like today, in numbers.
Every figure below comes off the same metering the API bills you against.
-
99.95%
Core API uptime over the last twelve months.
-
24
Source actors, one per site.
-
140
Golden vectors gating every actor release.
-
9M+
Records returned through the API.
Team
A small team keeping every actor in contract.
-
Marek Dvořák
Core engineer
Auth, metering, quota
-
Deniz Arslan
Actor platform
Runtime and cursors
-
Tomas Lindqvist
Wire contract
Schemas and vectors
-
Rahul Menon
Reliability
Queues and backpressure
-
Jonas Weber
Developer relations
SDKs and MCP
-
Ilya Sorokin
Data quality
Drift and fixtures
Overview
What running the actor fleet looks like.
Actors in service
24 sources live today.
12x
Less scraper maintenance
fewer engineer-hours per source after month one.
Caching
Requests answered from the warm cursor cache.
42%
Marek Dvořák
Owns the core API surface
What engineers say about BatScrape
-
“We deleted four scrapers and a queue the week we moved. Six months on, the wire contract has not shifted under us.”
Dana R.
Staff Engineer
-
“Cursor state living in the core is the part I did not know I wanted, until a retry came back clean instead of doubled.”
Marcus Ellery
Platform Lead
-
“I pointed Claude at the MCP surface on a Tuesday and skipped the integration sprint that was already on the roadmap.”
Priya N.
Founding Engineer
-
“The golden vectors caught a breaking rename before it reached a consumer. That one release paid for itself.”
Tomas Lindqvist
Data Engineer
-
“One actor per source sounded fussy until we were pulling six sources and not one of them needed a special case.”
Ada Okafor
Head of Data
-
“Metering reads back over the same API as the data, so finance stopped asking me to reconcile it in a spreadsheet.”
Jonah Reyes
Engineering Manager
Ready to stop babysitting scrapers?
When no scraper exists for your source, BatScrape ships one.
Get API keys
- One contract for every source
- Versioned wire, no surprises
