What this is. Complementary to subagentworkers.com: that site does prose RAG over Cloudflare's docs, this one does natural-language-to-SQL over the subagentjobs ecosystem's own structured data.
How it works. Your question + the target database's schema go to Cloudflare Workers AI (@cf/zai-org/glm-5.2), which returns a single SQL query. That query is validated — must be a single SELECT, no other statement types, every referenced table checked against an explicit allowlist — before it runs against the real D1 database. The results go back to the same model for a plain-English explanation.
No external API keys, anywhere. Generation is Workers AI via a native [ai] binding. All three databases are bound directly to this Worker rather than reached through the Cloudflare API, so there's no Cloudflare API token either.
Scope, deliberately. Only three databases are bound: subagentjobs-dwh, subagentworkers-dwh, and subagentdb itself — not the other ~50 Workers/databases in this Cloudflare account, most of which belong to unrelated systems (agent memory stores, telemetry, control planes) that have no business being queryable from a public site.
Sister site. subagentworkers.com · subagentjobs.com