AgentQL is a suite of tools designed to connect AI agents to the web, enabling web interaction and structured data extraction through a specialized query language.
AgentQL is a suite of tools designed to connect AI agents to the web, enabling web interaction and structured data extraction through a specialized query language. On Nagent, Agentql is exposed as a fully-configurable ai web scraping integration that any agent can call — 3 actions, and API key authentication. No code is required to wire Agentql into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Agentql to automate the kinds of tasks ai web scraping teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Agentql into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Agentql, with input parameters and output schema. Drop these into any step of an agent built in Helix.
AGENTQL_CREATE_REMOTE_BROWSER_SESSIONTool to create a remote browser session. Use when you need to run browser automation on remote infrastructure.
Input parameters
Proxy configuration for the remote browser session.
Browser rendering mode. 'light' provides fast headless browsing. 'stealth' enables anti-detection features for sites that block bots. Defaults to 'light' if not specified.
User agent preset to simulate different operating systems. Defaults to 'linux' if not specified.
Session inactivity timeout in seconds. The session will be automatically terminated after this period of inactivity. Defaults to 300 (5 minutes).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
AGENTQL_GET_USAGERetrieves API usage statistics and subscription limits for the AgentQL account. Returns current billing cycle dates, lifetime usage limits, API key usage counts, and total account usage. Useful for monitoring quota consumption and planning usage. No parameters required - uses the authenticated API key from connection settings.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
AGENTQL_QUERY_DATATool to query structured data as JSON from a web page using an AgentQL query or natural language prompt. Use after defining your query or prompt and a URL or HTML.
Input parameters
URL of the public web page to query. Provide either 'url' or 'html'.
Raw HTML content to query. Provide either 'html' or 'url'.
AgentQL query string. Provide either 'query' or 'prompt'.
Parameters controlling wait time, scrolling, extraction mode, and screenshot.
Natural language prompt describing data to extract. Provide either 'prompt' or 'query'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 48 agents privately built on Nagent that already use Agentql.
Build on Nagent
Connect Agentql to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Agentql, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Agentql is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Agentql is connected, you configure its 3 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Agentql steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Agentql event fires, the agent kicks off automatically.
Every Agentql action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Agentql ships with 3 pre-built ai web scraping actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Agentql together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Agentql-based workflows tailored to your business.