Data Sources — Content AI (Chatbase, Peec.ai, AlsoAsked)
API-key-based connections to AI chatbot data (Chatbase), AI-chat answer monitoring (Peec.ai), and PAA intelligence (AlsoAsked).
What is it?
Three integrations that enrich content planning with non-SEO signals.
- Chatbase — your deployed chatbot's conversation logs. Tells you what users are actually asking.
- Peec.ai — monitors how AI chatbots (ChatGPT, Perplexity, Gemini) answer queries about your brand and competitors. Surfaces content gaps where your brand is missing in AI-driven answers.
- AlsoAsked — pulls Google's "People Also Ask" tree for any keyword.
All three use an API key stored in Firestore as a secret. Chatbase also requires a chatbot ID.
When should I use it?
- Chatbase: any client running a bot — hugely valuable for understanding real user questions.
- Peec.ai: brands that care about AI-driven discovery (most do, increasingly). Premium signal.
- AlsoAsked: always connect — low-cost, essential for PAA question mining.
How to use it
Chatbase
- Click Connect Account on the Chatbase card.
- Enter your API key and Chatbot ID. Both are available in the Chatbase dashboard (Settings → API).
- Save. The card now shows conversation count.
- Don't have an account? Click the "Sign up for Chatbase" link under Connect Account (supports our referral program).
Peec.ai
- Click Connect Account on the Peec.ai card.
- Enter the API key from your Peec.ai dashboard.
- Save.
AlsoAsked
- Click Connect Account on AlsoAsked.
- Enter your API key.
- Save.
Tips and best practices
- Chatbase conversations are a goldmine — explore them via Chatbase Explorer in the Opportunity Finder.
- Peec.ai data surfaces in the Strategic Keyword Clusters widget on the Dashboard. Combine with GSC for cross-channel validation.
- AlsoAsked quotas vary by plan — check your usage before bulk operations.
Gotchas and limits
- API keys never appear in UI logs or the network tab — they're sent server-side. Safe to use.
- A bad API key fails silently on some endpoints. If a feature stays empty, verify the key first.
- Chatbase IDs look like UUIDs — double-check you copied the chatbot ID, not the team ID.
- Peec.ai limits per plan — heavy PDF dumps or large keyword lists may hit quota.