/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
tierparameter — Choosepro(default, optimized for quality) orbase(optimized for latency). - Independent of
scope—tierpicks the latency/quality trade-off,scopepicks which data is searched; every scope accepts either tier. - Opt-out, not opt-in — Omitting
tiergives youpro, so existing calls keep the ordering they already had. Sendbaseexplicitly 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 SDK2.10.0, and RESTPOST /v1/search.
Quick Start
Choose a search tier
When to reach for
base over the default proAPI Reference
Full
tier parameter specification