canonical: https://jentic.com/apis/scraperbox.com/scraperbox # ScraperBox API ScraperBox provides a web scraping API with proxy management, JavaScript rendering, and anti-bot detection bypass capabilities. The API exposes 2 endpoints secured with apiKey authentication. ## For AI agents Programmatically scrape web page (post), scrape web page. Covers 2 operations with apiKey authentication. ## Scope Does not handle payments, communications, or crm - use for media and content only. ## Capabilities - Scrape Web Page (POST) - Manage media data programmatically - Integrate ScraperBox API into automated workflows - Query and filter ScraperBox API records by parameters - Monitor ScraperBox API operational status and events ## Use cases ### Media and Content Operations Use the ScraperBox API to perform media operations programmatically. The API provides 2 endpoints covering core functionality including scrape web page (post), scrape web page. Example prompt: Call POST /scrape to scrape web page (post) ### Data Retrieval and Monitoring Query ScraperBox API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed. Example prompt: Poll the primary ScraperBox API endpoint, compare response to last known state, and alert if changed ### AI Agent Integration via Jentic AI agents discover and call ScraperBox 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 'scrape web page (post)', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/scrape` | Scrape Web Page (POST) | | GET | `/scrape` | Scrape Web Page | ## 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:** 44 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 90 / 100 - Developer Experience & Jentic Compatibility: 77 / 100 - AI-Readiness & Agent Experience: 35 / 100 - Agent Usability: 94 / 100 - Security: 15 / 100 - AI Discoverability: 69 / 100 - **View full report:** https://jentic.com/apis/scraperbox.com/scraperbox/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 ScraperBox API by hand means passing your token in the query string against api.scraperbox.com and building your own retry handling for failed scrapes. Through Jentic you install once, import ScraperBox from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** ScraperBox takes the target URL in the request rather than the path, so you limit the agent to the operations it needs, such as a GET or POST scrape. You choose the operations it may call, and any you leave out stay unavailable to the agent. - **Credential handling:** Your ScraperBox 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 a web page', and Jentic returns the matching ScraperBox operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Cloudinary** — Alternative media API - **Mux** — Alternative media API ## FAQ ### What authentication does the ScraperBox API use? The ScraperBox API uses an API key passed in the `token` 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 ScraperBox 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 ScraperBox 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 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 ScraperBox API operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the ScraperBox API have? The ScraperBox API exposes 2 endpoints covering scrape operations. ### Can I limit what my agent is allowed to do with the ScraperBox API? Yes. Because you run Jentic One yourself, your own rules decide which ScraperBox operations the agent may call, so you can allow only the GET /scrape read or the POST /scrape request and leave the other unavailable. Since ScraperBox takes the target URL in the request rather than the path, scoping happens at the operation level: any operation you do not grant stays out of reach for the agent. Your ScraperBox token is stored encrypted by your own instance and injected only when a permitted call runs.