## TL;DR

Switching modes is one parameter change, rest of the request stays the same. Unset mode defaults to advanced.

## Fix

1. Switching modes is one parameter change, rest of the request stays the same.
   Expected: You get the expected result; the problem is gone.

## When to use

- You are setting up or using this Parallel Search feature.
- The symptom matches: unset mode silently defaults to advanced (slowest, priciest) , set turbo or fast.

## When NOT to use

- Unrelated Parallel Search issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported against Parallel Search.

## Variant phrasings

### unset mode silently defaults to advanced (slowest, priciest) , set turbo or fast

## Why it happens

Official docs (Search Modes page): documents the mode default gotcha that trips agents on Parallel's Search API. If you leave `mode` unset you silently get `advanced` (~3s latency, $5 per 1,000 requests) even when you wanted something cheaper and faster.

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.