For agents

Agent index

Overview Reviewed · not yet fact-checked

In short

How does an AI agent use Reply?

This index maps Reply for agents: a capability table answering can-Reply-do-it, core workflows and objects, behavior rules that surprise the unread, interfaces — REST API on docs.reply.io and the MCP server at mcp.reply.io — plus machine entry points: llms.txt, llms-full.txt, index.json, capabilities.json, search-index.json, sitemap.xml, and a markdown twin for every page.

Reply is a sales engagement platform: the Reply Data B2B database with live search and enrichment, deduplicated contact management, multichannel sequences (email, LinkedIn, calls, SMS, WhatsApp, tasks, Zapier and condition steps), a consolidated inbox with AI-assigned reply categories, deliverability protection with MailToaster warm-up, analytics, and an AI SDR (Jason AI) that runs the loop with drafts-for-review or automatic sends. This page is the compact index; every claim links to its page.

Can Reply do the task?

Task	Page
Find prospects by ICP	Prospect search
Manage contacts without duplicates	Contact management
Fill missing emails/phones	Data enrichment
Send automated email sequences	Email outreach
Automate LinkedIn touches	LinkedIn outreach
Coordinate channels in one flow	Multichannel outreach
Detect and answer replies	Reply management
Report performance	Campaign analytics
Protect sender reputation	Deliverability
Run the whole loop with AI	AI SDR

Sections of this site

Start · Capabilities · Workflows · How to · Behavior · Specifications · Reference

Group landings inside those sections: Core concepts (in Start) · Playbooks (in Workflows) · Troubleshooting (in How to)

Page statuses: placeholder (structural scaffolding, claims unverified) → reviewed (grounded in Reply's product documentation) → verified (checked against the live product).

Core workflows

Build an AI SDR · Find prospects from an ICP · Launch an outbound campaign · Process positive replies · Sync Reply with a CRM

Core objects

Contacts · Sequences (the product also calls them campaigns) · Email accounts · Schedules · Inbox · Jason AI: Offers, Playbooks, Knowledge bases

Behavior that will surprise you if unread

A reply to a sequence email sets Replied and Finished and stops the contact's automation, unless Continue processing steps is enabled — Reply detection · Sequence stopping
The contact identifier chosen at import (Email, Last Name, or Phone) is the dedup key — matching rows update or skip, never double — Contact deduplication
The email account's own daily limit always beats a higher sequence setting — Mailbox selection · Limits
Follow-ups send from the same email account as the first email; schedules run on UTC and do not adjust for Daylight Saving Time — When Reply sends
Out-of-office replies pause the contact rather than finishing them; automatic handling resumes sending after the number of days you set — Reply detection

Interfaces

Surface	Where	Notes
REST API	docs.reply.io	Source of truth for the API surface; 15,000 requests per month, 10 seconds between calls
MCP server	`mcp.reply.io` — guide: agents.reply.io/mcp	URL and API key from the Integrations tab in Reply; auth via `Authorization: Bearer` with scoped personal API keys, or OAuth (full access); connects from Claude, ChatGPT, n8n, Make.com, and Claude Code
CLI	npm `reply-cli` — agents.reply.io/cli	Command-line operation of the same objects
Agent skills	agents.reply.io/skills	Packaged workflows for agent runtimes
OpenAPI spec	bundled.yaml	Machine-readable API contract

Machine entry points on this site

curl https://how.reply.io/llms.txt           # curated page index
curl https://how.reply.io/llms-full.txt      # whole site, one file
curl https://how.reply.io/index.json         # site map by section, typed
curl https://how.reply.io/capabilities.json  # flat can-do/cannot-do capability matrix
curl https://how.reply.io/search-index.json  # titles + descriptions + headings
curl https://how.reply.io/sitemap.xml        # every canonical URL
# append .md to any page URL for its markdown twin

Also useful: /reference/a-z — the alphabetical index of every term and page.

Known limitations

Pages labeled Placeholder are structural scaffolding — do not cite their detailed claims yet.
Reply is not a CRM and not a transactional email service — When to use Reply.
Interface coverage differs per surface — check agents.reply.io before choosing one.

Product map · How Reply works
Terminology · Statuses