Welcome to the official documentation for EngageAgent, the AI-powered Discord bot designed to elevate Web3 community engagement on Twitter (X). Since Grok AI is native to X enabling direct access to posts and algorithm determination, EngageAgent utilizes Grok AI from xAI to evaluate, incentivize, and provide insights on community-generated content. This approach cultivates genuine momentum on X directly contributing to the community growth and visibility on X, seamlessly linked to on-chain reward mechanisms.

This guide serves Web3 founders, community managers, and participants with straightforward, practical instructions.


Overview

What is EngageAgent?

EngageAgent functions as a Discord bot that transforms X posts from your community into verifiable, scored contributions eligible for rewards. Upon detecting a tweet link in designated channels, it performs ownership verification using secure OAuth, retrieves the full thread (including replies and media), and generates a score from 0 to 10 via Grok AI. Scores align precisely with your defined project focus, such as "DeFi yield optimization strategies" or "NFT narrative development."

Rapid Onboarding: Invite the bot to your Discord server, establish a dedicated project channel, and observe as members submit tweets to receive immediate scores and feedback.

image.png


How It Works

EngageAgent follows an efficient, automated workflow: Submission → Verification → Evaluation → Incentivization → Insight Generation.

  1. Initial Configuration (Administrators Only): Use the invite link to invite the bot into your server. Execute /addproject to associate a specific Discord channel with your project's thematic focus. This initiates a complimentary trial period supporting up to 5 scores, allowing initial testing without commitment. The tenant_id parameter serves as a unique identifier for your project (e.g., "DeFiDAO" or "NFTRevolution"), acting as the key across all features—used for scoring, analytics, subscriptions, and payments. Choose a concise, memorable string without spaces or special characters; it must remain consistent for upgrades like /paycrypto, where mismatched IDs will fail invoice linking. Also, run /setupwelcome to pin the welcome message and basic guides for members of the channel.
  2. User Onboarding (Members): The /register [wallet_address] command establishes a secure connection between the user's X account and wallet via OAuth 2.0 with PKCE for enhanced security. It accommodates multiple blockchain formats, including EVM (starting with 0x), Solana (32-44 base58 characters), Bitcoin (starting with 1, 3, or bc1), and Cosmos (starting with cosmos1) for now.
  3. Content Submission and Scoring: Members post a direct tweet link in the configured channel within 24-48 hours of the original post to maximize relevance and algorithm alignment—submissions outside this window may still process but could receive adjusted scores due to timeliness factors in Grok's evaluation. The bot fetches the complete thread—including text, media URLs, metadata (e.g., timestamps, engagement signals), and conversation context that relates to the project’s focus—verifies authorship against the registered X handle, and applies Grok AI for scoring. For instance, a project-relevant meme incorporating a reply-prompting question might receive 7.5/10, with embedded feedback highlighting strengths and optimization suggestions, which other members of the community sees and gain insights to contribute more quality X posts to the project’s visibility on X.
  4. Incentivization: Administrators export aggregated scores on a weekly or monthly basis using commands like /weeklyrewards or /monthlyrewards. Only scores meeting or exceeding the 5.0 threshold qualify for rewards, such as token airdrops or crypto payouts, with CSV outputs including user rankings, total points, and averages.
  5. Insight Generation: Background tasks produce automated reports every 7 days, identifying patterns like "Transition 20% of content to video-embedded threads for potential 4x reach amplification." Custom reports are available via /communityreport [number_of_days].