About & roadmap
Why this exists, what's real, and where it's going — the product concept behind agents.reply.io, the Sales Engagement API for AI Agents.
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.
Roadmap
| Capability | Phase | Status |
|---|---|---|
| Unified v3 REST API | Live now | Live |
| Official MCP server | Live now | Live |
| Prospect Search (Live Data) endpoints | Live now | Live |
| Contact Enrichment endpoints | Rolling out — late August 2026 | Coming soon |
| AI SDR autopilot endpoints | Live now | Live |
| Reply CLI | Live now | Live |
| Packaged agent skills | Live now | Live |
| Agent self-registration & trial provisioning | Next | Coming soon |
| Autonomous credit purchasing | Later | Coming soon |
| Per-scope agent budgets & usage API | Exploring | Concept |
Unified v3 REST API
The full platform API at api.reply.io/v3 — scoped Bearer-token auth, problem+json errors, OpenAPI + Postman published at docs.reply.io.
Official MCP server
Live at mcp.reply.io — the next-gen server, with tools spanning sequences, contacts, inbox, tasks, and the full Jason AI SDR autopilot. Streamable HTTP, Authorization: Bearer auth, tool discovery for Claude, Cursor, and any MCP client.
Prospect Search (Live Data) endpoints
B2B database search over 1B+ contacts via API — shipped, and callable today as of 2026-07-30. Reply marks the endpoints beta, so shapes may still change.
Contact Enrichment endpoints
Waterfall enrichment, email/phone finding, and AI custom fields — still marked Coming soon in Reply’s reference as of 2026-07-30 (targeted late August 2026).
AI SDR autopilot endpoints
Programmatic Jason autopilot — AI SDR sequences, autopilot control, the approval queue, and the strategist are all callable today, in beta. Per-contact AI insights and AI web search are the remaining pieces, targeted late August 2026.
Reply CLI
First-party reply command over the v3 API — JSON output for agents, pipes and scripting for humans. Shipped as reply-cli 0.5.1, covering authentication, profiles, teams, reply api — an authenticated passthrough that already reaches every v3 endpoint — plus reply skills to install the agent skills into an assistant and reply install to keep the CLI current. Dedicated commands for sequences, contacts, the inbox, and reporting are still to come, shaped by the SDR operation contract rather than by the endpoint list.
Packaged agent skills
reply-skills — 18 plain-markdown skills in the open Agent Skills format, shipped as three installable packs: vendor-neutral SDR expertise, the Reply.io execution adapter, and a durable multi-session runtime. Installed in one command with reply skills install, with confirmation guardrails on anything that reaches a real person. Enrichment-dependent guidance waits on its API.
Agent self-registration & trial provisioning
An agent creates its own account, workspace, and scoped API key, and receives trial credits — the flow simulated today on the Get started page.
Autonomous credit purchasing
Agent-initiated checkout inside human-approved spend guardrails. Today the agent hands its human an upgrade link; this closes the loop.
Per-scope agent budgets & usage API
Illustrative direction: budgets attached to API-key scopes (e.g. “this agent may spend 500 data credits/month”), plus a usage API so agents can forecast their own spend. No specification yet.