# DexScreener Memecoin and DEX Pairs Scraper - Prices, Liquidity (`thebee/dex-memecoin`) Actor

DEX pair and memecoin market data from DexScreener and GeckoTerminal: price in USD and quote token, liquidity, market cap and FDV, 24h volume and transactions, price change, pair creation time and socials. No API key. Pay per pair row at $0.002.

- **URL**: https://apify.com/thebee/dex-memecoin.md
- **Developed by:** [ttgi](https://apify.com/thebee) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 dex token pair rows

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## DEX and Memecoin Scraper

Live DEX pair data from Dexscreener and GeckoTerminal: prices, liquidity, volume,
transaction counts and price changes. No API key, no browser.

### Why

Zero dedicated DEX or memecoin actors across a 478-listing Apify Store survey.
This data moves by the second, which suits frequent scheduled runs rather than
one-off lookups.

### Usage

```
{
  "source": "both",        // dexscreener | geckoterminal | both
  "query": "SOL",          // search term, chain, or token address
  "network": "solana",     // GeckoTerminal network
  "sortBy": "liquidity",   // liquidity | volume | marketCap | priceChange24h | pairCreatedAt
  "minLiquidity": 0,
  "limit": 100
}
```

### Output

`source`, `chain`, `dex`, `pairAddress`, `url`, `baseToken`,
`baseTokenAddress`, `quoteToken`, `priceUsd`, `priceNative`, `fdv`,
`marketCap`, `liquidityUsd`, `volume24h`, `txns24h`, `priceChange5m`,
`priceChange1h`, `priceChange6h`, `priceChange24h`, `pairCreatedAt`,
`imageUrl`, `socials`, `websites`.

Rows are normalised across both APIs and tagged with `source`, so you can tell
Dexscreener rows from GeckoTerminal ones.

### Use cases

- **New pair detection** — sort by `pairCreatedAt` for freshest launches
- **Liquidity ranking** — most credible pairs by depth
- **Volume anomalies** — high volume with low liquidity is worth a look
- **Socials and websites** — `socials` and `websites` help vet a token
- **Cross-venue comparison** — same pair priced on different DEXs

### Honest notes

- GeckoTerminal enforces a strict per-minute request cap and answers HTTP 429
  well before its documented limit. The actor retries with backoff; if you run
  it very frequently you may still see a partial result, and the run reports
  which source failed rather than silently returning fewer rows.
- `fdv` and `marketCap` are frequently null on new or thin pairs.
- Price-change windows differ slightly between the two APIs, so compare like
  with like when mixing sources.
- Memecoin data is highly volatile and frequently manipulated. Treat it as
  market data, not as a recommendation.

*Pronouns: they/them.*

# Actor input Schema

## `source` (type: `string`):

Which API to pull from.

## `query` (type: `string`):

Dexscreener search term, chain, or token address.

## `network` (type: `string`):

Network id for trending pools.

## `sortBy` (type: `string`):

Metric to rank pairs by.

## `minLiquidity` (type: `integer`):

Drop pairs below this liquidity.

## `limit` (type: `integer`):

How many pairs to return.

## Actor input object example

```json
{
  "source": "both",
  "query": "SOL",
  "network": "solana",
  "sortBy": "liquidity",
  "minLiquidity": 0,
  "limit": 100
}
```

# Actor output Schema

## `source` (type: `string`):

The Source of the pair.

## `chain` (type: `string`):

The Chain of the pair.

## `dex` (type: `string`):

The DEX of the pair.

## `pairAddress` (type: `string`):

The Pair address of the pair.

## `url` (type: `string`):

The URL of the pair.

## `baseToken` (type: `string`):

The Base token of the pair.

## `baseTokenAddress` (type: `string`):

The Base token address of the pair.

## `quoteToken` (type: `string`):

The Quote token of the pair.

## `priceUsd` (type: `string`):

The Price USD of the pair.

## `priceNative` (type: `string`):

The Price native of the pair.

## `fdv` (type: `string`):

The FDV of the pair.

## `marketCap` (type: `string`):

The Market cap of the pair.

## `liquidityUsd` (type: `string`):

The Liquidity USD of the pair.

## `volume24h` (type: `string`):

The 24h volume of the pair.

## `txns24h` (type: `string`):

The 24h transactions of the pair.

## `priceChange5m` (type: `string`):

The 5m change of the pair.

## `priceChange1h` (type: `string`):

The 1h change of the pair.

## `priceChange6h` (type: `string`):

The 6h change of the pair.

## `priceChange24h` (type: `string`):

The 24h change of the pair.

## `pairCreatedAt` (type: `string`):

The Pair created of the pair.

## `imageUrl` (type: `string`):

The Image URL of the pair.

## `socials` (type: `string`):

The Socials of the pair.

## `websites` (type: `string`):

The Websites of the pair.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("thebee/dex-memecoin").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("thebee/dex-memecoin").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call thebee/dex-memecoin --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,thebee/dex-memecoin"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/43qxlv5zkY5325xXT/builds/y0Ouo3zrAvZ265IOx/openapi.json