What is vibe coding?
Vibe coding means describing what you want in natural language and letting an AI assistant write the code. With DexPaprika connected to your AI tool, the AI can fetch real crypto data while it builds — testing endpoints, checking response shapes, and writing working code from the start. This tutorial shows the workflow, not a fixed script. Your results will vary based on your AI tool, your prompts, and what you ask for.Prerequisites
Connect DexPaprika to your AI tool using one of these methods:| Tool | Setup |
|---|---|
| Claude Code | /plugin marketplace add coinpaprika/claude-marketplace then /plugin install dexpaprika |
| Cursor | Add MCP server URL https://mcp.dexpaprika.com/sse in Settings → Tools & Integrations |
| VS Code | Add MCP server via Copilot Chat settings |
| Claude Desktop | Add "dexpaprika": {"url": "https://mcp.dexpaprika.com/sse"} to claude_desktop_config.json |
Example 1: “Build me a token price dashboard”
The prompt
Give your AI a clear, specific prompt:What happens
The AI will:- Call the DexPaprika search endpoint to find ETH and BTC token addresses and networks
- Read the token details endpoint to understand the response format
- Write HTML/CSS/JS that fetches from the DexPaprika REST API
- Use
summary.price_usdfor the price,summary.24h.volume_usdfor volume, andsummary.24h.last_price_usd_changefor the percentage change - Add a
setIntervalfor auto-refresh
Tips for better results
- Be specific about data fields. “Show the 24h price change” is better than “show some stats”
- Name the tokens and networks. Don’t assume the AI knows every address
- Mention the API by name. Say “Use the DexPaprika API” so the AI uses the MCP tools or REST endpoints
- Start simple, then iterate. Get a working version first, then ask for styling, charts, or more features
Example 2: “Find me the hottest new pools”
The prompt
What the AI does
The AI will use the filter endpoint:Example 3: “Build a price comparison tool”
The prompt
What the AI does
- Finds WETH addresses on each network (via search or by knowing common addresses)
- Makes three batch pricing calls (one per network)
- Compares results and formats output
Example 4: “Add a live price ticker”
The prompt
What the AI does
The AI will use the streaming API:Iteration tips
Once you have a working first version, iterate with follow-up prompts:- “Add a chart showing the last 7 days of price history” (AI will use OHLCV endpoint)
- “Show the top 5 pools for each token” (AI will use token pools endpoint)
- “Add error handling for when the API is down”
- “Make it responsive for mobile”
- “Add dark mode”
- “Export the data to CSV”
Common issues
AI doesn't use DexPaprika
AI doesn't use DexPaprika
Be explicit: “Use the DexPaprika API at api.dexpaprika.com” or “Use the DexPaprika MCP tool.” If using an IDE integration, make sure the MCP server is connected and showing as active.
AI uses wrong endpoint or field names
AI uses wrong endpoint or field names
Point the AI to specific documentation: “Check the token endpoint response format at docs.dexpaprika.com” or provide the correct field path directly: “The price is at response.summary.price_usd, not response.price.”
CORS errors in browser
CORS errors in browser
The DexPaprika REST API supports CORS, so browser requests should work. The streaming API also supports CORS. If you see CORS errors, check that the URL is correct (https, not http).
AI hallucinates endpoints that don't exist
AI hallucinates endpoints that don't exist
If the AI invents endpoints, ground it: “Only use endpoints from the DexPaprika API reference at docs.dexpaprika.com/api-reference/introduction. The available endpoints are: /networks, /search, /networks//pools, /networks//tokens/, /networks//pools//ohlcv, etc.”