Can AI agents automate QuestDB?

QuestDB is automatable today through its REST API. This record is the QuestDB time-series database. It is not InfluxDB or ClickHouse. The REST API listens on port 9000. GET /api/v1/sql/execute runs a SQL statement and returns JSON. POST is not supported for that call and returns 405. The older path /exec still accepts the same parameters. POST /imp imports CSV. GET /exp exports a query as CSV, or as Parquet when fmt=parquet. Open Source authentication is HTTP Basic after http.user and http.password are set in server.conf. Enterprise also accepts Authorization: Bearer with a REST API token, and the docs prefer that token over Basic. The Web Console is the official web client of this API. QuestDB publishes github.com/questdb/mcp-server-questdb, a bridge that creates notebook cells, runs queries, and builds charts inside a browser session that is already signed into the console. The agent must pair with a one-time token, and the console expects a matching bridge version. A language SDK, a management CLI, and connector catalogs were not opened. Computer-use viability is unassessed. The REST API scores 7 and is the best path. The console bridge scores 4.

Best path today: api · Overall automatability: 7/10