Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Scrapestack 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%2Fscrapestack.com%2Fscrapestack" | shStep 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%2Fscrapestack.com%2Fscrapestack" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Scrapestack API.
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
GET STARTED
Patterns agents use Scrapestack API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'basic scrape - forward post body to target', load the operation schema, and execute with Jentic-managed credentials
3 endpoints — 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.
METHOD
PATH
DESCRIPTION
/scrape
Basic Scrape - forward POST body to target
/scrape
Basic Scrape
/scrape
Basic Scrape - forward PUT body to target
/scrape
Basic Scrape - forward POST body to target
/scrape
Basic Scrape
/scrape
Basic Scrape - forward PUT body to target
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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.
Alternatives and complements available in the Jentic catalogue.
Specific to using Scrapestack API through Jentic.
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.
For Agents
Programmatically basic scrape - forward post body to target, basic scrape. Covers 3 operations with apiKey authentication.
Use for: I need to basic scrape - forward post body to target, I want to basic scrape, Search for basic scrape - forward put body to target, List all records from Scrapestack API
Not supported: Does not handle payments, communications, or developer tools - use for crm only.
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.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>