What changed in August 2026
The August 2026 changelog has the full details.
Field type overrides
A new Field Types card on the search extractors page lets you override how a field is indexed. For example, you can index a Unix timestamp field as
int64so that date-range filtering works. Field type overrides are available only on QuantGov projects.A spend cap for AI Search
AI Search now appears in the per-interface spend caps introduced in June. You can cap it on its own, not only through the organisation-wide cap.
AI Search on the usage card
The AI Services usage card on the subscription page shows AI Search as its own line. Page updates and AI answers are listed separately.
Cost of each crawl run
On projects where AI Search is enabled, crawler run rows show the AI Search cost of each run.
Pricing before you enable
When you enable AI Search, the dashboard now shows its usage-based pricing. You must acknowledge it before the feature turns on.
Extractors page fix
An empty dialogue could appear over the search extractors page after an interaction and block every click. This is now resolved.
Who it is for
QuantGov search teams
Index a Unix timestamp field as
int64so that date-range filtering works for search on your QuantGov projects.Budget owners
Ask an organisation admin to cap AI Search spend, and see page updates and AI answers as separate usage lines.
Site teams that crawl
See the AI Search cost of each crawler run in the crawler run rows, on projects where AI Search is enabled.
How it works
A search extractor copies content from your pages into the fields of their search records. The new Field Types card is on the same page. Use it to override how a field is indexed.
For example, your pages can hold a date as a Unix timestamp. When you index that field as int64, date-range filtering works on it.
When you change a field type, the search index rebuilds. Search stays available during the rebuild, so your visitors can continue to search. Field type overrides are available only on QuantGov projects.
For AI Search, you can now see or limit the cost in four places:
- Spend caps: AI Search has its own place in the per-interface spend caps introduced in June. Organisation admins set these caps in AI governance. Before this change, you could cap it only through the organisation-wide cap.
- Usage card: the AI Services usage card on the subscription page lists AI Search page updates and AI answers separately.
- Crawler runs: on projects with AI Search, each crawler run row shows the AI Search cost of that run.
- Enabling: before AI Search turns on, the dashboard shows its usage-based pricing and asks you to acknowledge it.
AI Search is billed by usage. The cost increases when you crawl or publish more often, so frequent crawls of a large site cost more. Use the crawler run rows to see which runs add the most cost.
Get started
Open Field Types
Use the Field Types card on the search extractors page of a QuantGov project.
Set the field type
Choose
int64for a Unix timestamp field, so that date-range filtering works.Cap AI Search spend
Ask an organisation admin to add an AI Search cap in AI governance.
Check the usage card
Find AI Search as its own line on the AI Services usage card.
Read about cost
Related: Explore Quant Search · Documentation · August 2026 changelog
Ready to try it on Quant?
Use Quant Search on your own project, or read the docs first.