Practical overview
When it fits
Use Azimuth when you want a continuously refreshed candidate batch for an agent to evaluate, or want the documented Solana screening, entry and exit workflow. Consider the Robinhood Chain path when screening and signals are sufficient; its exit loop is disabled by default.
Who it is for
- Liquidity providers seeking automated pool screening and position management on Solana.
- Hermes agent operators who want to review batches of screened liquidity-pool candidates.
- Operators exploring pool signals for Uniswap v3/v4 on Robinhood Chain, with venue-specific exit limitations.
Documented uses
- Continuously discover and screen candidate pools against configurable quality and risk gates.
- Send all qualifying pools from a screening cycle as a batch for agent ranking and selection.
- Automate Solana liquidity-position entry and monitor exits.
- Keep track of previously signalled pools using in-memory or optional Redis deduplication.
Requirements & limits
The repository is public and identifies the project as MIT-licensed. Setup requires a Hermes profile; Solana execution requires a funded wallet and RPC endpoint. Redis is optional for deduplication persistence or sharing across instances.
- Solana Meteora DLMM supports screening, entry and automated exits; Robinhood Chain Uniswap v3/v4 support is described as screening and signaling, with exits disabled until deployment.
- The daemon emits a batch of qualifying pools per cycle rather than selecting and deploying a pool itself; the Hermes agent makes the selection decision.
- Solana signal sourcing uses Meteora’s public discovery API without third-party accounts or API keys. Robinhood Chain discovery is described as keyless, but its token-safety gates want a GMGN key and fail open without one
- The documented build and execution stack spans Go 1.22+, Hermes, Node.js 18+ and Python 3; Redis is optional.
- The README states that the system trades real funds and presents the project as beta.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Install Azimuth into a Hermes profile
Build the daemon and connect its skill, webhook subscription and monitor templates to an existing Hermes profile.
Before you start
- Go 1.22+
- Node.js 18+ and Python 3 for the Solana skill
- A Hermes agent profile
Steps
Clone the Azimuth repository and change into its directory.
Run install.sh with the target Hermes profile path.
Create the repository .env and set HERMES_WEBHOOK_SECRET to match the webhook subscription.
Configure the profile .env with the required wallet and RPC settings for Solana execution.
Set up the daemon environment and launch ./azimuth as described in the README.
Expected outcome
The daemon is built and configured to send pool-signal batches to the Hermes profile; Solana skill components are installed for the profile.
Guide limitations
- The install script does not create either environment file; they must be configured separately.
- A funded Solana wallet and RPC endpoint are needed for Solana execution.
- Robinhood Chain exit automation is disabled until separately deployed.
- This system can trade real funds.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 13 October 2026
- Original website title
- pgen0x/azimuth · Official homepage title · retained in its source language

