Warehouse questions
Ask how many orders a customer placed last quarter and Memtro writes the GoogleSQL, runs it and cites the table.
Read-only GoogleSQL over your BigQuery warehouse, with a dry run before every expensive scan.
Give Memtro a service account with viewer roles and the model can browse datasets, read table schemas and run SELECT queries. It dry-runs first when a scan could be large, so you see bytes processed before you pay for them.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right BigQuery tool, reads what it needs, and answers with the source cited.
Ask how many orders a customer placed last quarter and Memtro writes the GoogleSQL, runs it and cites the table.
It dry-runs first when a query could be large, so you see the bytes scanned before paying for them.
Questions people ask once BigQuery is connected. In agent mode each one also checks the other systems that know about the same people, companies or identifiers.
Teams that get the most from BigQuery in Memtro, with the rest of their stack attached.
A record in BigQuery is rarely the whole story. Connect the systems that hold the rest and the agent cross-references them by default, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The BigQuery tools are the same everywhere.
Clients and agents →Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.