Ask a question in plain language. The engine plans which of its tools to call, runs them against Scrutica’s records, and cites the records they return. How answers are produced
10 corrections · latest 22 Oct 2026
- 22 Oct 2026 · Concentration Monitor: supplier shares for four rows that their own source lines called editorial estimates
- 26 Sep 2026 · Concentration Monitor: supplier shares for three rows that no cited source gives
- 26 Sep 2026 · Concentration Monitor: trajectory labels that the evidence on their own cards did not support
- 26 Sep 2026 · Facility class: 864 records read “Hyperscale DC”, a class no source states
- 25 Sep 2026 · Facility class: country pages printed a class the record withholds
- 25 Sep 2026 · Supply chain: 630 partnerships were listed as suppliers and customers
- 25 Sep 2026 · Colossus 1: Anthropic’s compute agreements with SpaceX
- 25 Sep 2026 · Sovereign AI: the United States procurement figure counted records rated unrelated to AI, and advertised budgets as spending
- 24 Sep 2026 · Query Builder: three EU procurement records built from misread notices are withdrawn
- 5 Sep 2026 · Unsupported supply-chain values withheld
How an answer is assembled
The engine writes a plan first: which tools it will call, in what order, and which calls wait on an earlier result. The page draws the plan as it arrives, and the calls then run, in parallel where they are independent. A question has at most 8 data-tool calls across every round; calls past that budget are not run, and the answer is written from what was gathered.
The answer cites the records the tools returned: each supported clause carries a numbered marker, and the source list beside the answer has one row per cited record, saying what the record is, the source the tool returned for it, its authority tier where the tool returned one, and its estimate flag and date, with the tool and record identifier in its details. After the answer has streamed, the server checks that each cited identifier was returned in that run by the tool the citation names, and marks any it cannot find unverified provenance. The check does not establish that the record supports the claim. The model failover chain, the tag grammar and the matching rule are at the query-engine methodology.
55 tools; at most 8 data-tool calls per question
Search: —
55 available tools.
tools available to the query engine.
distinct fixed-list values across 45 parameters, including logic_fab and eu-ai-act.
Search above or try an example:
Scope
The tool reference lists the available searches and analyses. When a requested figure is missing, the model is instructed to say so. Revenue projections, for example, require a source that supplies a forecast. The model can explain regulations and threshold calculations; case-specific legal advice is outside its remit.
The subject box on the figure above matches against the catalogue in the browser and runs no query.