Introducing Axe
The operator harness for on-chain markets — Hyperliquid perps and Polymarket prediction markets in one terminal cockpit, on a protocol that pays its operators.
Axe is the operator harness for on-chain markets, built so that the more you use it, the more you own of it.
Axe gives Hyperliquid and Polymarket users a single terminal-grade cockpit to research, plan, monitor, and act — without leaving for native UIs and without surrendering their work to a closed platform. Every session you run on Axe is yours: it earns you tokens, feeds your memory, and contributes to a shared protocol that pays its operators back.
If a market workflow can be expressed as a session — a question, a watch, a runbook, an action — Axe can hold it for you.
Already Set Up? Get Started Now
Set up your environment
install axe, wire your model, point at Hyperliquid and Polymarket.
Best practices
how operators get the most leverage out of Axe sessions.
Capabilities deep dive
the cockpit, the markets, the memory layer, the token rail.
Use case gallery
concrete operator workflows running on Axe today.
What are Axe's strengths?
Axe is designed for ambitious market operators — traders, researchers, market makers, and analysts who want a real working surface, not a chat shell.
It is best for:
-
Running deep, multi-hour market work end-to-end
- Framing perps positions on Hyperliquid with funding, basis, and squeeze context
- Reading prediction-market odds on Polymarket against catalysts and news flow
- Building research notes that persist as memory and become tomorrow's runbooks
- Standing up scheduled monitors that page you when the world changes
-
Operating across Hyperliquid and Polymarket without leaving the cockpit
- Native order-book, funding, OI, and price commands for Hyperliquid markets
- Native odds, liquidity, and resolution-tracking for Polymarket questions
- Cross-venue session framing so a single thesis can live across perps and prediction markets
- Watch flows that surface only the events that matter to your current session
-
Turning your own work into compounding leverage
- Sessions, watches, and runbooks are captured in a structured local ledger
- Memory persists across sessions so context never has to be rebuilt
- Automations and subagents replay your runbooks while you sleep
- Usage data is yours to monetize — the protocol pays operators for the trail they leave behind
-
Composing intelligence with safety
- A search harness with provenance for every claim, every quote, every fill
- Explicit approvals and policy controls before any account-mutating action
- Local-first by default; remote and hosted surfaces are opt-in
- An audit trail you can hand to a counterparty, an LP, or your own future self
Rule of thumb
If you would normally open three tabs, a notebook, and a Telegram thread to work a market question — Axe can hold the whole session in one place.
General Product Features
Axe is the operator surface; everything else is a module that plugs into it. The product has three faces:
The Cockpit
A three-rail terminal interface — research, markets, rewards — that keeps your thesis, the live tape, and your protocol earnings in view at the same time.
The Market Surface
A unified command layer over Hyperliquid and Polymarket. Order books, funding, odds, liquidity, and watches are first-class verbs in your session, not links you click out to.
The Token Rail
Every session, watch, runbook, and shared insight contributes to the protocol. Operators earn AXE for using the harness, share in the upside of the surface they helped build, and can monetize their own usage data on their own terms.
The Axe Interface
The cockpit is a terminal application, not a web app. That choice is deliberate: market operators already live in terminals, and a TUI is the only surface that can hold a multi-hour session, a live watch, and a working memory at the same time without competing with browser tabs.
You launch Axe with one command. From there, slash commands frame sessions (/perps-open, /poly-open), market verbs read state (/markets, /price, /book, /odds), and the reward rail tracks what your session is earning in real time.
Getting Access
Axe runs locally. There is no waitlist, no hosted control plane, and no dependency on a closed account.
You bring your own model — Codex token reuse is automatic, and provider API keys can be set per session. Hyperliquid and Polymarket connectors are configured per account under ~/.axe/connectors/.
See Environment for the full setup walkthrough.
Feedback
Axe is built in the open with the operators who use it. Roadmap, bugs, and feature requests are tracked in Linear (team USB, project Axe v1); the canonical issue store is Beads, which mirrors one-way to Linear.
If you have access to the Axe repo, file directly. If you don't, the Hyperliquid module and the status & roadmap pages are the public surface for following along.
About Unstable
Axe is the first product from Unstable, a research lab building a decentralized protocol for on-chain market operators. The thesis is simple: the people who do the hardest work on a market — the operators, the analysts, the patient capital — should own the tools they use and share in the surface they create.
Axe is the cockpit. The token rail is the ownership. The protocol is the surface that pays operators back for the work they were already doing.
The more you use it, the more you own of it.