Skip to content

Integration · Data and databases

Agentql in Skyller.

Connect Agentql to Skyller and the AI starts reading from and acting in it through the functions your company enables — with each person's own login, approval before sensitive actions and a record of every call. Below, the actions and events the vendor publishes, what it takes to start and where this fits into the work.

Actions and events

Agentql

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.

Actions
3
Events
0
Composio catalog
API key
Global — no specific country
re-read from the vendor every 24 hours
www.agentql.com

3 ACTIONS

published by the vendor; the company enables only the necessary ones

0 EVENTS

triggers the system can send, when the vendor offers them

API KEY

each person signs in with their own credential, encrypted

APPROVAL BY RISK

sensitive actions show a card before running

Live proof

One request, one query in Agentql and one approval.

The scene shows the path of a request; the exact actions depend on the functions your company enables in Agentql.

  1. Input

    A team member asks, in the conversation, for something that today requires opening Agentql — inside their area's space, with their login.

  2. What Skyller does

    1. 01Picks, among the enabled functions, a query action and looks the information up in Agentql with the person's own credential.
    2. 02If the request requires writing something in Agentql, shows the card with what it is about to do and waits for Approve.
    3. 03Returns the result in the conversation and records who asked, which action was used and when.
  3. Result

    Agentql stops being an open tab and starts answering inside the conversation — through the functions your company enabled.

What this scene does not promise

  • The available actions are the ones the vendor publishes for Agentql; in your company only the functions turned on by the administrator are available.
  • If a write action is not classified as sensitive, it may run without a card; the classification is adjustable by the company.
  • Being in this catalog does not mean being installed, with a valid login, working in your company.

Where this helps your work

Agentql inside the conversation where the work happens.

Three common situations for people who use Agentql every day. What Skyller does in each one depends on the functions your company turns on.

Needing the information now

“What is recorded in Agentql about this?”

The person asks in the conversation and Skyller queries Agentql with their login, through the enabled read functions, and answers with what it found.

System data in the answer

Recording the result

“Log this in Agentql.”

Creating or changing a record is a write action: Skyller shows the card with what it is about to do and waits for Approve before touching Agentql.

Action with approval

Administering

“Enable only what this team needs.”

The administrator connects Agentql once, turns on the necessary functions, restricts them to groups and follows the record of every call.

Function by function, with a record

Actions and events

What the vendor offers in Agentql.

Names as the vendor publishes them, in English, with the description summarized to its first sentence. In your company, the administrator turns on only the necessary actions; none of them runs without permission, and sensitive ones go through approval.

  • Create Remote Browser Session

    AGENTQL_CREATE_REMOTE_BROWSER_SESSION

    Tool to create a remote browser session. Use when you need to run browser automation on remote infrastructure.

  • Get AgentQL Usage Statistics

    AGENTQL_GET_USAGE

    Retrieves 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.

  • Query Data

    AGENTQL_QUERY_DATA

    Tool 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.

Before you start

What your company needs to use Agentql.

Login
Each person enters their own Agentql API key, generated in their account. The key is stored encrypted and nobody sees it, not even the administrator.
Who installs
An administrator connects Agentql for the company and shares it with people or groups. Anyone can connect just for themselves, within the plan's limit.
Functions
3 published actions: the administrator turns on only the necessary ones. Sensitive ones ask for confirmation before running.
Plan
Counts as a company or personal connection within the plan's allowance; the larger plans have no cap. The connections-per-plan table is on the catalog page.

Questions from the people who decide

Common doubts before connecting Agentql.

Next step

Connect Agentql and try it with your team.

Try it free with your team or book a demo: together we pick the Agentql functions to enable and show the first approved action, with fictitious data.