auto mode already resolves simple queries fast — pin searchMode=fast when you need that latency guaranteed on every call, such as real-time applications and high-volume workloads. Equivalent to effort=low, if you use the generic effort dial instead of naming a mode.
When to pin fast mode
- Real-time search in user-facing applications with a hard latency budget
- High-volume automated queries
- Applications where latency matters more than exhaustive coverage
searchMode and let auto decide — it resolves simple queries fast on its own. See search modes for the full set.
Example response
Parsing the response
Adding extracts and metadata
Adding extracts and metadata
Get richer data from each result:
Fast mode vs. deep mode
Next steps
Deep mode
Multi-angle search with spell correction.
Search modes
Automatic effort by default, manual control when you want it.
Basic search example
Complete integration with error handling.
Response format
Response structure and metrics.

