# Guides

> Task-oriented paths across implemented capabilities.

Source page: https://docs.replynodes.com/docs/guides

# Guides

Choose a task page: [Web context](https://docs.replynodes.com/docs/guides/web), [Search](https://docs.replynodes.com/docs/guides/search), [YouTube](https://docs.replynodes.com/docs/guides/youtube), [Reddit](https://docs.replynodes.com/docs/guides/reddit), [App Store](https://docs.replynodes.com/docs/guides/app-store), [Google Play](https://docs.replynodes.com/docs/guides/google-play), [Brand intelligence](https://docs.replynodes.com/docs/guides/brand-intelligence), or [Brand Kit](https://docs.replynodes.com/docs/guides/brand-kit). Each page names only operations present in the runtime capability OpenAPI contract, except Brand Kit, which documents its separate local CLI workflow and aggregate boundary.

The keyless public loop is **Logo → Brand → Markdown**: successful Logo and Brand responses advertise the next capability in response metadata, while the three dedicated roots remain concise agent-readable guides.

## Use a guide with the API contract

Guides are a starting point for a specific public-data task, not a replacement for the contract. Start with [Quickstart](https://docs.replynodes.com/docs/quickstart) to set `REPLYNODES_API_KEY` in a secret store and make a request to `https://api.replynodes.com`. Every provider operation is represented by an exact method, path, and parameter list in the [API Reference](https://docs.replynodes.com/reference), which is generated from the runtime capability OpenAPI contract.

The task pages group the available reads by source. Web context covers scrape, map, crawl, and page-context work. Search covers `GET /v1/web/search`. The YouTube and Reddit pages list their public-data `GET` operations, while the App Store and Google Play pages cover application lookup, search, reviews, and related public metadata. Brand intelligence documents the operations for domains and brand data. PDF explains the separate PDF-to-Markdown capability.

Choose the page that matches the source and then copy only the documented parameters. Successful HTTP API responses use the `{ data, meta }` envelope; preserve `meta.request_id` for correlation. For interactive MCP clients, use the [MCP guide](https://docs.replynodes.com/docs/mcp). It documents the remote server and its authentication choices. For REST requests and generated SDKs, return to the API Reference before relying on a path or schema.

These pages are task-oriented entry points, not a replacement for the machine-readable contract. Follow a link to understand the intended workflow, then open the API Reference to select an operation and validate every parameter before making a call. An agent can begin with a broad discovery operation, retain the identifiers and locale returned by that response, and continue with a bounded detail or enrichment request. This sequence keeps the request plan explicit and makes it easier to explain why a result was selected. It also avoids guessing paths from provider names or copying undocumented examples into production automation.

The platform exposes public read operations only. A guide may describe data from an external service, but it does not grant permission to publish, modify, authenticate to a third-party account, or bypass an upstream access boundary. Use the deployed capability and OpenAPI documents as the authority for current availability. Preserve `request_id` values, handle errors according to their status and `Retry-After` guidance, and keep retries finite. If a guide and a live contract disagree, trust the live contract and report the discrepancy rather than inventing a route.