canonical: https://jentic.com/apis/scrapercity.com/scrapercity # ScraperCity API ScraperCity is a lead generation platform with APIs for finding B2B contacts, business emails, phone numbers, and local business data. The API follows a polling workflow: submit a scrape job, poll for status, then download results. The API exposes 15 endpoints secured with bearer authentication. ## For AI agents Programmatically scrape apollo leads, scrape google maps businesses. Covers 15 operations with bearer authentication. ## Scope Does not handle payments, communications, or crm - use for hr and recruiting only. ## Capabilities - Scrape Apollo leads - Skiptrace / People Finder - Validate emails - Query and filter ScraperCity API records by parameters - Monitor ScraperCity API operational status and events ## Use cases ### HR and Recruiting Operations Use the ScraperCity API to perform hr recruiting operations programmatically. The API provides 15 endpoints covering core functionality including scrape apollo leads, scrape google maps businesses, skiptrace / people finder. Example prompt: Call POST `/scrape/apollo` to scrape apollo leads ### Automated Scrape Management Automate scrape operations by combining multiple ScraperCity API endpoints. Agents can scrape google maps businesses and then skiptrace / people finder in a single workflow. Example prompt: Call POST `/scrape/google-maps` to scrape google maps businesses, then verify the result ### AI Agent Integration via Jentic AI agents discover and call ScraperCity API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually. Example prompt: Search Jentic for 'scrape apollo leads', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/scrape/apollo` | Scrape Apollo leads | | POST | `/scrape/google-maps` | Scrape Google Maps businesses | | POST | `/scrape/people-finder` | Skiptrace / People Finder | | POST | `/scrape/email-validator` | Validate emails | | POST | `/scrape/youtube` | Scrape YouTube channel emails | | POST | `/scrape/airbnb` | Scrape Airbnb pro host emails | | POST | `/scrape/yelp` | Scrape Yelp listings | | POST | `/scrape/domain-email` | Find emails for a domain | ## Key resources - **Scrape** — Start scraping jobs on various platforms - **Status** — Check scrape job status - **Download** — Download scrape results - **Database** — Query lead, local business, and ecommerce databases ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 64 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 90 / 100 - Developer Experience & Jentic Compatibility: 63 / 100 - AI-Readiness & Agent Experience: 49 / 100 - Agent Usability: 94 / 100 - Security: 60 / 100 - AI Discoverability: 53 / 100 - **View full report:** https://jentic.com/apis/scrapercity.com/scrapercity/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the ScraperCity API by hand means implementing its bearer auth, managing the run and download flow against app.scrapercity.com, and building your own retry handling. Through Jentic you install once, import ScraperCity from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** ScraperCity takes each scrape target in the request body across its Apollo, Google Maps, and other endpoints, so you limit the agent to the operations it needs, such as scraping Apollo leads or Google Maps listings. You choose the operations it may call, and any you leave out stay unavailable to the agent. - **Credential handling:** Your ScraperCity token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'scrape Apollo leads' or 'scrape Google Maps listings', and Jentic returns the matching ScraperCity operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Greenhouse** — Alternative hr recruiting API - **Lever** — Alternative hr recruiting API - **Workday** — Complementary hr recruiting API ## FAQ ### What authentication does the ScraperCity API use? The ScraperCity API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context. ### Can I scrape apollo leads with the ScraperCity API? Yes. Use the POST `/scrape/apollo` endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the ScraperCity API? Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer. ### How do I scrape apollo leads through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'scrape apollo leads'. Jentic returns the matching ScraperCity API operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the ScraperCity API have? The ScraperCity API exposes 15 endpoints covering scrape, status, download operations. ### Can I limit what my agent is allowed to do with the ScraperCity API? Yes. Because you run Jentic One yourself, you decide which ScraperCity operations your agent may call, so you can allow scraping Apollo leads while withholding Google Maps, Yelp, or people-finder scraping. Each scrape endpoint takes its target in the request body, and any operation you leave out of your own rules stays unavailable to the agent. The stored bearer token is injected at execution time and never enters the agent's prompt or context.