> 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/web3-intelligence/web3-intelligence.md). # Web3 Intelligence Overview Web3 Intelligence is TheContentForge's on-chain awareness layer. For teams whose audience or work touches Web3, it brings wallet activity, token context, DeFi positions, and execution conditions into the same workspace as content generation, brand voice, publishing, and analytics so on-chain signals can flow directly into posts, threads, briefs, reports, and stream prep. Open it from **Intelligence > On-Chain Intelligence**. ### Web3 Intelligence vs Investor Intel Web3 Intelligence is the content-side On-Chain hub built into this workspace. It is focused (Solana wallets, Kamino DeFi context, swap execution checks) and its job is to feed [Content Forge](/thecontentforge-docs/feature-guides/content-studio.md) so on-chain signals shape your posts. [Investor Intel](/thecontentforge-docs/investor-intel/investor-intel.md) is a separate paid crypto-research product covering more chains and deeper market analysis. If you want research as the destination, use Investor Intel; if you want on-chain signals flowing into content, stay here. It 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. ### The four modules * [**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, and liquidity tracking, Market Pulse, and AI reports * [**DeFi Intelligence**](/thecontentforge-docs/web3-intelligence/defi-intelligence.md) - read-only Kamino DeFi context across Earn and Liquidity 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 ### How it fits the rest of the platform Web3 Intelligence is an input layer, not a destination. Events, reports, and angles from any of the four modules can be sent into [Content Forge](/thecontentforge-docs/feature-guides/content-studio.md) as intelligence notes that prefill drafts, the same flow that the rest of the signal feeds use. The output is content, scheduled and published from the same workspace. ### Safety Every Web3 Intelligence module is read-only. Linking a personal wallet on the [My Account](/thecontentforge-docs/feature-guides/my-account.md) page is for verified ownership flows only; it does not gate access to Intelligence pages and it never authorises a transaction. Data providers receive no private keys and trigger nothing on your behalf. See the **Web3 safety** section of the [FAQ](/thecontentforge-docs/reference/faq.md) for the full disclosure. --- # 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/web3-intelligence/web3-intelligence.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.