Zyte API
Official vendor OpenAPI document · agent-readyDeveloper ToolsSource Controlbasic1 EndpointsREST
For Agents
Programmatically extract data from a web page. Covers 1 operations with basic authentication.
Use for: I need to extract data from a web page, Find available developer tools operations, Get the current status of Zyte API resources, List all records from Zyte API
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Zyte API provides web data extraction capabilities including HTTP responses, browser HTML, screenshots, and automatic data extraction. The API exposes 1 endpoints secured with basic authentication.
Install Jentic One Beta
Connect the Zyte API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Zyte 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.
1
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%2Fzyte.com%2Fzyte" | sh2
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%2Fzyte.com%2Fzyte" | 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.
Capabilities
What an agent can do with Zyte API.
Extract data from a web page
Manage developer tools data programmatically
Integrate Zyte API into automated workflows
Query and filter Zyte API records by parameters
Monitor Zyte API operational status and events
Use Cases
Patterns agents use Zyte API for, with concrete tasks.
★ Developer Tools Operations
Use the Zyte API to perform developer tools operations programmatically. The API provides 1 endpoints covering core functionality including extract data from a web page.
Call POST /v1/extract to extract data from a web page
Data Retrieval and Monitoring
Query Zyte 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.
Poll the primary Zyte API endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call Zyte 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 basic tokens manually.
Search Jentic for 'extract data from a web page', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
1 endpoints — zyte api provides web data extraction capabilities including http responses, browser html, screenshots, and automatic data extraction.
METHOD
PATH
DESCRIPTION
POST
/v1/extract
Extract data from a web page
POST
/v1/extract
Extract data from a web page
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Zyte API by hand means base-authenticating with your API key against the api.zyte.com host and handling extraction retries yourself. Through Jentic you install once, import Zyte from the API Directory, store the credential once, and your agent calls it.
Permission scoping
The Zyte target is a URL in the request body of its single extract operation, so limit the agent to the operation it needs: web-page extraction. You choose that operation set, so nothing beyond extraction runs unless you add it.
Credential isolation
Your Zyte 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 'extract data from a web page', and Jentic returns the matching Zyte operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Zyte API through Jentic.
What authentication does the Zyte API use?
The Zyte API uses HTTP Basic authentication with username and password. 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 extract data from a web page with the Zyte API?
Yes. Use the POST /v1/extract endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Zyte 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 extract data from a web page through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'extract data from a web page'. Jentic returns the matching Zyte API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Zyte API have?
The Zyte API exposes 1 endpoints covering extraction operations.
Can I limit what my agent is allowed to do with the Zyte API?
Yes. Because you run Jentic One yourself, you decide which Zyte operations your agent can call, and the Zyte API exposes a single extract operation, POST /v1/extract, that takes the target URL in its request body. You grant your agent only that web-page extraction operation, so it cannot invoke anything else unless you explicitly add it. Your Zyte API key stays with your own Jentic One instance and is injected only when that allowed operation runs, never entering the agent's prompt or context.
GET STARTED