forge-suite
Installation
SKILL.md
Forge Suite
Three products from one vendor, four REST surfaces, three separate API keys. Mailforge provisions domains and mailboxes, Warmforge warms them and reports deliverability, Salesforge sends sequences from them and handles replies.
API surface map
| Surface | Base URL | Key | Owns |
|---|---|---|---|
| Salesforge core | https://api.salesforge.ai/public/v2 |
SALESFORGE_API_KEY |
Workspaces, contacts, tags, custom vars, DNC, mailboxes, V1 email sequences, threads and replies, Primebox labels, products, webhooks |
| Salesforge multichannel | https://multichannel-api.salesforge.ai/public/multichannel |
SALESFORGE_API_KEY (same key) |
V2 sequences as a node graph (email + LinkedIn), LinkedIn accounts, sender profiles, validation runs, enrollment preflight, subsequences |
| Warmforge | https://api.warmforge.ai/public/v1 |
WARMFORGE_API_KEY |
Warmup settings and stats, mailbox health (SPF/DKIM/DMARC/MX, blacklists, Heat Score), inbox placement tests |
| Mailforge | https://api.mailforge.ai/public |
MAILFORGE_API_KEY |
Domain search and purchase, DNS, forwarding, masking, mailboxes and their SMTP/IMAP credentials, pre-warmed inventory, spam check, mailbox analytics |
Each key authenticates only its own product. Each product also keeps its own workspace records, so resolve and store a workspace ID per product; match mailboxes across products by email address.
Step 1: load the keys
Keys live in a .env file. Load only the keys the task needs.