Frequently asked

Two places, and you can use either or both. Scrapeloop can scrape live — Google Maps, Yelp, Apollo, LinkedIn, Instagram — on a schedule you set, per state. Or you can pull from the database, 56M B2B contacts plus a local-business index, filtered down to the rows you want. Both land in the same table and go through the same cleaning rules.

No — territory is the first thing you pick. Choose one state, seven, or all fifty, set a monthly cap, and Scrapeloop only spends against the tiles you selected. The coverage map records what has already been pulled and how fresh it is, so a monthly run keeps finding new businesses instead of re-buying the same ones.

It routes instead of dying. A lead with a verified email goes to cold email; one with only a mobile number goes to SMS; one with neither gets a LinkedIn profile lookup and, if a match is found, a connect-and-DM sequence. That is the loop in the graphic above — a lead only leaves it when it replies or you suppress it.

Instantly, Smartlead and Lemlist for email, GoHighLevel for SMS and CRM, and Aimfox for LinkedIn. Sending is two-way: replies, bounces, unsubscribes and opens come back into the lead row, so the next rule can act on them.

You sign up with the vendors directly — Outscraper, Apify, Prospeo, Reoon, Instantly — and paste your API keys in. You pay them at list price with no markup from us, and we never touch your card with them. Managed keys, where Scrapeloop handles vendor billing on your behalf, are on the roadmap.

Every scrape, enrichment and verification writes to one spend ledger, and every run is estimated before it starts. You set caps per credential, per integration and per workspace; when a cap is hit the run stops rather than continuing quietly. Agency owners see the same numbers per sub-account.

Yes. Agency owners get sub-accounts with their own workspaces, users, roles and credit meters, and an agency console that shows spend and volume per client. Agency navigation is a separate mode, so nothing about your other clients is visible from inside one of them.

Every workspace sits behind Postgres row-level security, and API keys are encrypted at rest and scoped to a single workspace. Private tables keep their derived campaigns, replies, jobs and spend private too — even from other members of the same workspace.

We want the first cohort to be a tight feedback loop rather than a support queue. Join the waitlist and invite codes go out in batches.