Tools & keys · Communities
GitHub setup
Issues and discussions, for developer tools only.
Optional
Updated
Free tier
Free. Without a token you get 10 searches a minute; a token raises that and adds Discussions.checked September 2026
Larvabot's cap
Nothing to cap: rate limits just hand the job to the next provider.Fallback position
#4 of 8 for conversations. See the orderWhat it does
GitHub's search API covers issues, pull requests and, with a token, Discussions.
- Finding issues and discussions where people ask for what your developer tool does
Get set up
- Create a fine-grained personal access token with no permissions (public data only)
- Paste it in Settings → Conversations → GitHub token
Where it goes
In the dashboard, open Settings and find the Conversations (optional keys) section. Secret values are encrypted before they're saved and only their last four characters are ever shown again.
Settings → Conversations (optional keys)
GitHub tokenencrypted
GITHUB_TOKENA fine-grained token with no permissions is enough: raises search limits and adds Discussions.
••••••••••••
Staying free
Only used when a project's profile has GitHub searches, which the analysis only fills in for developer audiences.
How the quota guard works →Fallback order
For conversations, Larvabot tries these in order and skips any that aren't set up, are out of free quota or are busy.
- 1Hacker News search (Algolia)
- 2Stack Exchange API
- 3YouTube comments (Data API)
- 4GitHub issues & discussions
- 5Bluesky search
- 6Lemmy (federated communities)
- 7Discourse forums
- 8Web discussions (your search keys)