Install Jentic One Beta

Connect the Oxylabs Web Scraper API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Oxylabs Web Scraper 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%2Foxylabs.io%2Foxylabs" | 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%2Foxylabs.io%2Foxylabs" | 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 Oxylabs Web Scraper API.

Submit a web scraping job for a target URL and get structured results

Submit a batch of scraping jobs in a single request

Check the status of a running or completed scraping job

Read the parsed results of a finished scraping job

Look up the callback IP addresses Oxylabs delivers results from

GET STARTED

Start building with Oxylabs Web Scraper API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Oxylabs Web Scraper API for, with concrete tasks.

★ Agent-Driven Web Data Collection

An AI agent connected through Jentic submits a scraping job for a target page, waits for it to finish, and reads back the parsed result, so the agent can pull live web data into a workflow without a human running a scraper. Because Oxylabs returns structured output, the agent can act on the fields directly rather than parsing raw HTML.

Submit a scraping job for this product URL, then return the parsed title and price once the job completes

Batch Scraping Pipeline

A data pipeline submits many target URLs in one batch request and then polls each job for completion before reading its results, so a large scrape runs as a single managed step. The pipeline uses the job status endpoint to know when each result is ready.

Submit these fifty URLs as one batch job and collect the parsed results for each as they finish

Firewall Allowlisting for Callbacks

Teams that receive scraping results by webhook first read the list of callback IP addresses Oxylabs uses and add them to their firewall allowlist, so delivered results are accepted rather than blocked. This keeps a push-based delivery setup working reliably.

Fetch the current Oxylabs callback IP addresses so I can add them to the firewall allowlist

Key Endpoints

5 endpoints — the oxylabs web scraper api runs web scraping jobs and returns structured results, so an application can collect data from web pages at scale without managing proxies or headless browsers itself.

METHOD

PATH

DESCRIPTION

POST

/v1/queries

Submit a web scraping job

POST

/v1/queries/batch

Submit a batch scraping job

GET

/v1/queries/{jobId}

Get scraping job status

GET

/v1/queries/{jobId}/results

Get scraping job results

GET

/v1/info/callbacker_ips

Get callback IP addresses

POST

/v1/queries

Submit a web scraping job

POST

/v1/queries/batch

Submit a batch scraping job

GET

/v1/queries/{jobId}

Get scraping job status

GET

/v1/queries/{jobId}/results

Get scraping job results

GET

/v1/info/callbacker_ips

Get callback IP addresses

Why Jentic?

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

Setup

Wiring the Oxylabs Web Scraper API by hand means handling HTTP Basic auth, choosing between the realtime and data delivery hosts, and polling each job until it finishes. Through Jentic you install once, import Oxylabs from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

You choose which operations your agent may call, so you can allow submitting a scraping job and reading its results while leaving anything else out. Oxylabs carries the target in the request body, so your rules bound which operations run, and every call the agent makes is logged.

Credential isolation

Your Oxylabs username and password are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'scrape a page and return results' or 'check a scraping job', and Jentic returns the matching Oxylabs operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using Oxylabs Web Scraper API through Jentic.

Is there an Oxylabs MCP server?

You don't need an MCP server to give your agent the Oxylabs Web Scraper API. Jentic connects it directly from the API Directory: import it, store your credentials once, and your agent can submit scraping jobs and read results straight away, with no extra server to run and no tool definitions to load into the agent's context.

Can I limit what my agent is allowed to do with the Oxylabs Web Scraper API?

Yes. You choose which operations your agent may call, so you can allow submitting a scraping job and reading its results while leaving everything else out. Every call the agent makes is logged, so you can see exactly which jobs it ran.

What authentication does the Oxylabs Web Scraper API use?

The Oxylabs Web Scraper API uses HTTP Basic authentication with your Oxylabs username and password per its OpenAPI spec. Through Jentic the credentials are stored encrypted by your own instance and added to each request at call time, so they never appear in the agent's prompt or logs.

Can I scrape many URLs at once with the Oxylabs Web Scraper API?

Yes. The API accepts a batch of targets in a single request and returns a job for each, so an agent can queue a large scrape in one call and then read each result as it completes. You can also check the status of any job before fetching its result.

What are the rate limits for the Oxylabs Web Scraper API?

The OpenAPI spec does not specify rate limits for the Oxylabs Web Scraper API. For current limits and fair-use guidance, see the Oxylabs documentation at https://developers.oxylabs.io.

How do I run an Oxylabs scraping job through Jentic?

Import the Oxylabs Web Scraper API from the Jentic API Directory, then have your agent issue a request such as 'scrape this page and return the parsed result'. Jentic matches the intent to the submit-job operation and returns its input schema so the agent builds the correct request, with your stored credentials injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Oxylabs Web Scraper API

Name: Oxylabs Web Scraper API
Brand: Oxylabs Web Scraper API
Availability: InStock

AI ReadinessFoundational (D-)40/100

See full scorecard

Official vendor OpenAPI document · agent-readyAnalyticsData Pipelinesbasic5 EndpointsREST

For Agents

Submit web scraping jobs for target URLs, check their status, and read the parsed results in Oxylabs. Authenticates with HTTP Basic authentication using your Oxylabs username and password.

Use for: Scrape a product page and return the parsed result, Submit several URLs as one batch scraping job, Check whether my scraping job has finished, Fetch the results of a completed scraping job

Not supported: Does not handle proxy pool configuration, billing, or account management. Use for submitting Oxylabs scraping jobs and reading their results only.

The Oxylabs Web Scraper API runs web scraping jobs and returns structured results, so an application can collect data from web pages at scale without managing proxies or headless browsers itself. You submit a scraping job that names the target and the parsing options, then read the job's status and its parsed results, either in real time or through batch delivery. A single request can queue one target or a batch of targets, and a helper endpoint lists the callback IP addresses Oxylabs delivers results from so they can be allowed through a firewall.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

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

75%

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: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

45%

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: D+Signals: 4

45%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

50%

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

10%

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

85%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Oxylabs Web Scraper API to your agent

Capabilities

Start building with Oxylabs Web Scraper API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Oxylabs Web Scraper API

Jentic AI Readiness Score

Oxylabs Web Scraper API

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