axe
Get Started

Environment

Install Axe, wire your model, and connect Hyperliquid and Polymarket — five-minute local setup.

Setting up Axe takes about five minutes. The harness is local-first: you install once, point it at your model and your venues, and everything else lives in your working tree.

Install Axe

The Axe runtime lives at ~/work/axe. The install script copies a stable launcher into your shell.

cd ~/work/axe
./scripts/install-axe.sh

The installer:

  • Copies the current checkout into ~/.axe/axe
  • Runs npm install against that copy
  • Writes launchers to ~/.axe/bin/
  • Symlinks ~/.local/bin/axe and ~/.local/bin/axe-dev

After install, you have two commands:

CommandSourceUse when
axe~/.axe/axeDay-to-day operator sessions
axe-devlive source checkoutIterating on Axe itself

Wire your model

Axe does not bundle a model. On startup it looks for credentials in this order:

  1. A reusable Codex machine token at ~/.codex/auth.json
  2. Provider API keys in your environment or session
  3. The interactive /login flow

Once a credential is available, pick a model with /model. Most operators run a frontier model for sessions and a faster model for watches.

Connect Hyperliquid and Polymarket

Per-account connector configs live under ~/.axe/connectors/ as JSON. You can also use the AXE_HYPERLIQUID_* and AXE_POLYMARKET_* environment variables for ephemeral sessions.

# Read-only public data — no key required
/markets
/price BTC
/book ETH
/odds "Will X win the election?"

Authenticated trading is gated behind the safety policy. Read-only public data works out of the box.

Verify

A clean install should give you:

$ axe
> /markets
… list of Hyperliquid markets …
> /odds "..."
… Polymarket question with current odds …
> /model
… current model …

If /markets returns data and /model reports a usable model, you are ready to start a session. See Best practices next.

On this page