Frequently asked questions
Practical answers, grounded in how the product actually behaves. For workflows, start with Your first scan; for the ideas behind the product, see the concepts section.
How long does a scan take?
It depends on scope — cost and runtime scale roughly linearly with each jurisdiction you add — but an expedited scan typically finishes within a few minutes. The order ticket shows a live runtime estimate (~…) alongside the price before you commit, so you never run blind. In the batch lane, results typically arrive within a few hours instead, with an optional email when they are ready.
What does a scan cost?
The ticket shows a live dollar range for exactly the configuration you have built, recomputed as you change it, with a confidence note — and a footer that says what it is: “Estimate, not a quote.” Two levers move it most: the number of jurisdictions (roughly linear) and the run lane — Batch — later today costs about 50% less than Expedite — run now. The Advanced accordion also shows a live per-engine cost so you can compare the three engines on your actual scan shape.
Why is the Batch option greyed out?
Not every analysis engine has a batch lane. The ticket says so explicitly when the selected engine can only run live; switch engines in the Advanced accordion or run Expedite.
Can I rerun a previous scan?
Yes — the Recent scans list at the foot of the order form covers your entire history, with a filter that searches titles, configuration, scan IDs, and dates. Each row has two actions: Reload fills the form with that scan’s configuration so you can tweak it, and Rerun runs it again as-is.
Can scans run themselves?
Yes. Scheduled scans puts a configuration on a rota — daily, weekdays, weekly, fortnightly, or monthly, at a time you choose — with an optional email each time a run completes. The quickest start is the “Make this a weekly scan” shortcut on the order ticket.
Which jurisdictions and topics are covered?
The order form’s pill lists are a starting set, not the boundary. Built-in jurisdiction pills run from the US, EU and UK through to Brazil and India; built-in areas run from Banking / Prudential to Research Bundling / Unbundling. Both lists are open — Add custom… accepts any jurisdiction and Add an area… any topic, marked ★ in your selection and treated as first-class scan scope. The catalogue the platform tracks is published as data through the API — see Discovery.
What languages are supported?
Seven: English, French, German, Spanish, Italian, Mandarin Chinese, Japanese — for the interface, the scan output (section 05 of the order form), and, where supported, generated artefacts, which follow the dashboard language. One exception: the Debate podcast is English-only, as its label says. Non-English output runs through a translation pass with a locked glossary, so terms of art stay consistent.
What is the Citation audit toggle?
A verification stage: with it on, every claim in the narrative is checked against its source before the dashboard renders. It defaults on for the verified engines; on the classic engine it is opt-in. The toggle in section 05 and the matching station in the Advanced view are the same switch — flipping either updates both.
Where do generated artefacts go?
Every deck, tearsheet, infographic, podcast, and video lands in the Studio archive, grouped by the scan that produced it. The shelf defaults to the current scan; All scans and a searchable scan picker are one tap away. Ready artefacts stay on the shelf and remain downloadable; a failed tile can be retried or deleted.
Can I generate more than one artefact at a time?
Yes. Generate does not block — the button becomes a counter (“1 generating — queue another”) and you can queue further artefacts immediately. Each archive tile tracks its own job through queued → generating → ready.
What happens when a generation fails?
The archive tile flips to failed and shows the error, with Retry (resubmits the identical job) and Delete. The archive footer keeps the cost picture visible — it states the current scan’s artefact spend whenever there is any.
Why does my artefact look different from the Studio preview?
The stage is labelled “Preview — example” — it demonstrates the selected format and style with example content, not your data. Your scan’s content appears in the generated artefact itself, and in the tile’s hover preview once it is ready.
Can I export the raw data?
Yes, two ways. In the app, the header’s Export & Import menu offers Export JSON (the full snapshot) and Export CSV (the item table), plus Import JSON to load an exported snapshot back in. Programmatically, the /v1 API exposes scans, snapshots, and exports.
Do my settings follow me between devices?
Account-level things do: snapshots, schedules, generated artefacts, language, the light/dark theme, and the Studio standing preferences (Expedite, image-generation service). The scan order form always carries forward your last scan’s configuration. See Settings for the full map.