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

# ScrapingAnt API

ScrapingAnt provides a web scraping API that runs a cluster of hundreds of Chrome browsers under the hood. The API handles JavaScript rendering, proxy rotation, CAPTCHA solving, and more. The API exposes 7 endpoints secured with apiKey authentication.

## For AI agents

Programmatically general web scraping (post), general web scraping. Covers 7 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for cloud infrastructure only.

## Capabilities

- General Web Scraping (POST)
- Markdown Extraction
- AI Data Extraction
- Extended JSON Output
- Monitor ScrapingAnt API operational status and events

## Use cases

### Cloud Infrastructure Operations

Use the ScrapingAnt API to perform cloud infrastructure operations programmatically. The API provides 7 endpoints covering core functionality including general web scraping (post), general web scraping, general web scraping (put).

Example prompt: Call POST /general to general web scraping (post)

### Automated extended Management

Automate extended operations by combining multiple ScrapingAnt API endpoints. Agents can general web scraping and then general web scraping (put) in a single workflow.

Example prompt: Call GET /general to general web scraping, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call ScrapingAnt 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 'general web scraping (post)', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/general` | General Web Scraping (POST) |
| GET | `/general` | General Web Scraping |
| PUT | `/general` | General Web Scraping (PUT) |
| DELETE | `/general` | General Web Scraping (DELETE) |
| GET | `/markdown` | Markdown Extraction |
| GET | `/extract` | AI Data Extraction |
| GET | `/extended` | Extended JSON Output |

## Key resources

- **extended** — Operations related to extended
- **extract** — Operations related to extract
- **general** — Operations related to general
- **markdown** — Operations related to markdown

## Why Jentic

- **Setup:** Wiring the ScrapingAnt API by hand means passing your x-api-key in the query string against api.scrapingant.com and building your own retry handling across its general, markdown, and extract calls. Through Jentic you install once, import ScrapingAnt from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** ScrapingAnt takes the target URL in the request rather than the path, so you limit the agent to the operations it needs, such as a general scrape or a markdown extraction. You choose the operations it may call, so the DELETE general operation is not included unless you add it.
- **Credential handling:** Your ScrapingAnt API 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 page' or 'get a page as markdown', and Jentic returns the matching ScrapingAnt operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Amazonaws** — Alternative cloud infrastructure API
- **Azure** — Alternative cloud infrastructure API
- **Googleapis** — Complementary cloud infrastructure API
- **Digitalocean** — Complementary cloud infrastructure API

## FAQ

### What authentication does the ScrapingAnt API use?

The ScrapingAnt API uses an API key passed in the `x-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 general web scraping (post) with the ScrapingAnt API?

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

### What are the rate limits for the ScrapingAnt 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 general web scraping (post) through Jentic?

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

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

The ScrapingAnt API exposes 7 endpoints covering extended, extract, general operations.

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

Yes. Because you run Jentic One yourself, you decide which ScrapingAnt operations the agent may call, so you can grant only a general scrape (GET or POST /general) or a markdown extraction (GET /markdown) and leave everything else out. Since ScrapingAnt takes the target URL in the request body rather than in the path, the DELETE /general operation is not available to the agent unless you explicitly add it. Your API key is held by your own instance and injected only for the operations you have approved.