Skip to content

DEX Screener

Screen live DEX pairs by category, chain, or search phrase. Security lookups expose GoPlus-derived token contract signals.

GET/v1/dexscreener/data

Get DEX Screener data

Query parameters:

  • category: trending, gainers, losers, new_pairs, or volume. Default trending.
  • network: optional supported chain slug such as ethereum, base, or solana. Unsupported slugs return 400.
  • phrase: optional search phrase. When network is also present, every returned row is restricted to that network.
  • limit: 1 to 50. Default 50.

Each row includes source (Codex or DexScreener). The response also includes source and sources summary fields so mixed/fallback results retain the actual provenance of returned rows; source is null when no rows are returned. observed_at is the newest provider/cache observation represented by the rows, while fetched_at is when Sharpe assembled the response. Each row also carries its own observedAt. Provider-missing numeric fields are null, not zero. DexScreener's REST fallback has exact 1h and 24h activity buckets only; 4h and 12h volume/transaction values remain null instead of being relabeled from its 6h or 24h buckets.

curl -G https://www.sharpe.ai/api/v1/dexscreener/data \
  -H "Authorization: Bearer sk_live_your_key_here" \
  --data-urlencode "category=trending" \
  --data-urlencode "limit=25"
GET/v1/dexscreener/security

Get token security

Query parameters:

  • address: required token contract address.
  • chainId: required Codex network ID.

Security fields are tri-state: true/false are provider-confirmed, while null means GoPlus did not return that check. Missing checks must not be interpreted as a clean contract.

curl -G https://www.sharpe.ai/api/v1/dexscreener/security \
  -H "Authorization: Bearer sk_live_your_key_here" \
  --data-urlencode "address=0x..." \
  --data-urlencode "chainId=1"

Was this page helpful?