DexScreener Pair Security Scraper — Honeypot, Rugpull, Audit & LP Lock Detection

The unique deep-data export for DEX pairs — security audit, honeypot detection, contract verification, liquidity locks, holder distribution and authoritative CoinGecko + CoinMarketCap metadata that DexScreener's public REST API does NOT expose. Bulk-resolve hundreds — or thousands — of DEX pair addresses across Solana, Ethereum, Base, BSC, Polygon, Arbitrum, Avalanche and 30+ chains in one run.

Built for rugpull detection systems, due-diligence dashboards, retail wallet safety apps, security firms, audit pipelines, on-chain forensics, KYT / KYC platforms and trading-bot safety filters.

🟢 No API key. No login. Built-in Cloudflare bypass via Apify Residential proxy + TLS fingerprint rotation.

---

🚀 Why this scraper

DexScreener's public REST API (api.dexscreener.com) is excellent for price, liquidity, volume and basic pair identity — but it deliberately omits the deeper signals that actually answer "is this token safe to trade?":

• Honeypot detection — can users sell, or is there a sell tax that traps buyers?
• Contract verification — is the source code published, or is it opaque?
• Ownership renunciation — does the deployer still have admin keys?
• Mint / burn / blacklist capabilities — can the owner mint unlimited supply, burn user balances, or block specific addresses from selling?
• Hidden owner / proxy contracts — is real control obscured behind upgradeability?
• Liquidity locks — is LP actually locked (UNCX, Team Finance, Onlymoons, Pinksale, etc.), and for what percentage?
• Holder distribution — how many holders, how concentrated at the top?
• Authoritative metadata — what does CoinGecko / CoinMarketCap actually say about this token's identity?

DexScreener's frontend pair page renders all of this from an internal endpoint (io.dexscreener.com/dex/pair-details/v4) that uses Quickintel for EVM audit, on-chain lock data for liquidity locks, and direct CoinGecko + CoinMarketCap integrations. This scraper accesses that same endpoint at scale, bypassing Cloudflare via Apify Residential proxy and got-scraping's TLS fingerprint rotation.

The output is the only commercial-grade source of these signals outside DexScreener's own UI.

---

✨ Key features

Feature	What it gives you
🛡️ Quickintel security audit	Honeypot, verified, renounced, mint, burn, blacklist, multi-blacklist, whitelist, hidden owner, proxy, external contract risk, obfuscated address risk
🔒 Liquidity lock data	UNCX, Team Finance, Onlymoons, Pinksale and other lockers with exact percentage locked + lock contract URL
👥 Holder distribution	Total holder count + top holders array, LP holder count
📖 CoinGecko metadata	Categories, official description, ID, URL
📊 CoinMarketCap metadata	Tags, websites, Twitter, launch date, CMC ID
📝 DexScreener-managed metadata	Verified name, description, social links, creation timestamp
💰 Supply data	Total, circulating, max supply from authoritative sources
☁️ Cloudflare bypass built-in	Apify Residential proxy + got-scraping TLS fingerprint rotation
🗃️ 40+ flat columns	No nested JSON, ready for spreadsheets and BI tools
🔓 No API key, no login	Works out of the box

---

🎯 Built for these use cases

1. Rugpull / honeypot detection systems

Flag tokens where isHoneypot=true, canMint=true, canBlacklist=true, lpLockTotalPercentage < 100, or holdersCount < 100 with concentrated top holders. Schedule the actor over your token universe and pipe red-flag tokens into your alert system.

2. Trading-bot safety filter

Before opening a position, run a 1-pair lookup. If auditProblem=true or isHoneypot=true, skip the trade. Saves capital from obviously dangerous tokens.

3. Retail wallet safety apps

Show users a risk indicator before they confirm a swap. "This token has minting enabled and unlocked liquidity — high risk."

4. Security firm bulk audits

Run a daily sweep of trending tokens to generate intelligence reports for clients. "Top 50 DEX-traded tokens with mintable supply this week."

5. Due diligence dashboards

Pre-trade or pre-investment audit reports for every position. Integrate the output into your compliance / OTC desk workflow.

6. Anti-scam research

Catalog the patterns. Tokens with hidden owners + low holders + boosted on DexScreener within 24 hours of launch = textbook setup. Build the dataset, train the model.

7. KYT / KYC enrichment

Wallet-screening platforms can use the audit signals to flag transactions involving high-risk tokens.

8. On-chain forensics

Investigators correlating wallet activity with token risk profile. Did the suspect interact with known mintable / blacklist-capable tokens?

9. Insurance & compliance reporting

Document the security posture of all tokens your protocol or fund touches. Audit trail.

---

📥 Inputs

Field	Type	Required	Description
pairs	string[]	✅ Yes	List of chainId:pairAddress entries. Example: ethereum:0x5628F3bb1f352f86Ea173184ffEe2E34b8fc2dc8. Pair addresses are on-chain LP / pool addresses (visible in DexScreener pair URLs).
useProxy	boolean	No	Use Apify Residential proxy (default true). Strongly recommended for production.
proxyGroups	string[]	No	Apify proxy group names. Default ["RESIDENTIAL"].
skipHolders	boolean	No	Omit the full holders array (keep holdersCount only). Reduces output size.
maxConcurrency	int	No	Parallel requests (1–10). Default 3 (internal endpoint has stricter rate limits than public API).

Example inputs

Default — single pair full audit:

{
  "pairs": ["ethereum:0x5628F3bb1f352f86Ea173184ffEe2E34b8fc2dc8"]
}

Bulk audit — 100 pairs:

{
  "pairs": [
    "ethereum:0xabc...",
    "solana:def...",
    "base:0x123...",
    "..."
  ],
  "maxConcurrency": 3
}

Lightweight (no full holder list):

{
  "pairs": ["ethereum:0x..."],
  "skipHolders": true
}

---

📤 Output (per pair)

{
  "chainId": "ethereum",
  "pairAddress": "0x5628F3bb1f352f86Ea173184ffEe2E34b8fc2dc8",
  "tokenAddress": "0xcab254f1a32343f11ab41fbde90ecb410cde348a",
  "tokenName": "Froge",
  "tokenSymbol": "FROGE",
  "tokenDecimals": 18,
  "tokenCreatedAt": "2024-10-31T15:35:59.000Z",

  "contractVerified": true,
  "contractRenounced": true,
  "contractCreator": "0x34919f7dd781e5cdbda923392dbc627add997a8f",
  "isHoneypot": false,
  "auditProblem": true,
  "auditExtra": "Liquidity low or problem with the purchase!",
  "canMint": false,
  "canBurn": false,
  "canBlacklist": false,
  "canMultiBlacklist": false,
  "canWhitelist": false,
  "hiddenOwner": false,
  "isProxy": false,
  "hasExternalContractRisk": false,
  "hasObfuscatedAddressRisk": false,

  "lpLockTotalPercentage": 100,
  "lpLocks": [
    {
      "tag": "UNCX",
      "address": "1-0xfd235968e65b0990584585763f837a5b5330e6",
      "amount": "97360743942280095720036981",
      "percentage": 100,
      "url": "https://app.uncx.network/lockers/univ3/chain/1/address/0x5628f3bb..."
    }
  ],

  "totalSupply": 649675271791611.8,
  "circulatingSupply": 649675271791611.8,
  "maxSupply": null,

  "holdersCount": 4282,
  "holders": [/* top holders array */],
  "lpHoldersCount": 11,

  "cgId": "froge",
  "cgUrl": "https://www.coingecko.com/en/coins/froge",
  "cgCategories": ["Ethereum Ecosystem", "Meme"],

  "cmcId": 35139,
  "cmcName": "Froge",
  "cmcSymbol": "FROGE",
  "cmcTags": [{"name":"Memes","group":"CATEGORY"}],
  "cmcWebsites": ["https://froge.io/"],
  "cmcTwitter": ["https://twitter.com/frogetoken"],
  "cmcDateLaunched": "2024-01-28T00:00:00.000Z",

  "cmsName": "Froge",
  "cmsDescription": "...",
  "cmsLinks": [
    {"label":"Website","url":"https://froge.io/"},
    {"type":"twitter","url":"https://x.com/frogetoken"}
  ],

  "scrapedAt": "2026-05-16T08:42:00.000Z"
}

---

🚨 Risk-scoring guide — how audit fields map to danger

Field	Risk meaning	Severity
isHoneypot: true	Users CANNOT sell. Hard rug.	🔴 Critical
auditProblem: true	Liquidity issue or purchase restriction detected	🟠 High
canMint: true	Owner can mint unlimited supply → dilution risk	🔴 Critical
canBurn: true	Owner can burn user balances → asymmetric power	🟠 High
canBlacklist: true	Owner can block specific addresses from trading	🟠 High
canMultiBlacklist: true	Mass-blacklist capability	🔴 Critical
hiddenOwner: true	Real ownership obscured	🟠 High
isProxy: true	Upgradeable contract — owner can swap implementation	🟠 High
hasExternalContractRisk: true	Calls external untrusted contracts	🟡 Medium
hasObfuscatedAddressRisk: true	Suspicious addresses in contract	🟡 Medium
contractRenounced: false	Owner still has admin keys	🟡 Medium
contractVerified: false	Source code not published	🟠 High
lpLockTotalPercentage < 100	Soft-rug risk	🟡 Medium
lpLockTotalPercentage < 50	High soft-rug risk	🔴 Critical
holdersCount < 50	Early/illiquid token	🟡 Medium
holdersCount < 100 + concentrated top	Whale-controlled	🟠 High

Composite risk score recipe

score = 0
if isHoneypot:                  score += 100
if canMint:                     score += 50
if canMultiBlacklist:           score += 50
if canBurn:                     score += 30
if canBlacklist:                score += 30
if hiddenOwner:                 score += 30
if isProxy:                     score += 20
if not contractVerified:        score += 25
if not contractRenounced:       score += 15
if lpLockTotalPercentage < 50:  score += 30
if lpLockTotalPercentage < 100: score += 10
if holdersCount < 100:          score += 15
if auditProblem:                score += 20

if score >= 100: RISK = "CRITICAL — do not trade"
elif score >= 50: RISK = "HIGH — caution"
elif score >= 25: RISK = "MEDIUM — investigate"
else:             RISK = "LOW"

---

⚙️ How it works

1. Parses chainId:pairAddress entries
2. For each pair, fires a request to io.dexscreener.com/dex/pair-details/v4/{chain}/{addr} via got-scraping (TLS fingerprint rotation) + Apify Residential proxy
3. Bypasses Cloudflare via realistic browser fingerprint + proxy IP rotation
4. Parses the nested response (cg, cmc, cms, qi, ll, holders, lpHolders, su, ta)
5. Flattens 40+ fields into a single row
6. Streams results to the Apify Dataset

---

⚡ Performance & limits

Workload	Time	Notes
1 pair	~3 seconds	Includes proxy connection setup
10 pairs at concurrency 3	~12 seconds	Proxy rotation between requests
100 pairs	~2 minutes	Steady state
1000 pairs	~25 minutes	Plan for proxy quota

The internal pair-details/v4 endpoint is stricter than the public REST API. Recommended concurrency: 2–5. Higher values increase Cloudflare block risk.

Apify Residential proxy traffic counts against your Apify proxy data quota. Each request uses ~50–200 KB depending on response size. 1000 pairs ≈ 100–200 MB of proxy bandwidth.

---

💰 Cost model

Pay-Per-Result — billed only on the actual pair rows saved. Plus Apify Residential proxy bandwidth.

---

🔄 Schedule for continuous monitoring

• Daily — refresh audit data for your watchlist of monitored tokens
• On-demand via API — single-pair lookup before every trade in your bot
• Weekly — bulk sweep of "trending" / "newly launched" tokens for security intelligence reports

---

🛠️ FAQ

Is this scraping? We use the same HTTP endpoint that the official DexScreener frontend calls, with proper browser headers via residential proxy. No browser automation, no DOM scraping.

Why is concurrency lower than other scrapers? The internal endpoint has stricter rate limits than the public REST API. Higher concurrency increases Cloudflare block risk and proxy spend.

How fresh is the audit data? DexScreener refreshes audit signals (via Quickintel for EVM chains, on-chain monitors for liquidity locks, periodic syncs for CoinGecko/CoinMarketCap) typically within minutes of contract or supply changes.

What if a chain isn't supported? Audit data depends on per-chain integration:

• EVM chains (Ethereum, BSC, Base, Polygon, Arbitrum, Avalanche, Optimism, Fantom) get the richest Quickintel audit.
• Solana gets a smaller subset (no Quickintel; relies on Solana-specific signals like supply analysis and metadata).
• Other chains (Sui, TON, Tron, Aptos, etc.) get even less audit detail.
• All chains get the LP lock data where applicable.

What if a pair has no audit data? Audit fields return null. The row is still saved with whatever data is available (metadata, supply, holders).

Does this work for newly launched tokens? Quickintel typically runs within 5–60 minutes of token creation. For very fresh tokens (< 5 min old), expect some audit fields to be null initially.

Why is useProxy=true recommended? Without proxy, requests come from a single IP. Cloudflare flags repeated requests and starts returning 403s. The residential proxy rotates IPs across requests, mimicking organic traffic.

Can I get holder addresses? Yes — when skipHolders=false (default), the holders array contains top holders by balance. Set skipHolders=true to omit this and just keep holdersCount.

Can I batch? The internal endpoint doesn't support batched lookups. Each pair = 1 request. Use concurrency to parallelize.

What about CoinGecko / CoinMarketCap rate limits? We use DexScreener's pre-cached version. No CG/CMC API key needed; no separate rate limit to worry about.

Why does my Solana lookup return holdersCount=null? Solana holder analytics isn't integrated as deeply on DexScreener's side. Use Solscan or Helius API if you need detailed Solana holder data.

---

📚 Related scrapers in the DexScreener suite

Scraper	Purpose
dexscreener-token-pairs-scraper	Token address → ALL pairs (multi-chain).
dexscreener-search-pairs-scraper	Free-text query → matching pairs.
dexscreener-pair-watchlist-scraper	Pair address → current data.
dexscreener-boosted-tokens-scraper	Currently boosted/promoted tokens + marketing spend.
dexscreener-pair-security-scraper	You are here. Deep audit, holders, locks, CG/CMC metadata.

Recommended workflow: Use dexscreener-boosted-tokens-scraper or dexscreener-token-pairs-scraper to discover tokens, then feed their pair addresses into this scraper for security verdict before any action.

---

🔑 Keyword cloud

Core: dex honeypot detector, rugpull detector, token audit api, defi security scanner, liquidity lock checker, uncx lock checker, dex holder data, token holders api, contract audit api, dex risk api, dex due diligence, defi audit data, smart contract verification, mintable token detector, blacklist detector.

Per check type: honeypot api, contract renounced checker, contract verified api, mint function detector, burn function detector, blacklist function api, hidden owner detector, proxy contract detector, liquidity lock api, lp lock percentage checker, holder concentration api.

Per chain: ethereum token audit, solana token security, base chain audit, bsc honeypot detector, polygon rugpull check, arbitrum token audit, avalanche security scan.

Per locker: uncx lock data, team finance lock checker, onlymoons lock api, pinksale lock data, dxsale lock checker.

Per audience: rugpull prevention for traders, token security for wallets, defi safety for retail, security api for compliance, smart contract risk api, kyt token enrichment, defi forensics api, audit data for security firms.

Per use case: memecoin safety check, dex pair audit bulk, defi audit pipeline, anti scam research, security intelligence crypto, trading bot safety filter, due diligence dashboard, on-chain forensics data.