GMX Arbitrum Stats Scraper

GMX Arbitrum Stats Scraper

Scrape GMX trading stats from Arbitrum, including volume, fees, open interest, and liquidity, up to a million records per run. Every record comes with token-level detail, timestamp, and computed metrics. No API key required. Export to CSV, JSON, Excel, or XML.

GMX's on-chain data is spread across multiple contracts and subgraphs, making it difficult to aggregate trading stats for analysis. This scraper reads the public GMX Arbitrum stats feeds directly, filtering by token, and returns each match in one fixed schema. Get a clean, analysis-ready dataset of protocol performance without writing complex GraphQL queries.

Who uses it	What they scrape GMX Arbitrum for
DeFi analysts	Track protocol revenue and trading volume trends over time.
Crypto traders	Monitor open interest and liquidity shifts for specific tokens.
Protocol researchers	Compare GMX Arbitrum performance against other perpetual DEXs.
Data journalists	Source on-chain metrics for DeFi market reports and articles.

What it does

This Actor collects GMX Arbitrum trading statistics by token and returns each record as a flat row.

• 📊 Token-level filtering: Focus on specific tokens like BTC, ETH, or ARB, or pull all available stats.
• ⏱️ Time-series ready: Each record includes a timestamp for building historical performance charts.
• 📈 Computed metrics: Volume, fees, open interest, and liquidity are returned in a structured format.
• 🔄 Scheduled monitoring: Set up recurring runs to build a continuous dataset of protocol health.

Results export to CSV, JSON, Excel, or XML, or straight from the API.

What you can do with GMX Arbitrum data

📈 Monitor protocol revenue.

A DeFi analyst runs the scraper daily to track GMX Arbitrum's fee generation and volume trends, informing investment decisions.

💧 Analyze liquidity depth.

A trader filters for ETH and BTC stats to assess liquidity conditions before opening a large position on GMX.

📊 Build a performance dashboard.

A data engineer schedules the scraper to feed a live dashboard comparing GMX Arbitrum's open interest against other perpetual exchanges.

📝 Source data for a research report.

A journalist collects a month of token-level stats to write an article on Arbitrum's DeFi ecosystem growth.

Why choose this scraper

	What you get
No API key needed	Access public GMX Arbitrum data without registration or rate limits.
Structured output	Get a clean, flat schema ready for CSV, JSON, Excel, or XML export.
Token filtering	Narrow results to specific assets like BTC, ETH, or ARB.
Scalable collection	Collect up to a million records per run for deep historical analysis.

How it compares

No other Store actor targets GMX Arbitrum the same way, so the honest comparison is with the alternatives teams actually weigh.

	GMX Arbitrum Stats Scraper	Build it in-house	By hand
Setup	Run it now, zero config	Days of engineering	None, but hours per pull
When GMX Arbitrum changes	Maintained for you	You fix it	You re-learn the page
Proxies, retries, anti-bot	Built in	Your problem	Browser only
Output	Fixed JSON schema, CSV/Excel export	Whatever you build	Copy-paste
Cost	Pay per result	Engineering time	Analyst hours

Configure the run

Drive the Actor with a maximum record count and an optional comma-separated token filter, so only the stats you need reach your dataset. The Input tab lists every parameter.

A first run with the defaults:

{
  "maxItems": 10
}

A larger pull:

{
  "maxItems": 200
}

Free users

Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.

Run it

1. Create a free Apify account with $5 in credit.
2. Open the GMX Arbitrum Stats Scraper.
3. Set your inputs and any filters, then click Start.
4. Export the results as CSV, Excel, JSON, or XML from the Dataset tab.

Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.

Use with AI agents (MCP)

Give an AI agent live access to GMX Arbitrum through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:

claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/gmx-arbitrum-stats-scraper"

Then prompt it in plain language to run the scraper and read back the results.

Troubleshooting

Why am I getting no results?

Check your token filter spelling. Token symbols are case-sensitive and must match exactly, for example, BTC not btc. Also, try increasing the maxItems value.

The run failed with an error.

This is often a temporary network issue. Retry the run. If the problem persists, check the Apify platform status or the actor's run log for specific error messages.

My dataset has fewer records than the maxItems I set.

The scraper collects only the records available at the time of the run. If the source has fewer data points than your maxItems setting, you will receive all available records.

Can I get real-time streaming data?

This actor is designed for batch collection. For near real-time updates, schedule the actor to run at a very high frequency, such as every minute.

FAQ

Question	Answer
What data does this scraper collect from GMX Arbitrum?	It collects trading statistics such as volume, fees, open interest, and liquidity, broken down by token and timestamp.
Do I need an API key or wallet connection to use this?	No. The scraper reads publicly available data feeds and requires no API key, wallet connection, or registration.
Can I filter stats for a specific token like ARB or ETH?	Yes. Use the optional token filter input to specify one or more tokens as a comma-separated list, for example, BTC,ETH,ARB.
How many records can I collect in one run?	You can set the maximum records from 1 up to 1,000,000 per run, depending on your data needs.
What format is the exported data in?	The data can be exported to CSV, JSON, Excel, or XML, making it easy to use in spreadsheets, databases, or analytics tools.
Is this for GMX on Arbitrum only, or does it support Avalanche?	This scraper is specifically for the GMX deployment on Arbitrum. It does not collect stats from the Avalanche deployment.
Can I schedule this scraper to run automatically?	Yes. You can set up recurring runs on Apify to collect data at regular intervals, building a historical dataset over time.
What is the difference between this and querying a subgraph directly?	This scraper handles the aggregation and returns a flat, structured dataset without requiring you to write or maintain GraphQL queries.
Does this scraper collect individual trade data?	No. It collects aggregated trading statistics, not individual trade-level data.

🆘 Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.

⚠️ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by GMX. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.