Skip to content
Raw Markdown

Ask in the web app

Open a project's Chat and ask in plain language. Cassis answers from the published ontology and shows the reasoning and SQL behind the result.

Sign in at app.getcassis.com, choose a project, and open Chat.

1. Question with no judgment call
Runs automatically, with the plan shown for transparency plus the SQL and result so anyone downstream can verify.
Cassis · Formula 1 project
Who won the most races in 2023?
Max Verstappen won 19 out of 22 races in 2023, far ahead of Pérez (2) and Sainz (1).
sql: SELECT d.full_name, COUNT(*) FROM public.results r
  JOIN public.races ra ON r.race_id = ra.race_id
  JOIN public.drivers d ON r.driver_id = d.driver_id
  WHERE ra.year = 2023 AND r.position = 1
  GROUP BY d.full_name ORDER BY 2 DESC

objects_used: public.results, public.races, public.drivers
Show SQL đź‘Ť / đź‘Ž Add as test case
2. Plan, then execution
A question with a genuine fork pauses on the plan first. Review or switch the assumptions and objects, then run it.
Cassis · Formula 1 project
Compare total points scored by all drivers in 2022 vs 2023, including sprint results.
Proposed query plan
UNION query combining the public.results and public.sprint_results tables, grouped by season.
public.races public.results public.sprint_results
Assumptions:
· Sprint points included in the total
· Points rolled up across all drivers per season
Run plan
Across 2023 drivers scored 2,458 points combined, slightly ahead of 2022 at 2,350. Sprint points are included in both totals.
3. Follow-up in the same chat
The chat holds its context, so follow-ups reference earlier results without restating the scope.
Cassis · Formula 1 project · continued
Now break it down by constructor for 2023.
Grouped by constructor in 2023: Red Bull Racing 860, Mercedes 409, Ferrari 406, McLaren 302, and six more.
objects_used: public.constructor_standings, public.constructors

Read the answer

Plan
Cassis shows how it interpreted the question. If there is a genuine choice, it waits for you to confirm or change the assumptions before running SQL.
SQL
Show SQL expands the exact statement behind the answer.
Provenance
The answer names the ontology objects it used, so you can spot an unexpected table, metric, or join.
Feedback
Rate the answer and explain what was wrong. Corrections become evidence for the review queue.

Use Add as test case only after someone validates the SQL and its business interpretation. That turns a useful answer into a regression case; see Build and run evals.

Keep corrections in the conversation

A chat belongs to the person who started it. Writing a correction in the thread—“active means billed this month”—gives Cassis evidence it can turn into a reviewed context improvement.

On a schema-only project, Cassis returns grounded SQL without executing it, so results is null. That is different from a query that ran and returned zero rows. See Connect a warehouse or upload DDL.

For a deeper explanation of plans and provenance, see Understand an answer.