AgentQL REST API

Name: AgentQL REST API API
Brand: AgentQL REST API
Availability: InStock

★ Only Publicly Available SpecAI/MLMl InferenceapiKey3 EndpointsREST

For Agents

Run a single AgentQL query against a web page or document and get structured fields back, or create a remote Chrome session for authenticated scraping.

Quickstart

Get started with AgentQL REST API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"extract structured data from a web page"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with AgentQL REST API API.

Extract named fields from a public web page using AgentQL query syntax via POST /query-data

Pull invoice numbers, totals, or contract terms from PDFs and images via POST /query-document

Provision a Tetra remote Chrome session for sites that require login or interaction via POST /tetra/sessions

Use natural-language prompts as an alternative to AgentQL syntax on either query endpoint

GET STARTED

Start building with AgentQL REST API API

Explore with Jentic

View OpenAPI Spec

Use for: Extract product names and prices from a marketplace listing page, Get the invoice total and due date from a PDF supplier invoice, Find the contact phone number on a company about-us page, Set up a remote browser session to scrape a site that requires login

Not supported: Does not handle proxy rotation, CAPTCHA solving, scheduled crawls, or dataset storage — use for one-off structured extraction from URLs and documents only.

Jentic publishes the only available OpenAPI specification for AgentQL REST API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for AgentQL REST API, keeping it validated and agent-ready. The 1.0.0 surface is the slimmest production cut of AgentQL: three endpoints that cover web-page queries, document queries, and Tetra remote browser session creation. Each request takes a target (URL or document) plus an AgentQL query or natural-language prompt and returns parsed fields keyed by the query shape. Everything else — pagination, scheduling, dataset storage — is intentionally out of scope.

★ One-Shot Web Page Query

Send a target URL and an AgentQL query to /query-data and receive a parsed JSON object matching the query's named fields. The agent skips HTML parsing, selector maintenance, and DOM traversal entirely. Best for occasional or low-volume extraction where a single request resolves the task.

POST /query-data with url='https://example.com/products' and query='{ products[] { name price sku } }' and write the result to a CSV

Document Field Extraction

Pass a PDF or image URL with a prompt or AgentQL query to /query-document to extract invoice fields, contract clauses, or form values. The endpoint handles OCR and layout-agnostic field naming. Suitable for accounts-payable workflows or contract intake without per-template parsers.

POST /query-document with a PDF URL and the prompt 'extract supplier_name, invoice_number, total_amount, currency'

Authenticated Scraping Setup

Create a Tetra browser session, drive it through a login flow with the returned session controls, then issue /query-data calls scoped to the session. Useful for SaaS dashboards or member-only content where direct GET requests fail.

POST /tetra/sessions, complete the login flow, then run a query-data call against the post-login analytics page

Agent-Driven Field Discovery

Let a Jentic-connected agent iterate on AgentQL query shapes until the target page yields the fields it needs. The agent loads the /query-data schema once and adjusts the query string in subsequent calls without redeploying. This makes the v1 surface a clean default tool for ad-hoc scraping inside a multi-step plan.

Try three progressively more specific AgentQL queries against the same URL and pick the one that returns the most non-null fields

Key Endpoints

3 endpoints — jentic publishes the only available openapi specification for agentql rest api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/query-data

Query data from a web page

POST

/query-document

Query data from a PDF or image

POST

/tetra/sessions

Create a remote browser session

POST

/query-data

Query data from a web page

POST

/query-document

Query data from a PDF or image

POST

/tetra/sessions

Create a remote browser session

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AgentQL API keys are stored in the Jentic vault and injected as the X-API-Key header at call time. The agent never sees the raw value.

Intent-based discovery

Agents search by intent (e.g. 'extract a PDF invoice') and Jentic returns the matching /query-data or /query-document operation with its input schema, including the AgentQL query string format.

Time to first call

Direct AgentQL REST integration: 1-2 hours for auth and query construction. Through Jentic: under 10 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Browserless

Raw headless Chrome as a service without an extraction query layer

Choose Browserless when the agent already has selectors and wants raw HTML, screenshots, or PDF generation rather than parsed fields.

Alternative

Apify API

Site-specific pre-built scrapers (Actors) with dataset storage

Choose Apify when the agent needs a maintained scraper for a major site (Google, Amazon, LinkedIn) rather than authoring queries per page.

Complementary

ZenRows

Proxy rotation and anti-bot bypass to reach blocked targets

Use ZenRows to fetch a tough target page, then hand the rendered HTML to AgentQL for structured extraction.

FAQs

Specific to using AgentQL REST API API through Jentic.

Why is there no official OpenAPI spec for AgentQL REST API?

AgentQL does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AgentQL REST API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the AgentQL REST API use?

AgentQL uses an API key in the X-API-Key header. Through Jentic the key lives in the credential vault and is injected at execution; the raw value never reaches the agent.

Can I extract fields from a PDF invoice with the AgentQL REST API?

Yes. POST /query-document with a PDF URL and either an AgentQL query or a natural-language prompt naming the fields you need. The response is a JSON object keyed by those field names.

What are the rate limits for the AgentQL REST API?

Rate limits are tied to your plan's monthly query and Tetra-minute quotas rather than a fixed requests-per-second cap. AgentQL throttles abusive bursts at the network layer; build retry-with-backoff for 429 responses.

How do I extract data from a single web page through Jentic?

Use the Jentic search 'extract data from a web page'. Jentic returns POST /query-data; load its schema, supply the url and your AgentQL query (or prompt), and execute. The parsed object is returned in the response body.

Do I need a Tetra session to scrape every page?

No. Public pages are handled by /query-data and /query-document directly. Use POST /tetra/sessions only when the target site needs login, JavaScript interaction, or cookie-based gating that the static endpoints cannot reach.

AgentQL REST API

Quickstart

Capabilities

Start building with AgentQL REST API API

Use Cases

Key Endpoints

Why though Jentic?

Related APIs

FAQs