Credentials. The wizard asks for API keys and chat credentials, so store the .env file securely and never post it in a channel.
Who it is forA crypto trader on Robinhood Chain who wants filtered trade ideas delivered to chat instead of scanning many markets by hand.
The problemScanning meme tokens, LP pools, NFT floors, Robinhood Chain alpha, and whale flow manually takes hours and mixes weak signals with strong ones.
The outcomeA running bot that posts call cards only when the swarm consensus reaches the 80% confidence floor, with DRY_RUN keeping execution off by default.
What you need first
- Node.js and npm installed
- Git installed to clone the repository
- API keys and chat credentials for the onboarding wizard (for example Discord or Telegram setup)
- Familiarity with a terminal on Windows, Linux, or macOS
Steps
- Run
git clone https://github.com/runesatsdev/noraz-agent.gitand thencd noraz-agent(the README clone URL differs from the repository URL given, so confirm the source first). - Run
bash setup.shon Linux or macOS, or.\setup.baton Windows. - Run
npm run wizard(ornoraz onboard) and set your API keys, AI models, and TP/SL values. - Run
npm run dev(ornoraz run) to start the live bot. - Open the
#call-meme-robinhoodor other#call-*Discord channel and check that call cards appear with audit data.
Prompt for your agent
Using the noraz-agent repo, set up the bot with DRY_RUN enabled and start it in development mode. Expected output: the bot runs and posts at least one call card or a status message to the configured Discord or Telegram channel. Verify that DRY_RUN is still true in the .env file before reporting success.
Caveat. The README says execution stays under your control through DRY_RUN and manual confirmation, so a call card is a research output and not an automatic trade.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page