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

# Scrapestack API

The scrapestack API was built to offer a simple REST API interface for scraping web pages at scale without having to programatically deal with geolocations, IP blocks or CAPTCHAs. The API supports a series of features essential to web scraping, such as JavaScript rendering, custom HTTP headers, various geo-targets, POST/PUT requests and an option to use premium residential proxies instead of datac. The API exposes 3 endpoints secured with apiKey authentication.

## For AI agents

Programmatically basic scrape - forward post body to target, basic scrape. Covers 3 operations with apiKey authentication.

## Scope

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

## Capabilities

- Basic Scrape - forward POST body to target
- Manage crm data programmatically
- Integrate Scrapestack API into automated workflows
- Query and filter Scrapestack API records by parameters
- Monitor Scrapestack API operational status and events

## Use cases

### CRM Operations

Use the Scrapestack API to perform crm operations programmatically. The API provides 3 endpoints covering core functionality including basic scrape - forward post body to target, basic scrape, basic scrape - forward put body to target.

Example prompt: Call POST /scrape to basic scrape - forward post body to target

### Automated scrape Management

Automate scrape operations by combining multiple Scrapestack API endpoints. Agents can basic scrape and then basic scrape - forward put body to target in a single workflow.

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

### AI Agent Integration via Jentic

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

Example prompt: Search Jentic for 'basic scrape - forward post body to target', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/scrape` | Basic Scrape - forward POST body to target |
| GET | `/scrape` | Basic Scrape |
| PUT | `/scrape` | Basic Scrape - forward PUT body to target |

## Key resources

- **scrape** — Operations related to scrape

## 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:** 41 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 57 / 100
  - Developer Experience & Jentic Compatibility: 76 / 100
  - AI-Readiness & Agent Experience: 35 / 100
  - Agent Usability: 94 / 100
  - Security: 15 / 100
  - AI Discoverability: 42 / 100
- **View full report:** https://jentic.com/apis/scrapestack.com/scrapestack/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 <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Scrapestack API by hand means passing your access_key in the query string against api.scrapestack.com and building your own retry handling for failed scrapes. Through Jentic you install once, import Scrapestack from the API Directory, store the access key once, and your agent calls it.
- **Permission scoping:** Scrapestack takes the target URL in the request rather than the path, so you limit the agent to the operations it needs, such as a basic GET or POST scrape. You choose the operations it may call, and any you leave out stay unavailable to the agent.
- **Credential handling:** Your Scrapestack access 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 target page and forward the POST body', and Jentic returns the matching Scrapestack 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 Scrapestack API use?

The Scrapestack API uses an API key passed in the `access_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 basic scrape - forward post body to target with the Scrapestack API?

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

### What are the rate limits for the Scrapestack 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 basic scrape - forward post body to target through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'basic scrape - forward post body to target'. Jentic returns the matching Scrapestack API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Scrapestack API have?

The Scrapestack API exposes 3 endpoints covering scrape operations.

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

Yes. Because you run Jentic One yourself, you decide which Scrapestack operations your agent may call, so you can allow a read-only GET /scrape while withholding POST /scrape and PUT /scrape, or the reverse. Any operation you do not enable stays unavailable to the agent, and since Scrapestack takes the target URL in the request body rather than the path, your rules govern exactly which scrape calls run. Your access key is stored encrypted by your own instance and injected only when an allowed operation executes.