Boyce

This is a semantic layer that sits between your LLM and your database to prevent the classic agentic SQL failure modes: hallucinated columns, missing joins, and the null trap where syntactically correct queries return silently wrong results. It ingests dbt manifests, LookML, DDL, or ten other schema sources into a graph, then exposes MCP tools like ask_boyce for natural language to deterministic SQL compilation and query_database for live Postgres or Redshift execution. The compiler runs without an LLM in the loop, so identical filters produce byte-identical SQL. Every query gets an EXPLAIN preflight check before execution. Reach for this when you're building agents that need to query production databases reliably, or when you're tired of debugging why your agent's SELECT statement returned plausible garbage at 2am.