When a Kimi Search Pro response misses the evidence you need, repeating the request with synonyms is not the most useful next step. First decide what was underspecified: the entity, the period or version, the source scope, or the question itself.
The reason is concrete: Kimi’s web-search best-practices guide says text_query is searched as submitted, without automatic rewriting, completion or expansion. The guide also states that calls are billed per request. Query construction is therefore a decision to make before another paid call—not something to assume the service will repair.
This is an explanation of the documented interface, not a release announcement. The source was captured on September 18, 2026; its publication date is not established.
Refine one information need, not just its wording
Kimi recommends making three things explicit:
- Entity: name the product, organization, person or event rather than a broad category.
- Time or version: specify the year, quarter or version relevant to the question.
- Angle or source type: say whether you need official documentation, an announcement, reporting or discussion.
For an illustrative documentation search, “search filters” is less specific than “Kimi Search Pro sites time_window official documentation.” If the missing information is how site restrictions interact with date restrictions, that is a related follow-up worth expressing in the same query. A separate question about another product’s subscription plans is not.
The guide recommends consolidating follow-ups about the same information need and describes substantial overlap between near-identical queries. That is the documentation’s rationale for avoiding synonymous retries, not a measured overlap rate or a guarantee that one longer query will recover every useful source. A more complete question is the goal; a bag of unrelated questions is not.
Ranking hints and scope restrictions are different controls
| What you need | Control documented by Kimi | What not to assume |
|---|---|---|
| Prefer a source type | Include wording such as “official documentation” in text_query |
That wording is not the same as a site restriction. |
| Restrict the source sites | Set sites, with at most five sites, combined with OR |
Adding more sites does not require each result to match all of them. |
| Express the relevant year or version | Include it in text_query; time words affect search and ranking |
A year in the query is not a publication-date filter. |
| Restrict when pages were published | Set time_window start/end values; supported date formats are YYYY, YYYY-MM, and YYYY-MM-DD |
Publication time is not necessarily the date of the event discussed. |
My recommendation is to use restrictions only when they express a real requirement. If only approved official sites are acceptable, sites makes that requirement explicit. If the question concerns an older event but later retrospective analysis is useful, a narrow publication window could exclude relevant evidence. Query time words and time_window can be combined, but they solve different problems.
A higher score on the next call is not proof of improvement
The guide defines chunks[].score as relevance between a chunk and the query. Its warning is important: scores have relative meaning only within the same query; do not compare absolute values across queries.
That rules out using a larger score after a rewrite as evidence that the second search is better. It also gives no basis for a universal cutoff such as “accept every chunk above this number” across all requests. Nor should a relevance score be read as a probability that a passage is factually correct.
For a web-grounded answer, inspect whether the passage actually supports the requested claim and retain its source link. Relevance to a question and support for an answer are different judgments.
A practical check before the next request
For an agent or RAG integration, I would use this small diagnostic sequence:
- Write down the missing evidence. “Need the documented site-count limit” is actionable; “results look weak” is not.
- Change the request for a reason. Add an entity, version or source qualifier; apply or relax a scope restriction when the information need warrants it. Do not merely swap synonyms.
- Keep the comparison reproducible. Record the original and revised query, site restrictions, date window and returned source links.
- Judge the revision by the missing evidence, not the score delta. Did it return a passage that answers the unresolved question? If not, identify a different source angle rather than treating another similar call as progress.
This is a suggested evaluation procedure, not a tested recall improvement or a quantified cost saving. The useful distinction is simpler: another call should pursue a defined evidence gap. Query-relative scores can help interpret that call’s chunks, but they cannot certify that the next call was worth making.