Queries in the dashboard.

Five query shapes from one tabbed panel: SQL, Vector, Full-text, Graph, and Ask. You'll need a running instance and the engine bearer (Ask uses your console session and works without a bearer paste).

1. 1. Open /app/query.
2. 2. Pick the instance, paste the bearer.
3. 3. Click the tab for the shape you want.
4. 4. Fill the request fields, click Run →. Results render in the panel below the editor.

SQL tab

Standard SQL editor. The EXPLAIN checkbox routes the same query through the operation-backend proxy at /v1/instances/:id/query?explain=true and returns the chosen plan tree, the access path per table, and the row-count estimate at each node.

SELECT id, email, region
  FROM shop.customers
 WHERE region = 'us-east-1'
 LIMIT 50;

Vector tab

HNSW topk with optional metadata equality filter. Pick the table, the metric (cosine / dot / l2), and a mode. high_recall is the default — recall@10 = 0.96 at 100k vectors with p99 109 ms. fast trades recall for latency at p99 37 ms / recall 0.69.

Full-text tab

BM25 / boolean / phrase modes over a per-tenant inverted index. Lucene defaults (k1=1.2, b=0.75). Pick the table, the field, and the mode; type the query.

Graph tab

Pick a schema, an op (neighbors, reverse, bfs, path, dijkstra), and supply the source ids. Direction tags on the schema's relations decide whether reverse traversal is allowed.

Ask tab

Type an English sentence. The first call compiles a Plan tree against your registered schemas; every repeat hits the cached plan at p50 < 2 ms. Ask uses your console session — the bearer above is not required.

Show me every customer in us-east-1 created last week

Common errors

• addon required — vector / FTS / graph need their respective add-ons. The result panel surfaces a banner with a one-click Enable add-on link to /app/billing/addons.
• 401 unauthorized on SQL/Vector/FTS/Graph — bearer paste is wrong; rotate from /app/keys. Ask is unaffected (it uses cookie auth).
• 429 too many requests — your per-key rate limit hit; the response includes a Retry-After header.
• instance not running — resume the instance from /app/instances.
• no plan compiled on Ask — the rule grammar couldn't resolve the question. Either rephrase, or scope the catalog with --schema filters in the SDK.