Skip to main content
The Upside skills plugin is an open-source bundle that teaches an AI coding assistant — Claude Code or Codex — how to drive Upside for you. Ask in plain language (“let me try it”, “buy BTC”, “show my positions”, “stream trades”) and the assistant runs the real, signed API calls against the QA testnet. It’s the fastest way to experience the exchange without writing any code first.
Everything runs on the QA testnet (https://dev.upsidemax.xyz). Wallets are generated at runtime and funded by the auto-airdrop — no real funds, no mainnet risk, nothing to configure.

chain-dex/dex-skill

Open-source. Clone it, read the code, or contribute. MIT licensed.

What’s in the plugin

Five skills. Start with dex-playground — it’s the guided, one-command experience layer over the others.

Install

1

Clone the plugin

Pick the tab for your assistant.
2

Install the Python dependencies

From the cloned directory, run the one-shot installer.
Requires Python 3.9+. Installs eth-account, eth-keys, eth-utils, eth-hash[pycryptodome], requests, and websocket-client.
3

Activate

  • Claude Code — restart; the five skills appear in /skills and activate automatically when your request matches.
  • Codex / Cursor — start the agent in the repo directory; it loads AGENTS.md and routes your request to the matching skill.

Use it

Just describe what you want. A few examples: You don’t have to memorize commands — the assistant maps your intent to the right flow and keeps the interaction to a single step wherever possible. Replies come back in your language.
Prefer to see the code behind a step? Ask the assistant to “show the request” — the playground can print the exact signed POST /exchange envelope it sent, so you can lift it straight into your own integration. From there, the Authentication and Exchange API pages cover the full signing scheme and every action.

Good to know

  • QA only. The plugin targets the QA testnet by default; production access is arranged with the Upside team.
  • Keys stay local. Wallets are generated at runtime and stored in a local session file — you’re never asked to paste a private key into chat.
  • It’s a starting point. Use it to learn the flows quickly, then build your own integration against the REST and WebSocket APIs documented in the rest of these docs.