ReplySwipe

ReplySwipe for agents

A clear entry point for agents and developers.

Discover what ReplySwipe solves, inspect capabilities as JSON, and test a recommended workflow without creating an account or exposing customer data.

Open OpenAPITry the sandbox

REST quickstart

Fetch public capabilities and integrations with one request. The response is JSON and supports CORS.

GET /api/v1/capabilities
curl --fail --silent --show-error \
  https://replyswipe.com/api/v1/capabilities

Endpoints

Public routes support discovery and evaluation. Review operations remain inside the authenticated application.

GET/api/v1

API index and canonical documentation links

GET/api/v1/capabilities

Product capabilities, integrations, and public-data boundaries

POST/api/v1/sandbox/recommendation

Deterministic workflow recommendation sandbox

POST/api/mcp

MCP Streamable HTTP endpoint

Authentication and API keys

These public endpoints need no key. ReplySwipe does not yet issue API keys or OAuth credentials to third-party agents. Do not send cookies or tokens from a human session.

Read auth.md

Security boundaries

  • The public API cannot read reviews, users, billing, or customer settings.
  • The sandbox calls no external model and stores no submitted content.
  • Account actions require a human session inside ReplySwipe.

Recommendation sandbox

Describe a team and receive a suggested setup. It is deterministic, stores nothing, and changes no account.

Options
Alert channels

The result opens as JSON in a new tab.

Model Context Protocol

MCP over Streamable HTTP

Compatible hosts can discover three public read-only tools for inspecting capabilities, recommending a workflow, and listing agent resources.

{
  "mcpServers": {
    "replyswipe": {
      "url": "https://replyswipe.com/api/mcp"
    }
  }
}
View MCP server card