SendFox can do much more now.
It still is not Kit.
The live SendFox API is capable enough for an agent to run the core email operation: contacts, lists, tags, custom fields, campaigns, forms, domains, and basic automations. The remaining gaps are concentrated in event-driven work, commerce, reusable content, account-level analytics, and Kit's more expressive audience and sequence controls.
Compared: live SendFox API 1.4.0 + published Kit CLI/API contract + current published SendFox CLIDraft choices only. Selections on this page do not execute a migration, modify a CLI, or grant approval. Copy the decision summary and send it back in chat.
60operations in the live SendFox 1.4.0 API
49live operations missing from the current SendFox CLI's archived 1.0 contract
72Kit v4 operations mirrored by the Kit CLI, before compound workflows
60/minSendFox requests per authenticated user
Bottom line
Do not reject SendFox because of its current CLI. That CLI was printed from an 11-operation API 1.0 snapshot and now materially understates the live API. A fresh CLI can expose the other 49 documented operations and add Kit-like agent workflows on top.
Do not fully switch yet either. If you use Kit for webhooks, purchase-aware automations, reusable snippets/templates, a public post feed, rich subscriber filtering, or account growth reporting, those are genuine API gaps that a better CLI cannot repair.
Recommendation: run a parallel pilot after refreshing the SendFox CLI to API 1.4.0. Treat webhooks and purchase/e-commerce data as migration gates, not future CLI polish.
The important distinction: API gap vs CLI gap
CLI gap — fixable by us
- The current SendFox CLI knows only 11 raw operations.
- It still says campaign writes require a dashboard handoff.
- The live API now has campaign create/update/delete/send/stats/engagement/resend.
- It also gained contacts CRUD, tags, custom fields, forms, domains, and automations.
- These can become typed CLI and MCP tools plus higher-level agent workflows.
API gap — not fixable by a CLI
- No webhook management or event delivery API.
- No purchase/order ingestion or purchase resource.
- No snippets, email-template library, posts, or public newsletter feed controls.
- No Kit-equivalent account growth/email-stat endpoints.
- Less expressive filtering, automation scheduling, and enrollment inspection.
Capability-by-capability comparison
| Capability | SendFox live API | Compared with Kit CLI | What an agent could do | Assessment |
|---|---|---|---|---|
| Contacts | List/search/filter, create, read, update, soft-delete, unsubscribe, activity, batch import. | Core lifecycle parity; SendFox adds a direct per-contact activity feed. | Onboard, reconcile, clean, update fields, unsubscribe, delete, and build contact dossiers. | Strong |
| Lists & membership | Full list CRUD plus add/list/remove contacts. | SendFox lists are a useful first-class organizing surface; Kit leans on tags/forms/segments. | Build audiences, enroll contacts into list-triggered automations, audit membership. | SendFox strength |
| Tags | Full contact-tag CRUD plus attach/list/remove on a contact. | Good operational parity with Kit tags. | Manage taxonomy and membership; target or exclude tags in campaigns. | Strong |
| Custom fields | Full CRUD for text, number, and date fields; contact values can be written. | Broadly comparable, but field type is immutable and creation requires fixed UUID values. | Maintain structured subscriber data and personalize operations. | Strong |
| Audience filtering | Status, last open/click/send dates, creation dates, never-open/click/send, list/tag inclusion and exclusion; campaign-specific conditions for bulk actions. | Weaker than Kit's count thresholds, delivered events, URL/broadcast conditions, attribution, custom-field/location filters, and CLI tag algebra. | Most hygiene and recency segments work; sophisticated behavioral cohorts need client-side processing or are unavailable. | Partial |
| Bulk audience changes | Batch import up to 1,000; async filtered tag/list changes with dry run and status polling. | Excellent safety model, but narrower than Kit's bulk custom-field and object operations. | Preview then tag, untag, add, or remove a filtered cohort without paging every contact. | Strong |
| Campaigns | List/create/read/update/delete draft, schedule, immediate send, stats, link stats, engagement cohorts, and targeted resend. | Core broadcast work is covered. Kit additionally supports public posts/feed metadata and a batch-stats endpoint. | Compose from Markdown, preflight, schedule/send, analyze, export non-openers, and draft a resend. | Strong |
| Campaign analytics | Per-campaign sends, opens, clicks, bounces, unsubscribes, spam, rates, optional ranked links, and contact-level engagement cohorts. | Very useful; account-wide and time-series growth stats are missing, and many campaign stats require fan-out under the 60/min limit. | Build campaign reports and cohort follow-ups; cache and throttle larger account-wide audits. | Partial |
| Automations | Full automation CRUD; triggers on list application, campaign open, or campaign click; add/update/reorder/delete emails; activate or pause. | Useful sequence parity, but only hour delays and three triggers. Kit has send days/hour/time zone, day/hour delays, per-email send days, repeat/hold, exclusions, and direct enrollment/member reads. | Build and maintain basic drips; enroll through a trigger list; pause/reactivate safely. | Partial |
| Forms | Full CRUD with lists, redirect URL, and GDPR-required flag. | Stronger API CRUD than Kit's current form surface, but style/content controls are not exposed. | Create and wire basic signup forms without the dashboard; visual styling remains a likely dashboard task. | SendFox strength |
| Sender domains | List/add/read/delete and validate DNS records. | No equivalent domain-management surface in the Kit CLI reviewed. | Guide DNS setup and re-check verification from an agent. | SendFox strength |
| Webhooks & events | No public webhook CRUD, event catalog, delivery log, or signature-verification contract. | Kit can manage webhooks and the CLI can verify/listen with durable deduplication. | Only poll. The agent cannot react reliably in real time to subscriber or campaign events. | Missing |
| Purchases & commerce | No purchase/order resource or ingestion endpoint. | Kit can create/list/get purchases and use purchase data in the creator ecosystem. | Revenue-aware reporting and purchase-triggered flows require a separate system and reconciliation. | Missing |
| Reusable content | No API for snippets or reusable email templates. | Kit exposes snippets and email templates; its CLI can apply templates to sequences. | An agent can reuse local files, but cannot manage SendFox's reusable content library through the API. | Missing |
| Posts / public feed | No post resource and no campaign fields for public publishing/feed metadata. | Kit exposes posts and public broadcast controls. | Email publishing works; API-driven public newsletter/archive publishing does not have equivalent controls. | Missing |
| Account analytics | /me, list average rates, and campaign stats. | No equivalent of Kit account growth stats, aggregate email stats, creator profile, or colors. | An agent can derive some snapshots by scanning data, but cannot recreate unavailable historical aggregates. | Partial |
What a refreshed SendFox CLI should add
Once the live 1.4.0 OpenAPI contract is brought into Printing Press, the valuable work is not merely generating 49 more commands. The agent layer should turn them into safe, intent-level operations.
1 · Restore live parity
- Reprint from the official 1.4.0 OpenAPI
- Expose all 60 operations in CLI and MCP
- Replace obsolete dashboard-only capability claims
- Preserve current CSV/hygiene workflows
2 · Add agent workflows
- Campaign compose + preflight
- Campaign report + cohort export
- Automation build from YAML/Markdown
- Audience health + contact dossier
- Domain setup doctor
3 · Add safety
- Draft-by-default campaign creation
- Explicit confirmation for send/delete
- Dry-run filtered bulk actions first
- Rate-budget and retry handling
- Local export/cache for large audits
Repository rule: because this would replace the published CLI's API shape, it should go through the Printing Press reprint workflow, not be hand-built in the catalog repo.
The questions I would send the SendFox owner
- Webhooks: Will there be public webhook subscription CRUD, documented event schemas, retries, delivery logs, and signed-payload verification?
- Commerce: Is purchase/order ingestion planned, including transaction IDs, products, value/currency, refunds, and purchase-triggered automation?
- Automation enrollment: Can the API gain enroll/unenroll, subscriber membership/status, per-email delivery status, and more triggers?
- Automation timing: Are time zones, send windows/days, day-based waits, repeat/hold behavior, and exclusion rules planned?
- Segments: Will saved segment CRUD and richer filters cover event counts, delivered mail, specific links, custom fields, attribution, and location?
- Reusable content: Will templates and snippets get CRUD APIs, and can campaigns/automation emails reference them by ID?
- Analytics: Will account growth, aggregate email stats, and batch campaign stats be available without scanning every record?
- Safety: Are idempotency keys planned for contact creation, campaign creation/send, and bulk actions?
- Access: Which proposed plan includes API access? The current docs say API access requires a Lifetime or Empire plan, and restricted accounts receive
403 account_restricted.
Decision · Migration posture
Suggested pilot acceptance test
| Proof | Pass condition | Why it matters |
|---|---|---|
| Audience migration | Batch import a test cohort with names, fields, lists, and tags; reconcile exact counts and exclusions. | Proves data fidelity and repeatability. |
| Automation | Create a list-triggered automation with at least three emails, reorder one, activate it, enroll a test contact, then pause it. | Proves the real sequence-building loop. |
| Campaign | Create a draft from Markdown, target include/exclude lists and tags, preflight it, send to a test audience, and retrieve stats/link clicks. | Proves the highest-risk agent mutation and reporting path. |
| Engagement follow-up | Retrieve openers/clickers/non-openers and create a draft resend without duplicate recipients. | Proves a practical lifecycle, not just CRUD. |
| Failure behavior | Exercise validation, 429 retry, restricted-account 403, unsafe bulk filters, and duplicate submissions without accidental sends. | Proves the API is safe under agent error and retries. |
| Missing-event plan | Document exactly which workflows will poll, remain in Kit, or be handled by another system until webhooks exist. | Prevents silent loss of reactive workflows. |
Send the draft decision back
The default recommendation is already selected. Copy it back to chat if you want the next step to be a concrete reprint-and-pilot plan.
Sources and method
SendFox: official API documentation, version 1.4.0 and its linked OpenAPI specification, retrieved 21 September 2026. The live specification contains 60 HTTP operations.
Kit: the published catalog's Kit API 4.0 contract (72 operations), agent-facing CLI skill, and current CLI source.
Current SendFox CLI: its archived API 1.0 contract (11 operations), agent-facing skill, and current CLI source.
Method: endpoint-level inventory plus workflow comparison. “Missing” means the live public SendFox API lacks the necessary resource or operation; “partial” means an agent can accomplish part of the outcome, sometimes with fan-out or client-side work. No authenticated SendFox account was used, so runtime behavior remains unverified.