Best interface
CLI for reporting agents —
reply api with --json makes the
reporting endpoints pipeable and cron-able. MCP for Q&A-style analysis — “compare Q3 sequences”
resolves to reply_compare_sequence_performance in one call.Steps
1
Pull the account-level overview
Both endpoints take a
filters object; dateRangePreset accepts lastWeek, lastMonth,
lastYear, or allTime.2
Drill into per-sequence stats
reply_get_sequence_stats (one sequence, custom date window) or
reply_compare_sequence_performance (up to 25 side by side — align by SequenceId, treat
missing rows as no data).3
Diagnose
Benchmark deliverability (bounces), copy (opens vs replies), and targeting (replies vs
interested). Flag stalled or degraded sequences. The
performance-analysis skill packages this diagnosis.4
Act — with confirmation
Pausing sequences or editing copy are production changes: recommend, confirm, then execute
(Manage sequences has the loop).
Availability notes
- Reports, per-sequence stats, and comparisons: available today.
- Stats endpoints can throttle earlier than CRUD endpoints — budget calls accordingly (Rate limits).
- Meetings are booked via Reply’s in-app scheduler; the API reports them (meetings ledger) but can’t book them.
Related
- Improve sequences every cycle — acting on the diagnosis
- Skill:
performance-analysis