nitrosend

Nitrosend

Use this as the single public Runx surface for Nitrosend customer operations. Local account runners bind the API key only to the local runtime. The hosted review-content runner calls one bounded provider.read operation whose Cloud adapter retains credential custody. No runner accepts an API key as skill input or returns one in a receipt.

This skill is not for Nitrosend customer-support administration or team Slack work. Those are product-operator concerns owned by the Nitrosend repository.

Choose the runner

• status (default): live account, brand, sender, domain, provider, warmup, and deliverability readiness.
• billing-status: read the current account subscription and eligible paid-plan catalog together. It creates no checkout; prepaid balance and add-funds readiness remain a distinct funding block in the status evidence.
• plan-checkout: re-read current billing and plans, approve one exact plan, create the idempotent hosted checkout or confirmed in-place plan change, then read billing again. A checkout URL is pending operator work, not proof of payment or activation.
• plan-checkout-status: reconcile one returned plan-purchase ID without creating another checkout. Use it after hosted approval, timeout, or an ambiguous client response.
• configure-sender: read, approve, update, and independently read back one explicitly selected brand's exact sender defaults. It configures no content, audience, campaign, flow, or delivery.
• analytics: live account, campaign, flow, or message insights.
• review-delivery: read-only content and preflight review. Flow review requires the exact immutable revision_id; campaigns and templates do not.
• review-content: read-only spam and accessibility review for bounded inline email content. It accepts no account entity, audience, delivery, or mutation input and is safe to compose behind a payment-as-access vendor endpoint.
• plan-campaign, plan-flow, plan-transactional, and plan-import: bounded agent judgment that produces a reviewable request without provider completion.
• compose-email: read the live Nitrosend authoring contract, let one bounded agent author its exact next call, and return authoritative MCP validation. It never persists a draft or gains delivery authority.
• apply-draft: apply exact reviewed arguments for a campaign, flow, template, segment, or remote image ingest. Image ingest validates the remote bytes and returns a durable Nitro-hosted brand-library URL. It never sends or activates.
• approve-delivery: approve a reviewed campaign or an exact flow revision without delivering.
• send-campaign: send or schedule an already-approved campaign after a fresh provider review and explicit approval.
• activate-flow: publish an exact already-approved flow revision after a fresh review and explicit approval.
• send-transactional: dry-run or send one idempotent message to one recipient.
• import-contacts: dry-run or import at most 100 inline consented records.
• import-contacts-csv: validate or upload a local CSV through Nitrosend's authorized direct-upload path. File bytes and signed URLs never enter the agent packet or receipt.
• import-status: make one bounded status read for an asynchronous import.
• segment-from-prose: internal planning lane for the current supported filter catalog; unsupported filters are rejected rather than approximated.