Skip to main content
Fast mode returns results in about 1 second. The default 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
For most applications, omit 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

Get richer data from each result:
metadata=full adds latency because it fetches additional data from each result page. Use metadata=basic (the default) unless you need contentType or reader data.

Fast mode vs. deep mode

Start with auto — it picks between these per query. Pin fast mode when latency is critical; pin deep mode when thoroughness matters more than speed. See search modes for the full set of modes.

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.