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

> ## Agent Instructions
> If the user asks to make Context.dev their default search and scrape provider, follow https://docs.context.dev/default-search-scrape.md. For other setup requests, follow https://docs.context.dev/agent-quickstart.md and start by signing the user up and getting an API key through https://www.context.dev/auth.md. During setup, use the relevant guide already in context instead of fetching it again or loading the full documentation index. Application code reads CONTEXT_DEV_API_KEY.

# Pre-built parsers

> Choose a parser for Maps, app stores, contact details, or links without writing CSS rules.

Use `POST /web/scrape` with `formats.parse: true`, `parseParams.type: "prebuilt"`, and one parser name per request. Don't send custom `rules`. See the [Quickstart](/quickstart) for authentication and SDK setup.

| Parser | Input | Data in `parsed.data` |
| - | - | - |
| [Google Maps](/scrape/prebuilt-parsers/google-maps), `google-maps` | Google Maps place, search, or data URL | `results` with business records |
| [Google Play](/scrape/prebuilt-parsers/google-play), `google-play` | Google Play app details URL | App details, ratings, downloads, and data safety |
| [Google Play reviews](/scrape/prebuilt-parsers/google-play-reviews), `google-play-reviews` | Google Play app details URL | `app_id` and up to 200 recent `reviews` |
| [App Store](/scrape/prebuilt-parsers/app-store), `app-store` | App Store app URL | App details, ratings, pricing, and screenshots |
| [App Store reviews](/scrape/prebuilt-parsers/app-store-reviews), `app-store-reviews` | App Store app URL | `app_id` and up to 500 recent `reviews` |
| [Emails](/scrape/prebuilt-parsers/emails), `emails` | Any supported page URL | `emails` with normalized contact addresses |
| [Phone numbers](/scrape/prebuilt-parsers/phone-numbers), `phone-numbers` | Any supported page URL | `phone_numbers` with E.164 numbers |
| [Links](/scrape/prebuilt-parsers/links), `links` | Any supported page URL | `links` with absolute URLs and text labels |

## Read the output

The `parsed` output identifies the parser in `parsed.type`. Check `parsed.success` before reading `parsed.data`; each parser’s page documents its data fields. A failed parse has `data: null`, with an `error_code` and `message`, and can coexist with successful outputs in the same request. See [timeouts and errors](/scrape/timeouts-and-errors).

## Page content and browser profiles

Emails, phone numbers, and links use page HTML after [content filtering](/scrape/content-filtering). They support [browser actions](/scrape/browser-actions) and [browser profiles](/scrape/browser-profiles). They extract from one page rather than crawling a site.

Google Maps and app store parsers fetch source data separately, using a US exit. Content filters and browser actions do not change those parser results, and browser profiles are unsupported. Google Play’s `hl` and `gl` query parameters and the App Store’s country path still select the source locale or storefront.

[Caching](/scrape/freshness-and-caching), [timeouts](/scrape/timeouts-and-errors), and [zero data retention](/optimization/zero-data-retention) apply to all parsers. Use the [Custom parser](/scrape/parse-fields) for CSS rules or [JSON extraction](/scrape/json) for a schema you define.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.