DexScreener DEX Pair Data Scraper (No API Key, No Login)

   

Search DexScreener by token term, contract address, or pair URL. Each returned row keeps the chain and pair identifier and exposes token symbols, price, liquidity, volume and transaction counts as flat columns.

Get your first results in under two minutes: open the prefilled input, run the Actor, and inspect the Markets dataset view.

Table of contents

• What it does
• Who uses it
• Data fields
• How to run it
• Input examples
• Live output example
• Limits and data quality
• Pricing
• Tips
• Use-case recipes
• Other market data
• MCP and API
• FAQ
• Related searches
• Disclaimer
• Resources

What it does

Search DexScreener by token term, contract address, or pair URL. Each returned row keeps the chain and pair identifier and exposes token symbols, price, liquidity, volume and transaction counts as flat columns.

This Actor stores one row per valid source record. It keeps provider identifiers so you can join the output to another dataset later. It does not place trades, predict outcomes, or create values the source did not return.

What you can collect

• ✅ Search pair listings across chains and DEXes
• ✅ Look up a token contract or a specific pair URL
• ✅ Read USD/native price, liquidity, volume and price changes
• ✅ Export base and quote token identifiers as top-level fields

Who uses it

• DeFi research teams screening public DEX listings
• Builders enriching token and pair watchlists
• Analysts comparing liquidity and 24-hour activity
• Teams that need chain-aware pair IDs for downstream APIs

Data fields

The table contains flat columns for the main values. The default dataset keeps the full structured record. Optional source fields remain null when the upstream did not provide them; a null is not converted to a guessed value.

Always populated on a valid row

Field	Type	Description	Availability
chainId / dexId	string	Chain and decentralized exchange identifiers.	Always
pairAddress	string	Pair contract or pool identifier returned by DexScreener.	Always
baseTokenSymbol / baseTokenAddress	string	Base token symbol and address, also exposed at top level.	Always
priceUsd	number	Reported pair price in USD. A row is accepted only when numeric.	Always
sourceType	string	Constant identifying DexScreener as the source.	Always

Populated when present in the source

Field	Type	Description	Availability
quoteTokenSymbol / quoteTokenAddress	string	Quote token symbol and address, also exposed at top level.	When supplied
priceNative	number	Pair price in its native quote currency.	When supplied
liquidityUsd	number	Reported USD liquidity.	When supplied
volume24h / volume6h / volume1h	number	Reported volume over the corresponding window.	When supplied
buys24h / sells24h	number	24-hour transactions, flattened from the source object.	When supplied
priceChange24h / priceChange1h	number	Reported price change percentages.	When supplied
fdv / marketCap	number	Fully diluted value and market cap when returned.	When supplied
url	URL	DexScreener pair page URL.	When supplied

How to run it

1. Open the input form and keep the prefilled example or replace it with your IDs, search terms, or market selectors.
2. Set maxItems to the largest number of rows you need for this run. The source can return fewer matches.
3. Start the Actor and wait for the run to finish. A valid row is written to the default dataset.
4. Open the Markets view, review the source identifier and update time, then export JSON or CSV if needed.

The Actor does not expose a browser or ask for provider credentials. If a lookup has no public match, the run fails with zero stored rows rather than claiming a successful empty dataset.

Input examples

Prefilled run

{
  "queries": [
    "SOL"
  ],
  "tokenAddresses": [],
  "pairUrls": [],
  "maxItems": 3
}

Use the source-specific selectors

SOL token-pair snapshot (check the returned chain)

{"queries":["SOL"],"tokenAddresses":[],"pairUrls":[],"maxItems":3}

Look up pairs for an Ethereum token address

{"queries":[],"tokenAddresses":["0xA0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"],"pairUrls":[],"maxItems":5}

Refresh one known pair

{"queries":[],"tokenAddresses":[],"pairUrls":["https://dexscreener.com/base/<pair-address>"],"maxItems":1}

Input notes

Every input property has a description and prefill in the form. Empty optional arrays are allowed. Array lengths and result limits are clamped by the Actor before a request is sent. Do not include API credentials in the input.

Live output example

This trimmed row was captured from a live run on 2026-10-03. Values change as the provider updates its market data; use it to understand the field names, not as a current quote guarantee.

{
  "chainId": "base",
  "dexId": "aerodrome",
  "baseTokenSymbol": "SOL",
  "baseTokenName": "Solana",
  "baseTokenAddress": "0x311935Cd80B76769bF2ecC9D8Ab7635b2139cf82",
  "quoteTokenSymbol": "USDC",
  "pairAddress": "0x1131DB5977242a03eBeaD1aCD18F80A9A29e5922",
  "priceUsd": 119.29,
  "liquidityUsd": 676308.44,
  "volume24h": 4840847.97,
  "buys24h": 5444,
  "sells24h": 5669,
  "fdv": 28640376,
  "url": "https://dexscreener.com/base/0x1131db5977242a03ebead1acd18f80a9a29e5922"
}

Limits and data quality

The Actor caps maxItems at 50 and accepts up to 30 entries per target list. Free-plan users have a 40 requested-result daily cap per Actor, resetting at 00:00 UTC. Paid Apify plans do not have that daily quota. Search results do not include token holders, audits or a guaranteed new-pair feed.

The Actor preserves the provider’s identifiers and reported values. Where the upstream returns a numeric zero, the dataset keeps zero. Where a field is absent or not parseable, the normalized optional field is null. Invalid lookup IDs are not saved as data rows.

Pricing

$0.00040 per stored valid DEX pair row ($0.40 per 1,000 rows). Apify platform usage is separate. Invalid inputs have no per-result charge.

A charge event is created only for a valid row pushed to the default dataset. Invalid inputs, empty results, and clean no-row failures do not create a per-result event. Apify platform usage charges (if any) are separate from the event price and follow your Apify plan. Set a run-level spending cap when calling the API at scale.

Tips

• Search by a short ticker such as SOL or ETH, then inspect chainId and pairAddress before joining data.
• Use tokenAddresses when the contract is known; symbols are not unique across chains.
• Use pairUrls for a specific pool when you already have its chain and address.
• Compare volume and liquidity together; a large volume number alone does not describe available depth.

For repeatable monitoring, keep the same canonical IDs or tickers in each run and compare snapshots with their update timestamps. Avoid comparing rows across chains or markets solely by display name.

Use-case recipes

These examples use supported inputs and small row caps. Replace IDs or search terms with the records your workflow needs.

SOL token-pair snapshot (check the returned chain)

Input: {"queries":["SOL"],"tokenAddresses":[],"pairUrls":[],"maxItems":3}. Review the returned source ID, status, and freshness before joining the row to another dataset.

Look up pairs for an Ethereum token address

Input: {"queries":[],"tokenAddresses":["0xA0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"],"pairUrls":[],"maxItems":5}. Review the returned source ID, status, and freshness before joining the row to another dataset.

Refresh one known pair

Input: {"queries":[],"tokenAddresses":[],"pairUrls":["https://dexscreener.com/base/<pair-address>"],"maxItems":1}. Review the returned source ID, status, and freshness before joining the row to another dataset.

Other market data

For spot coin price, rank and supply fields, use CoinGecko Market Data. For cross-chain DEX pairs, use DexScreener Pair Data. For public prediction markets, see Polymarket and Kalshi. These sibling links point to the same publisher profile while each Actor is released.

Browse the publisher profile at apify.com/myagizm.

MCP and API

Connect an MCP client to Apify’s hosted MCP server at mcp.apify.com. Authenticate with Apify, then find this Actor using the Store search or expose it in your MCP tool list. The MCP server can run Actors and retrieve datasets under your account permissions.

For scripts and integrations, use the Apify API. Keep your token in an environment variable.

Run and return dataset items synchronously

curl -X POST "https://api.apify.com/v2/acts/myagizm~dexscreener-scraper/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"queries":["SOL"],"maxItems":3}'

Start an asynchronous run

curl -X POST "https://api.apify.com/v2/acts/myagizm~dexscreener-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"queries":["SOL"],"maxItems":3}'

Fetch the default dataset

$curl "https://api.apify.com/v2/datasets/$DATASET_ID/items?clean=true&format=json&token=$APIFY_TOKEN"

Use your API token only in your local environment. Do not paste it into Actor input, datasets, or issue reports.

FAQ

What does one result represent?

One stored row is one normalized DEX trading pair, identified by chainId and pairAddress. The Actor does not charge for a status message, a failed lookup, or a run that stores no valid records.

Is this an official product from the data provider?

No. This is an independent Apify Actor that reads public market data. CoinGecko, DexScreener, Polymarket, and Kalshi keep ownership of their names, sites, and data.

Do I need an API key, cookie, or account?

No user-supplied provider key, login, cookie, or browser session is required for the public endpoints used here. Apify still requires your Apify account to run Actors and access your dataset.

How current are the results?

The Actor requests data when the run starts. Market prices and volumes can change between the upstream response, the saved dataset row, and a later export. Treat each row as a timestamped snapshot, not a live stream.

Does the Actor return historical prices?

No. This Actor returns the public market snapshot exposed by its supported endpoint. It does not reconstruct price history, candle series, or a tick-by-tick order book.

Why can some fields be null or zero?

The upstream may not publish every field for every record. A zero is retained when the source reports zero; null means the source did not provide a usable value. The README field table separates required output from optional fields.

Why can a search return several rows for one term?

A term can match multiple coins, trading pairs, events, or outcome markets. The Actor deduplicates by the source record identifier and applies maxItems after normalization.

What happens when an input is invalid?

Input errors finish SUCCEEDED with no results and no charge; see OUTPUT for the reason. Transport errors and unclassified empty responses remain failures with no per-result charge.

Can one input return no rows even when it is syntactically valid?

Yes. A symbol, ticker, address, or search term can be valid text but have no public match in the selected endpoint or status. Try the provider’s canonical ID or ticker and inspect the returned market status.

What does maxItems control?

maxItems is the maximum number of normalized rows written by one run. It is a result cap, not a promise that the upstream will have that many matches.

Why can prices differ from a trading screen?

The Actor reads the provider’s public discovery/data API. Screens may refresh at a different moment, apply a different filter, or display a live order book. Returned quotes are informational snapshots, not executable trading instructions.

Does this Actor place trades?

No. It only reads public market data and writes normalized rows to the default dataset. It does not connect a wallet, submit orders, move funds, or manage positions.

Can I export the results?

Yes. Apify datasets can be downloaded as JSON, CSV, Excel, XML, and other supported formats. The dataset view exposes the main flat columns for quick inspection; the default dataset remains the complete structured output.

Can I schedule runs?

Yes. Create a schedule in Apify Console or call the Apify API. Choose an interval that matches the upstream update cadence and your use case; frequent polling does not make a cached upstream value fresher.

Can I call the Actor from code?

Yes. Use the Apify API with your own API token, pass the JSON input, and read the run’s default dataset. The API examples below show synchronous run, asynchronous run, and dataset retrieval.

Can an AI agent call it over MCP?

Yes. Connect an MCP client to Apify’s hosted MCP server, authenticate through Apify, and expose this Actor from the Store or the actor tools list. The MCP connection uses your Apify account permissions.

What is the price?

The Actor uses PAY_PER_EVENT pricing and charges only for valid rows saved to the default dataset. Apify platform usage for the run can be billed separately under your plan; check the run and pricing panel before large workloads.

Why is there a minimum run budget?

Apify may show a minimum spending cap for PPE runs even when the per-row price is small. That cap is a limit on a run, not an extra per-row charge. Set maxTotalChargeUsd in API calls when you want a hard ceiling.

Can I submit many inputs at once?

Yes, within the input array limits. Start with a small maxItems value, check the dataset fields, then raise the cap if the upstream response and your budget support it.

What should I do after a timeout or temporary upstream error?

Retry later with the same input and a reasonable maxItems cap. Repeated retries cannot make a provider outage disappear and may consume platform run time even when no rows are saved.

Is the output investment advice?

No. The dataset is for research, monitoring, and software workflows. It does not recommend buying or selling, and it cannot guarantee that a market price, volume, or outcome probability will remain unchanged.

Does the Actor access private or restricted data?

No. It uses public, unauthenticated market endpoints. It does not bypass login screens, paid access, private accounts, or access controls.

How do I report a broken field or a provider change?

Open the Actor’s Issues tab and include the input shape, approximate run time, run ID, and the field that looks wrong. Do not include your Apify API token or other credentials in an issue.

Can I use the dataset in a commercial dashboard?

You can use the output in your workflow subject to Apify’s terms and the provider’s terms. You are responsible for checking the rights and obligations that apply to your specific use.

Why are there several market rows with similar titles?

Prediction events can contain multiple outcome markets, and DEX tokens can trade in several pairs or on several chains. The record ID and contract or market identifiers distinguish those rows.

Are all fields guaranteed to be populated?

No. The Actor preserves optional values when supplied by the upstream and returns null when an optional source field is absent. Only the required fields listed as always populated gate a row as valid.

Does an empty dataset mean the asset does not exist?

Not necessarily. It can mean the input did not match the endpoint, the record is not in the selected status, or the provider returned a temporary error. Check the input format and notes before drawing a conclusion.

Can I use the sample output as a quote guarantee?

No. The sample documents the output shape from a live response. It is not a quote commitment, an offer, or a guarantee of future availability.

Can I send a ticker instead of an ID?

Use queries for a ticker such as SOL or ETH. Use tokenAddresses for exact token contracts and pairUrls for a known pool. Symbols are not unique: check the returned chain and addresses.

Why does the default input use only a few results?

The prefilled input is deliberately small so you can inspect real records and price fields before increasing maxItems. A small first run also makes it easier to catch a wrong coin ID, chain address, series ticker, or query.

Can I keep the full nested dataset?

Yes. The table view exposes common flat columns, while the default dataset retains the complete normalized JSON row, including arrays and nested objects where the source has them.

Does the Actor change upstream values?

No. It normalizes names and numeric types for a consistent dataset, but it does not calculate a synthetic market price or predict an outcome. A field that comes directly from a provider is identified by the sourceType and source URL fields.

What if an upstream endpoint changes its response?

The Actor validates required business fields before writing a row. If a required field disappears, the run will not silently save an empty success. Report the run ID and changed field in the Issues tab so the mapper can be checked against a fresh response.

Can I use an API token from a different service?

No third-party token is accepted or needed by this input schema. Do not paste secrets into the input. The Actor communicates with the public endpoint and returns the results in your Apify dataset.

Are market prices guaranteed to be executable?

No. A public market-data snapshot may be delayed, cached, or incomplete compared with an exchange order book. It is not an order, quote guarantee, execution price, or recommendation.

Can I filter or transform the exported rows?

Yes. Use the top-level columns in the dataset view, then filter in Apify’s dataset interface or after downloading JSON/CSV. If you need a specific output shape, transform the dataset downstream without changing the source record identifiers.

How should I handle duplicates?

The core deduplicates repeated source identifiers within one run. Separate runs are independent snapshots and can contain the same market or pair because the record still exists at the next observation time.

Can I request all markets in one run?

The Actor caps maxItems and bounds request counts. For broader coverage, use a series, tag, or several small scheduled runs rather than assuming one page is a complete market catalog.

Can this replace the source provider’s own API?

It is a convenient Apify interface and dataset pipeline, not a promise of broader coverage or a replacement for provider documentation. Use the source identifiers and public API URLs in each row when you need to verify a record.

What does no result billing mean?

PPE billing is attached to successfully stored dataset rows. When input validation or the upstream lookup produces no valid row, the bridge fails the run before pushing data. A failed no-row control therefore has zero default dataset item events.

Related searches

DexScreener new pairs · DexScreener new pairs API · DexScreener API free · Dex Screener pair search · Solana token pairs and liquidity · DEX pair price USD · crypto liquidity data · DEX volume and transaction counts · base token contract address lookup · Ethereum DEX pair scraper · Solana DEX pair data CSV · token price across chains · DEXScreener pair URL lookup · pair liquidity monitor · on-chain market pair data

Disclaimer

This Actor is an independent data tool and is not affiliated with or endorsed by the data provider. The output is informational and may be delayed, incomplete, corrected, or unavailable. It is not investment, legal, tax, or financial advice. You are responsible for complying with the terms and laws that apply to your use of the data.

Resources

• Apify API v2
• Apify MCP server
• Dataset export
• Apify schedules
• Publisher profile
• Support: use the Actor’s Issues tab and include a run ID, input shape, and the field to review.

Operational notes

How do I choose between a search term and a direct identifier?

Use a direct identifier when it is known and stable. For DexScreener public DEX pair snapshots, a search term is convenient for discovery, while the source ID or ticker gives a more precise repeatable lookup. The input table describes the accepted shape for each option.

What is a safe first-run size?

The prefill uses a small maxItems value. Keep the first run at that size, inspect the live DexScreener public DEX pair snapshots fields, then increase the cap only when the rows and cost match your workflow.

What fields should I use as a join key?

Use the source-specific identifier columns rather than display titles. Names and titles can change; IDs, tickers, contract addresses, or condition IDs are designed to identify the underlying record.

Can I run this continuously?

You can schedule repeated runs in Apify, but each run is a separate snapshot. Choose an interval that fits the source update cadence and the amount of change you need to observe; do not assume that faster polling creates fresher upstream data.

What if I need a field that is not listed?

First inspect the complete default dataset row and confirm that the source returns the field for the selected record. If the public API exposes it consistently and the field matters to your workflow, open an issue with a run ID and a sample record identifier.

How are failed lookups handled?

A failed lookup never becomes a fabricated result row. The bridge validates required DexScreener public DEX pair snapshots fields before writing to the dataset; when no valid row remains, the run fails and the result event is not charged.

How should I compare two snapshots?

Compare records by their source identifiers and retain the run timestamp. Prices and volumes are mutable, so a changed value can reflect the market moving rather than a parsing error.

Does this Actor provide a complete catalog?

No single request is guaranteed to include the complete provider catalog. The Actor uses bounded pages, selectors, and maxItems to keep a run predictable. Use the provider’s own catalog documentation for coverage guarantees.

Can I share the dataset with a teammate?

Yes. Share access through Apify’s dataset and account controls, or export a file. Treat shared exports as copies of a time-bound snapshot and preserve the source record identifiers.

What does the source URL mean?

The source URL points to a public record or provider page when the Actor can construct or verify that URL. It is included for inspection, not as a promise that the page will remain available or display the same data later.

Why does a valid response still fail row validation?

HTTP success only means the request returned a response. The Actor also checks that required business fields exist and have usable types. A challenge page, unrelated object, or empty payload is not a valid DexScreener public DEX pair snapshots record.

Can I change the row limit between runs?

Yes. maxItems is part of the run input. A smaller cap lowers the amount of data saved; a larger cap remains bounded by the input schema and the upstream request limits.

---

中文说明

DexScreener DEX 交易对数据抓取（无需第三方 API 密钥或登录）

   

按代币关键词、合约地址或交易对 URL 搜索 DexScreener。每行包含链和交易对标识符，并将代币符号、价格、流动性、成交量及交易次数显示为平铺列。

两分钟内查看首批结果：打开预填输入，运行 Actor，然后检查 Markets 数据集视图。

目录

• 功能
• 适用对象
• 数据字段
• 使用步骤
• 输入示例
• 实时输出示例
• 限制与数据质量
• 价格
• 使用技巧
• MCP 与 API
• 常见问题
• 相关搜索
• 免责声明
• 资源

功能

按代币关键词、合约地址或交易对 URL 搜索 DexScreener。每行包含链和交易对标识符，并将代币符号、价格、流动性、成交量及交易次数显示为平铺列。

每条有效来源记录保存为一行。数据保留来源标识符，方便后续连接其他数据集。本 Actor 不进行交易、不预测结果，也不会补造来源没有返回的数值。

可收集的数据

• ✅ 搜索不同区块链和去中心化交易所的交易对
• ✅ 按代币合约或具体交易对 URL 查询
• ✅ 获取美元及原生币价格、流动性、成交量和价格变化
• ✅ 将基础币与报价币标识符导出为顶层字段

适用对象

• 筛选公开 DEX 交易对的 DeFi 研究团队
• 为代币和交易对观察列表补充数据的开发者
• 比较流动性与 24 小时交易活动的分析师
• 需要链和交易对联合标识符的 API 开发团队

数据字段

表格视图提供常用的平铺列，默认数据集保留完整结构。上游没有提供的可选字段为 null，不会被猜测或替换。

有效结果始终包含

字段	类型	说明	可用性
chainId / dexId	string	区块链和去中心化交易所标识符。	始终
pairAddress	string	DexScreener 返回的交易对合约或交易池地址。	始终
baseTokenSymbol / baseTokenAddress	string	基础代币符号及地址，同时提供顶层字段。	始终
priceUsd	number	交易对的美元价格；有效行必须为数值。	始终
sourceType	string	标识目标平台 DexScreener 的常量。	始终

上游提供时包含

字段	类型	说明	可用性
quoteTokenSymbol / quoteTokenAddress	string	报价代币符号及地址，同时提供顶层字段。	有数据时
priceNative	number	以原生报价币表示的交易对价格。	有数据时
liquidityUsd	number	报告的美元流动性。	有数据时
volume24h / volume6h / volume1h	number	对应时间窗口的成交量。	有数据时
buys24h / sells24h	number	24 小时买入及卖出次数，已平铺为顶层字段。	有数据时
priceChange24h / priceChange1h	number	报告的价格变化百分比。	有数据时
fdv / marketCap	number	返回时的完全稀释估值与市值。	有数据时
url	URL	DexScreener 交易对页面链接。	有数据时

使用步骤

1. 在输入表单中保留示例，或替换为你的 ID、关键词和市场筛选条件。
2. 将 maxItems 设为本次运行需要的最大行数；来源实际匹配数可能更少。
3. 启动 Actor 并等待运行完成，检查默认数据集中的有效行。
4. 打开 Markets 视图检查来源 ID 和更新时间，需要时导出 JSON 或 CSV。

Actor 不会要求第三方平台凭据。没有公开匹配结果时，运行会报告失败并写入零行，而不是伪装成成功的空结果。

输入示例

预填输入

{
  "queries": [
    "SOL"
  ],
  "tokenAddresses": [],
  "pairUrls": [],
  "maxItems": 3
}

其他查询方式

SOL 交易对快照（请核对返回的链）

{"queries":["SOL"],"tokenAddresses":[],"pairUrls":[],"maxItems":3}

按以太坊代币合约查询交易对

{"queries":[],"tokenAddresses":["0xA0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"],"pairUrls":[],"maxItems":5}

刷新已知交易对

{"queries":[],"tokenAddresses":[],"pairUrls":["https://dexscreener.com/base/<pair-address>"],"maxItems":1}

所有输入字段都有说明和预填值。可选数组可以留空；Actor 会在发出请求前限制数组和结果上限。不要将密钥放入输入。

实时输出示例

下方记录来自 2026-10-03 的实时数据运行。数值会随来源更新；样例用于说明字段结构，不保证是当前报价。

{
  "chainId": "base",
  "dexId": "aerodrome",
  "baseTokenSymbol": "SOL",
  "baseTokenName": "Solana",
  "baseTokenAddress": "0x311935Cd80B76769bF2ecC9D8Ab7635b2139cf82",
  "quoteTokenSymbol": "USDC",
  "pairAddress": "0x1131DB5977242a03eBeaD1aCD18F80A9A29e5922",
  "priceUsd": 119.29,
  "liquidityUsd": 676308.44,
  "volume24h": 4840847.97,
  "buys24h": 5444,
  "sells24h": 5669,
  "fdv": 28640376,
  "url": "https://dexscreener.com/base/0x1131db5977242a03ebead1acd18f80a9a29e5922"
}

限制与数据质量

maxItems 最大为 50，每个目标数组最多 30 项。免费计划每个 Actor 每天最多请求 40 条结果，UTC 00:00 重置；付费计划没有此每日配额。搜索结果不包含持币人、审计或保证完整的新交易对列表。

Actor 保留来源标识符和来源数值。来源返回数字 0 时，结果仍为 0；来源缺少字段时，规范化的可选字段为 null。无效 ID 不会作为市场数据行保存。

价格

每条有效 DEX 交易对数据行 $0.00040，即每 1,000 行 $0.40。Apify 平台资源费用另计；无效输入没有按结果费用。

只有写入默认数据集的有效行会产生按结果计费事件。无效输入、空结果和无行失败不会计入结果事件。Apify 平台运行资源费用可能按你的计划另行收取。大批量 API 运行建议设置 maxTotalChargeUsd。

使用技巧

• 按 SOL、ETH 等符号搜索，然后核对 chainId 和 pairAddress 再连接数据。
• 已知合约时使用 tokenAddresses；代币符号在不同链上并不唯一。
• 已知链和地址时，用 pairUrls 查询指定交易池。
• 同时比较成交量与流动性；高成交量本身不代表足够交易深度。

做定期监控时，固定使用规范 ID 或 ticker，并保存更新时间。跨链或跨市场比较时，不要只依赖显示名称。

MCP 与 API

将支持 MCP 的客户端连接到 Apify 托管 MCP 服务 mcp.apify.com，完成 Apify 授权后即可搜索并运行 Actor、读取数据集。MCP 权限沿用 Apify 账户权限。

脚本可通过 Apify API 调用 Actor。请将 API token 保存在本地环境变量中。

curl -X POST "https://api.apify.com/v2/acts/myagizm~dexscreener-scraper/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"queries":["SOL"],"maxItems":3}'

异步运行使用 /runs 接口；完成后通过 defaultDatasetId 读取数据集：

curl -X POST "https://api.apify.com/v2/acts/myagizm~dexscreener-scraper/runs?token=$APIFY_TOKEN"
curl "https://api.apify.com/v2/datasets/$DATASET_ID/items?clean=true&format=json&token=$APIFY_TOKEN"

不要把 token 放入 Actor 输入、数据集或 issue。

常见问题

一条结果代表什么？

一行数据对应一个规范化的 DEX 交易对，由 chainId 和 pairAddress 共同标识。状态消息、失败查询和没有有效结果的运行不会生成按条计费的数据行。

这是数据平台的官方产品吗？

不是。这是一个独立的 Apify Actor，读取公开市场数据。CoinGecko、DexScreener、Polymarket 和 Kalshi 保留其名称、网站和数据的所有权。

需要 API 密钥、Cookie 或平台账号吗？

不需要提供第三方平台的密钥、登录信息、Cookie 或浏览器会话。运行 Actor、查看数据集仍需要 Apify 账户。

数据有多新？

Actor 在运行时请求公开接口。上游响应、保存数据行和稍后导出的时刻可能不同。每行是带更新时间的快照，不是实时行情流。

会返回历史价格吗？

不会。本 Actor 返回所支持接口提供的公开市场快照，不会生成历史价格、K 线或逐笔订单簿。

为什么有些字段为 null 或 0？

上游并非对每条记录都提供所有字段。来源明确给出 0 时会保留 0；没有可用数据时为 null。README 字段表区分必填输出和可选字段。

为什么一个搜索词会返回多行？

同一关键词可能匹配多种币、交易对、事件或结果市场。Actor 按来源记录 ID 去重，并在规范化后应用 maxItems 上限。

输入无效时会怎样？

输入错误会以 SUCCEEDED 状态结束，不产生结果且无按结果费用；请查看 OUTPUT 了解原因。传输错误和未分类的空响应仍为失败，不产生结果行费用。

输入格式正确但仍然没有结果，为什么？

文本可能有效，但在当前接口或状态筛选下没有公开匹配项。请尝试来源平台的规范 ID 或 ticker，并检查市场状态。

maxItems 控制什么？

maxItems 是一次运行最多写入的数据行数，不保证上游一定有这么多匹配记录。

为什么价格可能和交易页面不同？

Actor 读取公开数据接口。页面可能刷新时间不同、筛选不同，或显示实时订单簿。结果是参考快照，不是可执行的交易报价。

Actor 会下单吗？

不会。它只读取公开市场数据并写入默认数据集，不连接钱包、不提交订单、不转移资金，也不管理持仓。

可以导出数据吗？

可以。Apify 数据集支持 JSON、CSV、Excel、XML 等格式。数据集视图提供常用平铺字段，默认数据集保留完整结构。

可以定时运行吗？

可以。在 Apify Console 创建计划任务或调用 API。轮询间隔应符合上游更新节奏；更频繁地请求不会让缓存数据更实时。

可以从代码调用吗？

可以。使用自己的 Apify API token 发送 JSON 输入，并读取运行的默认数据集。README 提供同步运行、异步运行和读取数据集的示例。

AI agent 可以通过 MCP 调用吗？

可以。将 MCP 客户端连接至 Apify 托管 MCP 服务，并通过 Apify 完成授权，再从 Store 或 Actor 工具列表中调用本 Actor。权限来自你的 Apify 账户。

计费方式是什么？

Actor 使用 PAY_PER_EVENT，只对写入默认数据集的有效结果行收费。运行平台资源费用可能按你的 Apify 计划另行计算；大批量运行前请查看运行与价格面板。

为什么有最低运行预算？

PPE 运行可能显示最低消费上限，即使单行价格很低。该上限是运行预算限制，不是额外的每行费用。API 调用可通过 maxTotalChargeUsd 设置硬上限。

一次可以提交多个输入吗？

可以，但需遵守输入数组上限。建议先用较小的 maxItems 检查字段，再根据上游响应和预算提高上限。

超时或上游临时错误后该怎么办？

稍后使用相同输入和合理的 maxItems 重试。反复重试无法消除服务故障，即使没有结果也可能消耗平台运行时间。

结果属于投资建议吗？

不属于。数据可用于研究、监控和软件工作流，不建议买入或卖出，也不保证价格、成交量或概率保持不变。

会访问私人或受限制的数据吗？

不会。Actor 使用无需认证的公开市场接口，不绕过登录、付费墙、私人账户或访问控制。

怎样报告字段错误或上游变更？

请在 Actor 的 Issues 页面提供输入结构、大致运行时间、run ID 和有问题的字段。不要在 issue 中粘贴 Apify API token 或其他凭据。

可以在商业仪表板中使用数据吗？

可以按 Apify 条款和数据提供方条款使用输出。具体用途的权利与义务由使用者自行确认。

为什么会有多个标题相似的市场行？

一个预测事件可以包含多个结果市场；一个代币也可以在多条链或多个交易对中交易。记录 ID 和合约、市场标识符用于区分这些行。

所有字段都保证有值吗？

不保证。上游提供的可选字段会保留；来源缺失时为 null。只有“始终返回”部分列出的必需字段用于判断结果行是否有效。

空数据集是否说明资产不存在？

不一定。输入可能与接口不匹配、记录不在所选状态，或上游发生临时故障。请先检查输入格式和运行说明。

样例数据是否保证报价有效？

不保证。样例只展示一次真实响应的输出结构，不构成报价承诺、交易要约或未来可用性的保证。

可以只输入 ticker 而不输入 ID 吗？

queries 接受 SOL、ETH 等代币符号；tokenAddresses 用于合约地址，pairUrls 用于已知交易池。符号并不唯一，请核对返回的链和地址。

为什么默认输入只取少量结果？

预填输入故意设置得较小，便于先检查真实记录和价格字段，再提高 maxItems。小批量运行也更容易发现币种 ID、链地址、series ticker 或查询词是否写错。

可以保留完整的嵌套数据吗？

可以。表格视图展示常用平铺列，默认数据集保留完整规范化 JSON 行，包括来源提供的数组和嵌套对象。

Actor 会改写来源数值吗？

不会。Actor 会规范字段名和数字类型，不会计算虚构价格或预测结果。直接来自来源的字段会由 sourceType 和来源 URL 标识。

如果上游接口改了响应会怎样？

Actor 会在保存前检查必需业务字段。若必需字段消失，运行不会悄悄保存空的成功结果。请在 Issues 页面提供 run ID 和发生变化的字段，以便对照新响应检查映射。

可以输入其他服务的 API token 吗？

该输入不接受也不需要第三方 token。不要把密钥粘贴到输入中。Actor 使用公开接口，并把结果写入你的 Apify 数据集。

市场价格保证可以成交吗？

不保证。公开市场快照可能延迟、缓存或不完整，与交易所订单簿不同。它不是订单、成交价保证或投资建议。

可以筛选或转换导出数据吗？

可以。使用数据集视图中的顶层字段，在 Apify 界面筛选或下载 JSON/CSV。也可在下游转换输出，同时保留来源记录标识符。

如何处理重复记录？

核心会在一次运行内按来源标识符去重。不同运行是独立快照，同一个仍然存在的市场或交易对可能再次出现。

可以一次请求所有市场吗？

Actor 对 maxItems 和请求数设有上限。需要更广覆盖时，可使用 series、tag 或多个小型计划运行，而不要假设单页就是完整市场目录。

这能替代来源平台的 API 吗？

这是方便的 Apify 接口和数据集流程，不承诺更广覆盖，也不替代平台文档。需要核验记录时，请使用每行的来源标识符和公开 API URL。

无结果不计费是什么意思？

PPE 按成功写入数据集的结果行计费。输入或上游查询没有有效记录时，桥接层会在写入前失败。因此无行的无效控制不会产生默认数据集 item 事件。

相关搜索

DexScreener 新交易对 · DexScreener API 查询 · Solana 代币交易对流动性 · DEX 交易对价格和成交量 · 代币合约地址交易对查询 · 以太坊 DEX 市场数据 · Base 链交易对数据 · 加密货币流动性数据 · DEX 买入卖出次数 · 交易对地址数据集 · 多链代币价格快照 · DexScreener CSV 导出 · 代币 FDV 市值查询 · 流动性监控 API · DEX pair 数据抓取

免责声明

本 Actor 是独立的数据工具，与数据来源平台没有隶属或背书关系。输出仅供参考，可能延迟、不完整、被更正或暂时不可用，不构成投资、法律、税务或财务建议。你需要自行确认数据使用适用的条款和法律。

资源

• Apify API v2
• Apify MCP server
• Apify 数据集
• Apify 计划任务
• 发布者主页
• 支持：请在 Actor Issues 页面提供 run ID、输入结构和需要核对的字段。

运行说明

搜索词和直接标识符怎样选择？

已知稳定标识符时优先使用它。查询 DexScreener public DEX pair snapshots 时，关键词适合发现记录，来源 ID 或 ticker 更适合可重复查询。每个输入选项的格式见表单说明。

首次运行适合取多少行？

预填输入使用较小的 maxItems。先用该值检查实时 DexScreener public DEX pair snapshots 字段，再确认数据和费用符合工作流后提高上限。

哪些字段适合作为连接键？

使用来源标识符字段，不要只用显示标题。名称和标题可能变化；ID、ticker、合约地址或 condition ID 用于标识底层记录。

可以持续运行吗？

可以在 Apify 中安排重复运行，但每次运行都是单独快照。间隔应符合来源更新频率和监控需求；更快轮询不会让上游数据自动变新。

需要未列出的字段怎么办？

先检查默认数据集完整行，并确认所选记录的来源是否返回该字段。如果公开接口稳定提供且字段对工作流很重要，请在 issue 中附上 run ID 和来源记录标识符。

失败查询怎样处理？

失败查询不会变成伪造数据行。桥接层在写入前检查必需的 DEX 交易对 字段；没有有效行时运行失败，不产生结果行费用。

如何比较两个快照？

按来源标识符比较，并保留运行时间。价格和成交量会变化，因此值发生变化可能是市场变动，而非解析错误。

这会返回完整目录吗？

单次请求不保证覆盖来源平台完整目录。Actor 用有界分页、筛选器和 maxItems 控制运行规模。覆盖范围请以来源平台目录文档为准。

可以与同事共享数据集吗？

可以通过 Apify 数据集权限共享，或导出文件。导出内容是特定时刻的快照，建议保留来源记录标识符。

source URL 有什么用途？

Actor 能构造或核验时会提供公开记录/API 链接，便于检查。链接不保证永久可用，也不保证之后页面仍显示相同数据。

HTTP 成功为什么仍可能没有有效行？

HTTP 成功只代表收到响应。Actor 还会检查必需业务字段和类型。挑战页、无关对象或空载荷都不是有效的 DEX 交易对 记录。

可以在不同运行中更改结果上限吗？

可以，maxItems 是运行输入。较小上限减少保存量；较大上限仍受输入 schema 和上游请求限制约束。

Errors & billing

Input errors finish with status SUCCEEDED, no results and no charge; see the OUTPUT record for the reason.

错误与计费

输入错误会以 SUCCEEDED 状态结束，不产生结果且不收费；原因请查看 OUTPUT 记录。

Search specificity

Ticker searches can return wrapped tokens or matching names on other chains. The SOL example currently includes a Base-chain pool; it is not a Solana-only filter. Use chainId plus pairAddress for deduplication and pairUrls for exact pools.

查询精度

符号搜索可能返回其他链上的包装代币或同名代币。例如 SOL 样例包含 Base 链交易池，并不等于仅筛选 Solana。请用 chainId 与 pairAddress 联合去重；精确交易池查询使用 pairUrls。