Kit

**Judgement** A strong, well-scoped integration for the Kit (formerly ConvertKit) v4 API via the Maton gateway. It is suitable as a primary tool for managing email-marketing data (subscribers, tags, forms, sequences, broadcasts, custom fields, and webhooks) when you already use Kit or are standardizing on Maton-managed OAuth. **Key Strengths** - Broad coverage of core Kit resources (subscribers, tags, forms, sequences, broadcasts, segments, custom fields, purchases, email templates, webhooks). - Managed OAuth and connection management (create/list/delete connections, select specific connections) offload auth complexity from your app/agent. - Clear HTTP contract with consistent base URL, explicit query parameters, and cursor-based pagination handling. - Good, language-agnostic examples (Python, JS) and detailed error semantics to guide robust integrations. **Risks / Limitations** - Hard dependency on external infrastructure: both Maton (gateway + control plane) and Kit must be available and correctly configured. - Requires secure provisioning and storage of `MATON_API_KEY`; misuse or leakage can expose or mutate sensitive subscriber data. - The API allows destructive operations (deleting tags/custom fields, altering subscribers, webhook targets), so poorly designed agent prompts or logic could damage lists, segmentation, or automations. - Broadcast-related operations in the provided spec are read-focused (list) rather than full lifecycle (create/send), so advanced campaign orchestration may still require direct Kit API knowledge. **Recommended Scenarios** - Agents or backend services that need to keep a Kit subscriber base in sync with another system (e.g., product users → subscribers, course enrollments → tags/sequences). - Automation flows that regularly add subscribers to forms or sequences, maintain tags, and update custom fields based on business events. - Operational dashboards or admin tooling that need to inspect forms, sequences, broadcasts, segments, purchases, or email templates from a central interface. - Workloads where you want to avoid implementing OAuth with Kit directly and prefer a managed connection model via Maton. Use with extra care in contexts where accidental mass edits or deletions could significantly impact an email list; consider implementing guardrails (confirmation steps, dry-run modes, or scope-limited prompts) around destructive actions.