The server executes SQL queries in a real ephemeral database, returning typed errors with suggestions, execution plans, and diffs to help validate and optimize SQL behavior.

🛠️ Key Features

Executes SQL against a real ephemeral database
Typed error reporting with actionable suggestions
Provides execution plans and query diffs
Lightweight, focused tooling for SQL verification
Supports multiple tools (toolCount: 5)

🚀 Use Cases

SQL correctness verification in ephemeral environments
Debugging complex queries with error hints
Analyzing query plans to optimize performance
Comparing diffs across query iterations
Safe experimentation without affecting production data

⚡ Developer Benefits

Clear, typed feedback on SQL errors
Insightful plans and diffs to guide optimization
Reproducible ephemeral database context
Integrates into developer workflows for rapid iteration
Comprehensive toolset (5 tools) for varied scenarios

⚠️ Limitations

Ephemeral database context means no long-term state preservation
Diagnostic outputs depend on the underlying database capabilities
Not a replacement for full-fledged production-grade DB tooling

schema	string	required	DDL statements (CREATE TABLE ...; multiple statements allowed).
query	string	required	ONE SQL statement to execute. Stacked statements are rejected.
seed	object	optional	Optional seed rows: {"table_name": [{"col": value, ...}, ...]}. Max 10MB total.
engine	string	optional	Engine. Server-side supports 'sqlite' (default). 'duckdb' runs in the browser demo at sqlai.dev only.

schema	string	required	DDL statements.
query	string	required	ONE SQL statement to validate.
engine	string	optional	Engine. Server-side supports 'sqlite' (default). 'duckdb' runs in the browser demo at sqlai.dev only.

schema	string	required	DDL statements (include your indexes!).
query	string	required	ONE SQL statement to explain.
engine	string	optional	Engine. Server-side supports 'sqlite' (default). 'duckdb' runs in the browser demo at sqlai.dev only.

schema	string	required	DDL statements.
queries	array	required	Up to 10 statements, one per entry.
seed	object	optional	Optional seed rows: {"table_name": [{"col": value, ...}, ...]}. Max 10MB total.
engine	string	optional	Engine. Server-side supports 'sqlite' (default). 'duckdb' runs in the browser demo at sqlai.dev only.

schema	string	required	DDL statements.
seed	object	optional	Optional seed rows: {"table_name": [{"col": value, ...}, ...]}. Max 10MB total.
query_a	string	required	Original query.
query_b	string	required	Refactored/alternative query.
engine	string	optional	Engine. Server-side supports 'sqlite' (default). 'duckdb' runs in the browser demo at sqlai.dev only.

sqlai.dev SQL Verifier

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

run_sql

validate_sql

explain_plan

run_sql_batch

diff_results

Install

Remote endpoint