Install Jentic One Beta

Connect the WebScraping.AI to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the WebScraping.AI, 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%2Fwebscraping.ai%2Fwebscraping" | sh

Step 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%2Fwebscraping.ai%2Fwebscraping" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with WebScraping.AI API.

Get an answer to a question about a given web page

Extract structured data fields from a web page

Page HTML by URL

HTML of a selected page area by URL and CSS selector

Information about your account calls quota

GET STARTED

Start building with WebScraping.AI API

Explore with Jentic One

View OpenAPI Document

Automated AI Management

Automate ai operations by combining multiple WebScraping.AI endpoints. Agents can extract structured data fields from a web page and then page html by url in a single workflow.

Call GET /ai/fields to extract structured data fields from a web page, then verify the result

AI Agent Integration via Jentic

AI agents discover and call WebScraping.AI 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 'get an answer to a question about a given web page', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

7 endpoints — webscraping.

METHOD

PATH

DESCRIPTION

GET

/ai/question

Get an answer to a question about a given web page

GET

/ai/fields

Extract structured data fields from a web page

GET

/html

Page HTML by URL

GET

/text

Page text by URL

GET

/selected

HTML of a selected page area by URL and CSS selector

GET

/selected-multiple

HTML of multiple page areas by URL and CSS selectors

GET

/account

Information about your account calls quota

GET

/ai/question

Get an answer to a question about a given web page

GET

/ai/fields

Extract structured data fields from a web page

GET

/html

Page HTML by URL

GET

/text

Page text by URL

GET

/selected

HTML of a selected page area by URL and CSS selector

GET

/selected-multiple

HTML of multiple page areas by URL and CSS selectors

GET

/account

Information about your account calls quota

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring WebScraping.AI by hand means passing its api_key on every query, managing proxy and rendering options across the extraction endpoints, and handling retries yourself. Through Jentic you install once, import WebScraping.AI from the API Directory, store the API key once, and your agent calls it.

Permission scoping

WebScraping.AI carries the target URL and query in each request rather than in the path, so scope the agent to the operations it needs, such as fetching page text or asking a question about a page. You choose the operations it may call, so account or field-extraction calls are not included unless you add them.

Credential isolation

Your WebScraping.AI 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.

Intent-based discovery

Agents search Jentic by intent such as 'get an answer to a question about a web page' or 'extract the text of a page', and Jentic returns the matching WebScraping.AI operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using WebScraping.AI API through Jentic.

What authentication does the WebScraping.AI use?

The WebScraping.AI 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 get an answer to a question about a given web page with the WebScraping.AI?

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

What are the rate limits for the WebScraping.AI?

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 get an answer to a question about a given web page through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get an answer to a question about a given web page'. Jentic returns the matching WebScraping.AI operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the WebScraping.AI have?

The WebScraping.AI exposes 7 endpoints covering ai, html, text operations.

Can I limit what my agent is allowed to do with the WebScraping.AI API?

Yes. Because you run Jentic One yourself, your own rules decide which WebScraping.AI operations and credentials the agent may use, and this API carries the target URL and query in each request rather than in the path, so you scope by operation. You can allow the agent to fetch page text (GET /text) or ask a question about a page (GET /ai/question) while leaving field extraction (GET /ai/fields) and account quota lookups (GET /account) out unless you explicitly add them. Only the operations you approve are callable, so the agent cannot reach beyond the pages and actions you permit.

WebScraping.AI

AI ReadinessFoundational (D-)42/100

See full scorecard

AI/MLLanguage ModelsapiKey7 EndpointsREST

For Agents

Programmatically get an answer to a question about a given web page, extract structured data fields from a web page. Covers 7 operations with apiKey authentication.

Use for: I need to an answer to a question about a given web page, I want to extract structured data fields from a web page, Search for page html by url, Find all page text by url

Not supported: Does not handle payments, communications, or crm - use for ai and machine learning only.

WebScraping.AI scraping API provides LLM-powered tools with Chromium JavaScript rendering, rotating proxies, and built-in HTML parsing. The API exposes 7 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4

37%

Example Density

How richly the API is illustrated with examples.

92%

Example Validity

Percentage of examples that conform to their schemas.

71%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

24%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

86%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

15%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: ASignals: 1

84%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the WebScraping.AI to your agent

Capabilities

Start building with WebScraping.AI API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

WebScraping.AI

Jentic AI Readiness Score

WebScraping.AI

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness