Cloudflare moves AI Search billing to December and changes the default refresh interval

Cloudflare moved AI Search billing to December and changed the default indexing refresh interval.

**Dek:** Cloudflare’s November 2 notice sets a December 1 billing start and changes the default sync interval from six to 24 hours. The two changes affect operating cost and index freshness separately.

Cloudflare announced on November 2 that usage-based billing for AI Search will begin on December 1, 2026, a month later than the previous schedule. Cloudflare says it will not charge for AI Search usage before that date and that prices and included usage are unchanged. The same notice lengthens the default interval at which an AI Search instance synchronizes its source, from six hours to 24. Operators can still choose a supported interval from 15 minutes to 24 hours in settings or through the API. [Cloudflare AI changelog](https://developers.cloudflare.com/changelog/product-group/ai/)

How index freshness changes an answer

Search used by an assistant depends on which documents have reached its index. When a team replaces a help article, the old version may still affect answers until the next synchronization. The change in the default means a deployment that accepts default settings can refresh less often than a team expected. An explicit interval lets the team choose a cadence for the kind of material it indexes. A product manual that changes rarely may be fine on a daily sync, while a live support policy can need more frequent refresh. [Cloudflare AI changelog](https://developers.cloudflare.com/changelog/product-group/ai/)

Operators can check a real retrieval path by changing a known document and measuring when searches consistently return the new version. A check should include an updated document and one that has been removed or replaced. That helps distinguish a freshness problem from a ranking or response problem. If the application must reflect a change within a defined window, the configured sync interval should be part of the acceptance evidence.

The billing delay is time to measure actual usage

A team planning for December can inventory its search instances and look at ingestion, storage and query activity before estimating costs. The provider’s notice changes the date charges begin. It does not imply that usage will fit into a given team’s included allowances. Choosing an interval also has an operational cost when content changes frequently, so the answer should come from the application’s freshness needs and measured workload. [Cloudflare AI changelog](https://developers.cloudflare.com/changelog/product-group/ai/)