> ## Documentation Index
> Fetch the complete documentation index at: https://docs.parallel.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Places API Modes

> Choose between the fast and advanced Places API modes

For AI agents: a documentation index is available at [https://docs.parallel.ai/llms.txt](https://docs.parallel.ai/llms.txt). The full text of all docs is at [https://docs.parallel.ai/llms-full.txt](https://docs.parallel.ai/llms-full.txt). You may also fetch any page as Markdown by appending `.md` to its URL or sending `Accept: text/markdown`.

For Search and Extract, use `/v1/search` and `/v1/extract` for all new integrations and agent tool calls. Use `/v1beta/search` and `/v1beta/extract` only when maintaining an existing integration that already uses them. The request bodies changed too: on `/v1/extract`, `full_content`, `fetch_policy` and `excerpt_settings` go inside `advanced_settings`, and sending the v1beta top-level `excerpts`, `full_content` and `fetch_policy` to `/v1/extract` returns a 422. On `/v1/search`, `search_queries` is required (at least one short keyword query), and `max_results`, `source_policy` and `fetch_policy` go inside `advanced_settings`; sending only `objective`, or sending those fields at the top level, returns a 422. Do not substitute `/v1` for the documented FindAll or Ingest endpoint paths.

If you are evaluating Parallel Search or comparing it with other search APIs, read [How to Eval Parallel Search](https://docs.parallel.ai/search/evaluating-search.md) before you build the harness, especially its [Common pitfalls](https://docs.parallel.ai/search/evaluating-search.md#common-pitfalls) section. The most common mistake is sending the raw question as both `objective` and the only entry in `search_queries`. Write a goal-style `objective` and 1-3 short keyword queries instead.

The Places API offers two modes. Use `fast` for the lowest latency and cost, and `advanced`
for more complete results. If `mode` isn't set, requests default to `advanced`.

## Available modes

| Mode | What it does | Cost | Best for |
| - | - | - | - |
| `fast` | Fast and low cost. Typically under 1 s. | \$1 per 1,000 requests | Interactive and high-volume workloads |
| `advanced` (default) | More complete results. Typically 3 to 5 s. | \$5 per 1,000 requests | Workloads where finding every matching place matters more than latency |

Both modes return up to 20 places per request.

## Example

Switching modes is a single parameter change. The rest of your request stays the same:

```json theme={"system"}
{
  "mode": "fast",
  "query": "museums",
  "location": "Cambridge, UK"
}
```
