This is also a much more scalable approach than supporting a fat client driver for every single combination of language / integration / OS. It would enable a tinybird.co-like access pattern to our data in MD. A REST endpoint would also allow the (usually local) duckdb engine to run (and be scaled) within MD without having to worry about the details of local vs remote execution in the hybrid execution engine.

I ran into a use case for this this week - specifically in wanting to just verify my creds were okay without having to load the full DuckDB drivers.

If we could use a REST API to do something like "SELECT 1" with a specific API key, this would give a lighter-weight option. While I can see use cases for querying and loading _also_, my use cases this week just wanted to make sure that (1) creds were fine and (2) the database exists.

Would love to see this! There are some budding alternatives such as quackpipe and the httpserver extension, which may work with MotherDuck - but would be wonderful to have something managed by the team. If the response options included CSV as a file - would enable lots of connections with dataviz tools that accept a CSV URL. There are also some that accept JSON via API url and those would also be enabled through this.

My use case: run on Cloudflare worker. Cloudflare analytics engine is a bit new to me and its lack of db management functionality. I only need query and adding data into the data warehouse, not any else special functionality.