AgentQL API

What authentication does the AgentQL API use?

AgentQL uses an API key passed in the X-API-Key request header. Through Jentic the key is held in the credential vault and injected at execution time, so the raw value never reaches the agent's context.

Can I scrape sites that require login with AgentQL?

Yes, by using Tetra. POST /tetra/sessions to create a session, drive it through the login flow, then run /query-data calls scoped to that session id. Static page queries against /query-data alone do not handle authentication.

What are the rate limits for the AgentQL API?

Limits are enforced as monthly query and Tetra-minute quotas tied to your plan rather than a hard requests-per-second cap. Build retry-with-backoff into the agent for 429 responses.

How do I extract structured data from a URL through Jentic?

Run the Jentic search 'extract structured data from a web page'. Jentic returns the POST /query-data operation; load its schema, supply the url and an AgentQL query like '{ products[] { name price } }', and execute. The parsed object comes back in the response.

Does AgentQL accept natural language instead of AgentQL syntax?

Yes. Both /query-data and /query-document accept a prompt parameter. The shape of the returned JSON is inferred from the prompt rather than declared explicitly in a query.

Can I limit what my agent is allowed to do with the AgentQL API?

Yes. Because you run Jentic One yourself, your own rules decide which AgentQL operations the agent may call, so you can allow only structured extraction from a web page (POST /query-data) or a document (POST /query-document) and keep those in the permitted set. Since browser session creation (POST /tetra/sessions) is not included unless you add it, an agent scoped to extraction alone cannot spin up a Tetra session. Your API key is held by your own instance and injected as the X-API-Key header at execution time, so it never reaches the agent's context.