> For the complete documentation index, see [llms.txt](https://thecontentforge.gitbook.io/thecontentforge-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://thecontentforge.gitbook.io/thecontentforge-docs/getting-started/what-is-thecontentforge.md). # What is TheContentForge? TheContentForge is an operations platform spanning a few distinct products: * **Content Forge** - the core content workspace. One place to generate content, transcribe and repurpose video, clip social-ready moments, manage brand voice, publish or schedule posts, track performance signals, and run experiments for X, Instagram, and Facebook. Publishing and account connections are live for X today, with Instagram and Facebook coming soon. * **Investor Intel** - a separate retail crypto research product, with its own home at `/intel`. It is a standalone research surface, not part of the content workspace. * **Students** - a dedicated lane for student creators, with its own onboarding and guardrails. Most teams live in Content Forge; the sections below describe it unless noted otherwise. ### What it replaces Most teams juggle a content doc, a video clipping workflow, a scheduling tool, a spreadsheet of analytics, and a group chat for trend spotting. TheContentForge collapses that stack: * **Content Forge** replaces your drafting doc and prompt notes * **Video Forge** replaces the manual long-form-to-social repurposing and clipping workflow * **Brand Voice** replaces the "make sure it sounds like us" review loop * **Publishing** and **Calendar** replace the handoff between drafting and scheduling * **Asset Library** keeps reusable media and source documents in one org-scoped place * **Patterns** and **Competitor Intelligence** replace the weekly analytics spreadsheet * **ForgeSays**, **Algorithm Watch**, and **Current Events** replace the "did you see this?" group chat * **Experiments** replaces the gut-feel "let's just try it and see" approach ### Who it's for Content leads, social managers, and growth teams who ship on a schedule and need their output to improve over time; not just get published. For Web3 Project orgs, TheContentForge also supports a more structured project-native workflow: project profile, team, roadmap, FAQs and objections, and approved supporting context that can be used directly in [Content Forge](/thecontentforge-docs/feature-guides/content-studio.md). See [Web3 Projects](/thecontentforge-docs/feature-guides/web3-project.md). ### Multi-tenant by design Every org has its own isolated workspace. Data, users, assets, social connections, and settings never cross organization boundaries. ### On-chain Intelligence For teams whose audience or work touches Web3, Content Forge layers in on-chain context alongside the rest of the workspace. This content-side On-Chain Intelligence is built to inform what you post; it is distinct from Investor Intel, the standalone crypto research product at `/intel`. * [**Wallet Intelligence**](/thecontentforge-docs/web3-intelligence/wallet-intelligence.md) - Solana wallet watchlist with a live on-chain feed, alert rules, and AI analysis * [**Token Intelligence**](/thecontentforge-docs/web3-intelligence/token-intelligence.md) - token watchlist with price, volume, liquidity tracking, Market Pulse, and AI reports * [**DeFi Intelligence**](/thecontentforge-docs/web3-intelligence/defi-intelligence.md) - read-only DeFi context across yield vaults, lending markets, and wallet positions * [**Execution Intelligence**](/thecontentforge-docs/web3-intelligence/execution-intelligence.md) - pre-publish swap-quality checks and prediction-market discovery for content angles Web3 Intelligence is read-only by design. TheContentForge does not custody funds, hold private keys, execute trades, place bets, or provide financial advice. The Intelligence pages exist to inform content decisions - what to post, when, with what framing - not to move assets. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://thecontentforge.gitbook.io/thecontentforge-docs/getting-started/what-is-thecontentforge.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.