AI SQL Query Tool for Postgres, MySQL, Snowflake, and BigQuery
One read-only connection, one plain-English question, and the SQL plus the answer come back together. Pick your database to see how the connection works.
Read-only by design · shows the SQL every time · Last updated July 2026
Ask your data a question:
Writing SQL… Running (read‑only)… SQL Agentsql wrote
▋
Click a question. Agentsql writes the SQL, runs it read-only, and answers.
Direct answer
An AI SQL query tool connects to the database you already run, turns a plain-English question into SQL, executes it, and returns the result. Agentsql supports Postgres, MySQL, Snowflake, and BigQuery, connects with a read-only role or service account so it can never write, and shows the exact query behind every answer. Setup is a least-privilege credential and a connection string, not a data migration.
›_ pick your database
Four engines, one way of asking.
Each page covers how the read-only connection is granted on that engine, the questions people actually ask it, and the honest tradeoffs.
PostgreSQL
Natural Language to SQL for Postgres: Chat With Your Postgres Database
Point Agentsql at your Postgres database with a read-only role, ask a question the way you would ask a teammate, and get the query, the chart, and the answer together.
Read the Postgres guide →MySQL
Natural Language to SQL for MySQL: Ask Your MySQL Database in Plain English
Connect Agentsql to MySQL or MariaDB with a read-only user, ask in plain English, and get the SQL, the chart, and the answer in one pass.
Read the MySQL guide →Snowflake
Snowflake Natural Language Query: Ask Snowflake in Plain English, Get the SQL
Give business users a safe way to ask Snowflake questions themselves, on a read-only role, on a small warehouse, with every query visible.
Read the Snowflake guide →Google BigQuery
BigQuery Natural Language to SQL: Ask BigQuery in Plain English
Ask BigQuery a question in plain English. Agentsql writes the standard SQL, runs it read-only on your dataset, and returns the chart, the table, and the answer.
Read the BigQuery guide →›_ the same on every engine
Three things hold true whichever database you connect.
It only ever reads
You grant a read-only role, user, or service account. The boundary is enforced by your database and your cloud, not by a setting inside our app, so no question can ever change a row. See read-only by design.
It shows the SQL
Every answer arrives with the exact query that produced it. That is how a non-engineer gets to trust the number and how an engineer verifies it in seconds. See text-to-SQL.
It closes the loop
A chart, a result table, and one plain-English line come back together, so an ad-hoc question stops being a ticket. See charts and dashboards.