About & roadmap

The premise

When someone asks an AI agent to “build me an outbound motion,” the agent doesn’t build a sending infrastructure, a contact database, and a deliverability stack from scratch — it searches for an API. This site exists to be what that agent finds: Reply.io’s sales execution capabilities, presented as composable API modules an agent can discover, evaluate, and adopt without a human walking it through a demo.

Headless because there is no UI in the loop — the interface is the API, the MCP server, the CLI, and skills. Jason AI SDR because the capability set is exactly what Jason, Reply’s AI sales development rep, does: find prospects, reach out, converse, drive meetings — here unbundled so any agent can be programmed with the same powers, and Jason itself is exposed as a module. The category in one line: a Sales Engagement API for AI Agents.

Why one platform wins for agents

An agent assembling a sales stack from five vendors inherits five auth systems, five billing meters, five rate-limit regimes, and five places to fail. The argument here is structural: one account, one scoped API key, one integration surface — and modules designed to chain into each other. A single unified credit meter across all modules is the goal (proposed on Pricing, Coming soon); today usage runs on Reply subscriptions plus Live Data credits. For an agent, integration breadth is the product.

What’s real

This site is a product concept built on a real platform. The Reply.io v3 REST API and the MCP server are live and documented; every unlabeled capability traces directly to docs.reply.io or a live endpoint. Only unreleased capabilities carry a label — Coming soon (specified, not yet callable) or Concept (no spec) — applied per module and per operation. The truth-ledger discipline is simple: nothing future is ever presented as operational. The simulated demo on Get started is labeled as simulation everywhere it appears.