Jam (SpreadJam)
Growth-channel agent platform that turns AI-search visibility, SEO audits, lead discovery, and content distribution into workflow nodes and product actions.
Jam is useful to track because it productizes the Writing and Content Skills loop as an agent workflow: audit a site or repo, identify AI-search/content gaps, make concrete edits, then connect that work to growth channels such as warm leads, outreach inboxes, lead enrichment, and deliverability. The March 2026 demo bookmarked by Kevin shows a Jam flow reading a GitHub repo, running a GEO/SEO audit, surfacing content gaps and quick wins, then presenting PR-style code/content changes. Source: X/@jia_seed and local video review, 2026-07-02
Product shape
The public site positions Jam as "agents for every growth channel." The durable surface is not a generic dashboard; it is a set of channel-specific agents around AI-search visibility, lead/contact discovery, outbound inboxes, lead enrichment, mailbox warm-up, and custom automations. Source: SpreadJam site, 2026-07-02
Use Jam as a tool candidate when the task is "turn SEO/GEO findings into repeated growth actions." Keep Kevin's installed Security and Review Skills and seo-audit skills as the default execution route for one-off audits and site changes; Jam matters when those steps need a productized workflow layer.
jam-nodes
The open-source layer is wespreadjam/jam-nodes, a TypeScript node framework with Zod-validated nodes and a browser playground. The docs list built-in logic, transform, integration, and action nodes, including HTTP requests, Reddit/Twitter/LinkedIn monitoring, contact search, email drafting, social AI analysis, Sora video, SEO keyword research, SEO audit, and social keyword generation. Source: Jam docs, 2026-07-02
Current source snapshot: @jam-nodes/playground@0.1.2 on npm, wespreadjam/jam-nodes HEAD e8e1abc1536ac8d41e6ab31c05347b55ef10fb41, MIT license, 197 stars, 45 forks, no public tags returned by git ls-remote as of 2026-07-02. The docs repo is wespreadjam/jam-docs, MIT, HEAD maintained separately. Source: npm registry and GitHub API, 2026-07-02
Routing notes
- For auditing a page or site now, load Security and Review Skills or
seo-audit. - For building reusable growth-channel workflows, evaluate Jam/jam-nodes as a workflow-node substrate.
- For agent access to docs or node metadata, follow Jam's MCP/documentation route before scraping the site manually. Source: Jam docs
/llms.txt, 2026-07-02
Timeline
- 2026-07-02 | Page created from Kevin's bookmarked @jia_seed demo. Local video review identified the product as Jam/SpreadJam and confirmed a repo-driven GEO/SEO audit workflow with PR-style changes; source review added current site/docs/GitHub/npm snapshots. Source: X/@jia_seed, 2026-03-03