Agentql APIs
3 APIs14 Endpoints1 Category
Categories
API Catalog(3 of 3)
AgentQL API
Jentic publishes the only available OpenAPI specification for AgentQL API, keeping it validated and agent-ready. AgentQL extracts structured data from web pages and documents using AgentQL query syntax or natural language prompts. The 0.1.0 spec exposes both versioned (/v1) and unversioned routes for the query-data endpoint plus the Tetra remote Chrome browser session API. Each call returns parsed fields keyed by the names declared in the query, removing brittle CSS or XPath selectors from agent code.
8 endpointsAgentQL API
Jentic publishes the only available OpenAPI specification for AgentQL API, keeping it validated and agent-ready. The main 1.0.0 surface combines AgentQL's web and document extraction with Tetra remote browser session creation behind a single base URL. Three endpoints handle the full flow: query a web page, query a document, or spin up a browser session for sites that need login. Each query call accepts AgentQL syntax or a natural-language prompt and returns parsed fields directly.
3 endpointsAgentQL REST API
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.
Connect Your Agent
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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.