Capabilities deep dive
Map of every Axe capability layer — the cockpit, the markets, the memory plane, the token rail.
Axe is one harness with several layers. This page is a map of what each layer does and where to read more.
The cockpit
A three-rail terminal interface — research, markets, and rewards — designed for multi-hour operator sessions.
- The research rail holds your active session, your thesis, and your working notes
- The markets rail holds the live tape: order books, funding, odds, watches
- The rewards rail holds your real-time AXE earnings and protocol activity
Read more: The cockpit.
Hyperliquid perps
Native first-class commands for Hyperliquid markets:
/markets,/price,/book,/funding,/oi/perps-open,/perps-updatefor session framing- Watch flows over funding, OI, basis, and order-book imbalance
- A search harness with provenance over historical Hyperliquid state
Read more: Hyperliquid perps.
Polymarket prediction markets
Polymarket is a peer of Hyperliquid in Axe, not a stub.
/odds,/liquidity,/resolution/poly-open,/poly-updatefor session framing- Watches over odds crosses, liquidity shifts, and resolution events
- Cross-venue session framing — one thesis can live across perps and prediction markets
Read more: Polymarket prediction markets.
Memory and automations
Axe captures the work you do and replays the parts you want replayed.
- A structured local session ledger you own
- Persistent memory that survives across sessions
- Scheduled automations that run watches and runbooks while you are away
- Subagents for long-running, parallel investigations
Read more: Memory & automations.
The Axe token rail
The reward layer that turns operator work into ownership.
- Earn AXE the more you use the harness — for sessions, runbooks, watches, and shared insights
- Share in the upside of the surface you helped build
- Monetize your own usage data on your own terms
- Spend tokens to earn tokens — a circular economy where operator work compounds
Read more: The Axe token rail.
Safety and approvals
Axe is opinionated about the boundary between reading and acting.
- Read-only by default — public market data needs no credential
- Explicit approvals before any account-mutating action
- A staged rollout from preview to simulation to testnet to mainnet
- Audit trail and provenance for every action and every claim
Read more: Safety & approvals.