DEX Screener Token Pairs Scraper

Export DEX Screener token pair snapshots for symbols, addresses, chains, prices, liquidity, volume, websites, and socials.

Data fields

FieldTypeDescription
querystringInput query that produced the pair.
chainIdstring | nullValue exported as chainId.
dexIdstring | nullValue exported as dexId.
pairUrlstring | nullValue exported as pairUrl.
pairAddressstring | nullValue exported as pairAddress.
baseTokenobjectValue exported as baseToken.
quoteTokenobjectValue exported as quoteToken.
priceNativestring | nullValue exported as priceNative.

Input preview

queriesToken queries *
chainIdsFilter by chain IDs
maxResultsPerQueryMaximum pairs per query
includeWebsitesAndSocialsInclude websites and socials
requestDelayMsDelay between queries (milliseconds)
proxyConfigurationProxy configuration

API and agents

This actor can be run through Apify API, datasets, webhooks, schedules, and the official Apify MCP server.

How this actor works

See example inputs, outputs, API usage, and practical limits before running this actor on Apify.

Open Apify page

DEX Screener Token Pairs Scraper exports DEX Screener crypto token pair data for symbols, addresses, chains, prices, liquidity, volume, websites, and socials.

What data it exports

DEX Screener Token Pairs Scraper exports structured DEX Screener crypto token pair data by token symbol, pair name, token address, or pair address. It turns DEX Screener search results into clean CSV, JSON, Excel, and API-ready token pair datasets for crypto watchlists, market research, token discovery, and liquidity monitoring. Key fields include query, chainId, dexId, pairUrl, pairAddress, baseToken, quoteToken, priceUsd, liquidityUsd, volume, and fetchedAt.

Use cases

  • Crypto analysts comparing liquidity and volume across DEX pairs.
  • Trading and alerting teams monitoring token watchlists.
  • Web3 researchers enriching token databases with websites and socials.
  • Growth and BD teams finding active projects and markets.
  • Developers building dashboards, bots, and automated market data workflows.

Example input

{
  "queries": ["SOL/USDC", "WETH"],
  "chainIds": ["solana", "ethereum"],
  "maxResultsPerQuery": 10,
  "includeWebsitesAndSocials": true,
  "requestDelayMs": 250
}

Example output

{
  "query": "SOL/USDC",
  "chainId": "solana",
  "dexId": "raydium",
  "pairUrl": "https://dexscreener.com/solana/...",
  "pairAddress": "...",
  "baseToken": { "address": "...", "name": "Solana", "symbol": "SOL" },
  "quoteToken": { "address": "...", "name": "USD Coin", "symbol": "USDC" },
  "priceNative": "1.0",
  "priceUsd": "150.12",
  "txns": { "h24": { "buys": 120, "sells": 98 } },
  "volume": { "h24": 123456.78 },
  "priceChange": { "h24": 2.4 },
  "liquidityUsd": 987654.32,
  "fdv": 1000000000,
  "marketCap": 1000000000,
  "pairCreatedAt": "2024-01-01T00:00:00.000Z",
  "websites": [{ "label": "Website", "url": "https://example.org" }],
  "socials": [{ "type": "twitter", "url": "https://x.com/example" }],
  "fetchedAt": "2026-07-10T08:00:00.000Z"
}

Input settings

Field Type Required Description
queries array of strings Yes Token symbols, names, pairs, token contract addresses, or pair addresses.
chainIds array of strings No Keep selected DEX Screener chains such as solana, ethereum, base, bsc, polygon, or arbitrum.
maxResultsPerQuery integer No Maximum saved token pairs per query. Default 30, maximum 100.
includeWebsitesAndSocials boolean No Include token website and social profile URLs when available.
requestDelayMs integer No Delay between queries for large watchlists.
proxyConfiguration object No Optional proxy settings. The public DEX Screener API usually works without a proxy.

Input recipes

Start from a verified public Example task when you want a ready-made configuration:

Tips and limits

  • Use exact pair names such as SOL/USDC when you want tighter results.
  • Add chainIds to reduce noise for multi-chain token symbols.
  • Increase requestDelayMs for large query lists if the API returns rate-limit warnings.
  • DEX Screener can change or omit fields for some pairs; missing values are returned as null or empty arrays.

API usage

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/dexscreener-token-pairs-scraper').call({
  queries: ['SOL/USDC'],
  chainIds: ['solana'],
  maxResultsPerQuery: 10
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

from apify_client import ApifyClient

client = ApifyClient('YOUR_APIFY_TOKEN')
run = client.actor('fetch_cat/dexscreener-token-pairs-scraper').call(run_input={
    'queries': ['SOL/USDC'],
    'chainIds': ['solana'],
    'maxResultsPerQuery': 10,
})
items = client.dataset(run['defaultDatasetId']).list_items().items
print(items)

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~dexscreener-token-pairs-scraper/runs?token=YOUR_APIFY_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"queries":["SOL/USDC"],"chainIds":["solana"],"maxResultsPerQuery":10}'

MCP and agent usage

Use this actor from Apify MCP tools with:

https://mcp.apify.com/?tools=fetch_cat/dexscreener-token-pairs-scraper

Claude CLI add command:

claude mcp add apify-dexscreener-token-pairs --transport http "https://mcp.apify.com/?tools=fetch_cat/dexscreener-token-pairs-scraper"

JSON config block:

{
  "mcpServers": {
    "apify-dexscreener-token-pairs": {
      "url": "https://mcp.apify.com/?tools=fetch_cat/dexscreener-token-pairs-scraper"
    }
  }
}

Example prompts showing MCP usage:

  • "Run DEX Screener Token Pairs Scraper for SOL/USDC and WETH, filter to solana and ethereum, then summarize the highest-liquidity pairs."
  • "Use the Apify DEX Screener tool to export BONK pairs, then list the top 10 by 24h volume."
  • "Fetch token pair data for these contract addresses and return pairs with websites or Twitter links."

Support

Open an issue from the Apify actor page if you need help. Please include:

  • Your input JSON.
  • Expected output.
  • Actual output or error message.
  • The run ID or run URL.
  • A reproducible public URL for the run, if available.

Common questions

Questions and answers reused from the canonical actor README.

Does this need a DEX Screener API key?

No. It uses publicly reachable DEX Screener data.

Can I search contract addresses?

Yes. Add token or pair addresses to queries.

Why do I see multiple chains for one token symbol?

DEX Screener search is cross-chain. Use chainIds to keep only the chains you need.

Is this financial advice?

No. The actor exports public market data snapshots for research and monitoring. Always verify data before making decisions.