Do we have to write AgentQL queries ourselves?

No. Query Data accepts either an AgentQL query or a natural language prompt describing the fields you want, alongside a URL or raw HTML. So a plain description of the data is enough to get structured JSON back.

How do we keep track of what this consumes?

Get AgentQL Usage Statistics returns the current billing cycle dates, lifetime usage limits, per-API-key usage counts and total account usage. Everything runs on the key you connect, so the quota being spent is your own.

Why does Lyro open a remote browser session?

Because pages that need real rendering are driven on AgentQL's remote infrastructure rather than locally. Create Remote Browser Session sets that up, and the query then runs against the live page inside it.

Can Lyro click through a site or submit a form with this?

Not with these three actions. The toolkit covers session creation, one query action and a usage read, so it returns data from a page rather than driving a multi-step flow through it.

Agentql MCP integration

Opens a remote browser session, queries a live page or supplied HTML for structured JSON, and reports usage against subscription limits.

Connect Agentql See all integrations

3actions available

What your agent can do with Agentql

Every action runs live through MCP. Nothing to build, nothing to maintain.

Query data
Lyro extracts structured data from web pages using natural language or AgentQL syntax. Your team pulls live pricing, inventory, or status info from any website in seconds.
Create remote browser session
Lyro opens a remote browser to navigate websites and gather data on demand. Your team automates lookups without asking customers to paste screenshots.

See all 3 actions

How businesses use Agentql + Lyro

Each card is one request a support team gets, and the Agentql actions Lyro runs to close it.

Extract structured data from a live web page
Lyro opens a remote browser session, runs an AgentQL query or plain-language prompt against the URL or HTML, and returns JSON, checking usage against the account's limits on larger runs.
Create Remote Browser SessionQuery DataGet AgentQL Usage Statistics

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Agentql actions it has and picks the ones a request needs.

01
Connect Agentql
Authorize the Agentql account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Agentql actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Agentql · Lyro

Everything else about Agentql

Setup, permissions, and the limits of what Lyro can do inside Agentql.

No. Query Data accepts either an AgentQL query or a natural language prompt describing the fields you want, alongside a URL or raw HTML. So a plain description of the data is enough to get structured JSON back.

Every action available in Agentql

All 3 actions your agent can call on Agentql, straight from the live MCP connection.

Create remote browser session
Create a remote browser session.
Get agentql usage statistics
Retrieves API usage statistics and subscription limits for the AgentQL account.
Query data
Query structured data as JSON from a web page using an AgentQL query or natural language prompt.