canonical: https://jentic.com/apis/scraperapi.com/scraperapi

# ScraperAPI

ScraperAPI handles proxies, browsers, and CAPTCHAs so you can scrape any web page with a simple API call. Supports web pages, API endpoints, images, documents, PDFs, and other files with a 50MB maximum request size limit. The API exposes 3 endpoints secured with apiKey authentication.

## For AI agents

Programmatically scrape web page (post), scrape web page. Covers 3 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or developer tools - use for crm only.

## Capabilities

- Scrape Web Page (POST)
- Get Account Information
- Integrate ScraperAPI into automated workflows
- Query and filter ScraperAPI records by parameters
- Monitor ScraperAPI operational status and events

## Use cases

### CRM Operations

Use the ScraperAPI to perform crm operations programmatically. The API provides 3 endpoints covering core functionality including scrape web page (post), scrape web page, get account information.

Example prompt: Call POST / to scrape web page (post)

### Automated account Management

Automate account operations by combining multiple ScraperAPI endpoints. Agents can scrape web page and then get account information in a single workflow.

Example prompt: Call GET / to scrape web page, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call ScraperAPI 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 apiKey tokens manually.

Example prompt: Search Jentic for 'scrape web page (post)', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | / | Scrape Web Page (POST) |
| GET | / | Scrape Web Page |
| GET | /account | Get Account Information |

## Key resources

- **account** — Operations related to account
- **default** — Operations related to default

## Why Jentic

- **Setup:** Wiring ScraperAPI by hand means passing your api_key in the query string, choosing between the standard and async hosts, and building your own retry handling for failed requests. Through Jentic you install once, import ScraperAPI from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** ScraperAPI takes the target URL in the request rather than the path, so you limit the agent to the operations it needs, such as scraping a page or reading account usage. You choose the operations it may call, and any you leave out stay unavailable to the agent.
- **Credential handling:** Your ScraperAPI key 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 a web page' or 'check my account usage', and Jentic returns the matching ScraperAPI operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the ScraperAPI use?

The ScraperAPI uses an API key passed in the `api_key` query. 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 web page (post) with the ScraperAPI?

Yes. Use the POST / endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the ScraperAPI?

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 web page (post) through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'scrape web page (post)'. Jentic returns the matching ScraperAPI operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the ScraperAPI have?

The ScraperAPI exposes 3 endpoints covering account, default operations.

### Can I limit what my agent is allowed to do with the ScraperAPI?

Yes. Because you run Jentic One yourself, your own rules decide which ScraperAPI operations the agent may call, so you can allow it to scrape a page while withholding the account-usage lookup, or the reverse. ScraperAPI takes the target URL in the request rather than in the path, so you scope the agent to just the operations it needs, and any operation you leave out stays unavailable to it. Your API key is held by your own instance and injected only at execution time, so the agent never sees the raw secret.