Install Jentic One Beta

Connect the ScraperCity API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ScraperCity API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fscrapercity.com%2Fscrapercity" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fscrapercity.com%2Fscrapercity" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with ScraperCity API.

Scrape Apollo leads

Skiptrace / People Finder

Validate emails

Query and filter ScraperCity API records by parameters

Monitor ScraperCity API operational status and events

GET STARTED

Start building with ScraperCity API

Explore with Jentic One

View OpenAPI Document

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.

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.

Search Jentic for 'scrape apollo leads', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

15 endpoints — scrapercity is a lead generation platform with apis for finding b2b contacts, business emails, phone numbers, and local business data.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using ScraperCity API through Jentic.

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.

ScraperCity API

Name: ScraperCity API
Brand: ScraperCity API
Availability: InStock

AI ReadinessAI-Aware (B)64/100

See full scorecard

Official vendor OpenAPI document · agent-readyHR recruitingRecruiting Atsbearer15 EndpointsREST

For Agents

Programmatically scrape apollo leads, scrape google maps businesses. Covers 15 operations with bearer authentication.

Use for: I need to scrape apollo leads, I want to scrape google maps businesses, Search for skiptrace / people finder, Find all validate emails

Not supported: Does not handle payments, communications, or crm - use for hr and recruiting only.

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

60%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D+Signals: 4

45%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: C-Signals: 1

53%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the ScraperCity API to your agent

Capabilities

Start building with ScraperCity API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

ScraperCity API

Jentic AI Readiness Score

ScraperCity API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness