What is the DexPaprika CLI?
A fast, standalone command-line tool for querying on-chain DEX data. Written in Rust. Covers the entire DexPaprika API: token prices, pools, OHLCV, transactions, search, pool filtering, and real-time price streaming via SSE. No API key needed to start. No dependencies. One binary. Source: github.com/coinpaprika/dexpaprika-cliInstall
One-line install (macOS, Linux)
~/.local/bin. You can override the install path:
Download from GitHub
Pre-built binaries for every platform are on the releases page:Build from source
Requires Rust:Verify installation
Commands
Every DexPaprika REST API endpoint has a matching CLI command:dex-pools reads pool search with a dex_name filter. The REST path it used to call,
GET /networks/{network}/dexes/{dex}/pools, was removed and returns 410 Gone, so an older
build of the CLI fails on that command until you upgrade. The command name and arguments are
unchanged; in --raw JSON the rows arrive under results with has_next_page and
next_cursor, and the 24h volume field is volume_usd_24h.Output formats
The CLI outputs tables by default. Switch to JSON for scripting and piping:jq for filtering:
Examples
Get a token price
Search for a token you don’t know the address of
List top pools by volume
Get OHLCV history for a pool
Without a key, OHLCV reaches back 24 hours at1h and up, so start from today (UTC). A free key reaches 7 days at 10m and longer; see OHLCV limits by plan.
Get a technical indicator for a pool
pool-indicator returns RSI, EMA, MACD, Bollinger Bands or VWAP computed from the pool’s candles, on every plan with the same interval and history limits as pool-ohlcv. --indicator is required; pass only the parameters the chosen indicator uses (--period; --fast-period, --slow-period and --signal-period for macd; --std-dev for bbands), because one that belongs to another indicator is refused with a 400. Needs CLI 0.10.0 or later.
token-indicator takes the same flags for a token across all its pools and needs a Dev or Pro key on the paid host. See the technical indicators tutorial.
Stream live prices
Interactive REPL
dexpaprika-cli each time.
Batch prices for a portfolio
Use with AI agents
AI agents running in terminals (Claude Code, Aider, etc.) can install and use the CLI as a tool. The one-liner install works in any shell:dexpaprika-cli directly with --output json --raw for machine-readable output. This is useful when:
- The agent doesn’t have MCP support
- You want the agent to script data pipelines
- You need to pipe output into other tools (
jq,csvkit, scripts) - You’re running headless or in CI/CD
Troubleshooting
Command not found after install
Command not found after install
The installer puts the binary in Add that line to your
~/.local/bin. If that’s not in your PATH, add it:~/.bashrc, ~/.zshrc, or ~/.profile to make it permanent.Permission denied during install
Permission denied during install
The installer tries
~/.local/bin first (no sudo needed). If it falls back to /usr/local/bin, it will ask for sudo. You can also set a custom directory:No data returned for a token
No data returned for a token
Check the network ID (must be lowercase:
ethereum, not Ethereum) and verify the token address. Use dexpaprika-cli search <name> to find the correct network and address.Streaming disconnects
Streaming disconnects
SSE streams can drop due to network issues. The
stream command will show an error. Restart it and the CLI handles reconnection. For production use, wrap it in a script with retry logic.Next steps
REST API Reference
Full endpoint documentation with interactive playground
Streaming API
Real-time price streaming docs
Common Patterns
Standard API workflows
Vibe Coding with AI
Build projects with AI + DexPaprika
FAQs
Do I need an API key?
Do I need an API key?
No. Without one the CLI calls the API keyless, metered per IP against the keyless allowance. A free key from the console raises the allowance and opens 7 days of OHLCV at
10m and longer. Store it with dexpaprika-cli config set-key <KEY>, pass --api-key <KEY> on a single command, or set DEXPAPRIKA_API_KEY; dexpaprika-cli config show tells you which key is in use. On Dev, Pro or Enterprise, point the CLI at the paid host with --base-url https://api-pro.dexpaprika.com or DEXPAPRIKA_API_BASE_URL (0.9.0 and later); transactions and token-ohlcv need it. See upgrading to Pro.What are the rate limits?
What are the rate limits?
Same as the REST API: 10,000 credits per rolling 30 days without a key at 15 requests a minute, 100,000 with a free key at 30 requests a minute. Each CLI command makes one API call.
stream opens a single long-lived SSE connection, and each price update it delivers costs one credit, the same as a REST call. A stream left running all month can outgrow the free allowance, so see Pro pricing if you need 5,000,000 credits at 500 requests a minute.Does the CLI support the filter endpoint?
Does the CLI support the filter endpoint?
The filter endpoint can be accessed via the REST API directly. Check the pool filtering tutorial for examples.
Can I use the CLI on Windows?
Can I use the CLI on Windows?
Yes. Download the Windows binary from the releases page. The install script works on macOS and Linux only.