Skip to main content
Released: September 8, 2026 /search now takes a tier parameter that picks between latency and result quality. pro — the default — is quality-oriented: the most relevant results are ordered to the top. base is latency-oriented: responses come back faster, with less precise ordering near the top.

Highlights

  • New tier parameter — Choose pro (default, optimized for quality) or base (optimized for latency).
  • Independent of scopetier picks the latency/quality trade-off, scope picks which data is searched; every scope accepts either tier.
  • Opt-out, not opt-in — Omitting tier gives you pro, so existing calls keep the ordering they already had. Send base explicitly when latency matters more.
  • Strict on names — Matched case-insensitively with whitespace trimmed, but an unrecognized tier is rejected rather than quietly defaulted, so you are only ever served the tier you named.
  • Available everywhere — This setting is supported in Python SDK 1.13.0, TypeScript SDK 2.10.0, and REST POST /v1/search.

Quick Start

Choose a search tier

When to reach for base over the default pro

API Reference

Full tier parameter specification