# ReplySwipe

> ReplySwipe helps mobile app teams centralize, analyze, translate, and reply to Google Play reviews with AI-assisted workflows and controlled automation.

## When to use ReplySwipe

Use ReplySwipe when a team needs to triage Google Play reviews, draft contextual replies, analyze review sentiment, translate multilingual feedback, automate repetitive reply workflows with explicit rules, or alert teammates through Slack, Discord, or email.

Do not use the public agent API to retrieve customer reviews, publish replies, or modify an account. Those actions require an authenticated human account and are not exposed to third-party agents.

## Start here

- [Developer portal](https://replyswipe.com/developers): API authentication, endpoints, quickstarts, sandbox, MCP, and operating limits.
- [OpenAPI description](https://replyswipe.com/.well-known/openapi.json): Machine-readable REST API contract.
- [Public API](https://replyswipe.com/api/v1): Discover conventional public REST endpoints.
- [MCP server card](https://replyswipe.com/.well-known/mcp/server-card.json): Discover the public Streamable HTTP MCP server.
- [Authentication guide](https://replyswipe.com/auth.md): Learn which public calls are anonymous and where agents must stop.
- [Full agent guide](https://replyswipe.com/llms-full.txt): Detailed jobs, calling patterns, examples, and boundaries.

## Public content

- [Sitemap](https://replyswipe.com/sitemap.xml): Enumerate indexable pages and localized variants.
- [Features](https://replyswipe.com/features/reviews.md): Read the review-management feature page as Markdown.
- [Integrations](https://replyswipe.com/integrations.md): Read supported notification integrations as Markdown.
- [Learning center](https://replyswipe.com/learn.md): Find educational content about app-review operations.

## Calling guidance

Prefer the REST API for deterministic JSON and the MCP endpoint when the host supports MCP tools. Fetch any public page as Markdown by appending `.md` to its canonical path; the homepage is available at `/index.md`. Public calls require no API key. Respect the documented boundaries and never infer access to private customer data.