aeX402
Solana AMM that uses on-chain Q-learning to adjust swap fees, amplification and farming rewards from observed trades.
not read yet
Use
- For
- Liquidity providers and token launchers on Solana who want automatically tuned pool fees.
- Price
- Price not read
- Activity
- Activity not read yet
- Company
- Domain since 2025domain registered
- Runs as
- CLI
- Used for
- swap tokens on Solana pools with ML-adjusted fees
- provide concentrated liquidity and earn swap fees
- launch a token on a bonding curve with a one-hour deadline
- Domain since2025domain registered
These are aeX402's own statements, read from its pages. We did not audit them. A line that is missing was not found on the pages we read; it does not mean the practice is absent.
- MCP servercom.aex402/rpcverified in the MCP registry
- Stateanswers, 33 toolschecked 2026-10-14
- Address to connectrpc.aex402.com/mcp
- OpenAPI spec24 pathsthe spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
What is aeX402?
Solana AMM that uses on-chain Q-learning to adjust swap fees, amplification and farming rewards from observed trades.
Who is aeX402 for?
Liquidity providers and token launchers on Solana who want automatically tuned pool fees.
Do people use aeX402?
Little sign of use.
Not quite it? Describe the job
betaFive tools from the Atlas that fit it, each judged against what you wrote.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.