# Яндекс Yandex | Парсер Поиска Яндекса

A seo tools tool your agent can run on one prepaid apifare key. Page: https://apifare.com/tools/johnvc/yandex-scrape-yandex-search-results-at-scale---per-result

## What you need

An apifare key with credits (sign up: POST https://apifare.com/v1/signup {"email": "..."}; new accounts get 500 free credits). No other account or key.

## Inputs

- `text` (string, required): Search Query
- `include_organic_results` (boolean): Organic results
- `include_ads` (boolean): Ads
- `include_knowledge_graph` (boolean): Knowledge graph
- `include_inline_images` (boolean): Inline images
- `include_inline_videos` (boolean): Inline videos

The most relevant fields; the search result's input_schema lists all of them.

## Price

5 credits reserved per run, settled to the run's true cost, never more than 20 credits (1 credit = $0.01). Failed runs are refunded. Exact numbers: https://apifare.com/capabilities

## Run it

1. Find it: MCP search_apis, or GET https://apifare.com/v1/search?q=%D0%AF%D0%BD%D0%B4%D0%B5%D0%BA%D1%81%20Yandex%20%7C%20%D0%9F%D0%B0%D1%80%D1%81%D0%B5%D1%80%20%D0%9F%D0%BE%D0%B8%D1%81%D0%BA%D0%B0%20%D0%AF%D0%BD%D0%B4%D0%B5%D0%BA%D1%81%D0%B0 with Authorization: Bearer <token>. Take the result named "Яндекс Yandex | Парсер Поиска Яндекса"; it carries a proxy_route.
2. Run it: MCP proxy_call with that proxy_route and the input JSON (apifare-mcp over stdio), or POST the proxy_route over HTTP with the input JSON as the body and the same Authorization header.
3. On HTTP 402, relay the body's human_readable field to your human verbatim, wait, then retry the same call. Every other error and its fix: https://apifare.com/errors.md