CoinMarketCap Community (Gravity) Scraper — Posts, Profiles, Trending (Unofficial)

Scrape CoinMarketCap Community (Gravity) — author posts, user profiles, and a coin's top trending posts. Run the actor with a small JSON input, get clean, structured JSON back in the run's dataset (and OUTPUT), ready to store in your own database or pipeline. Use Apify Proxy or your own (datacenter is fine).

One run fetches one thing, chosen by the mode field:

• post-stats — an author's recent posts (likes, comments, reposts, impressions, reactions, topics, sentiment…).
• profile-stats — a user profile (followers, following, bio, verification, numeric guid, mindshare…).
• top-posts — the top trending posts for any coin, ranked by trending score.

⚠️ Unofficial. This scraper is not affiliated with, endorsed by, or sponsored by CoinMarketCap. All trademarks are the property of their respective owners.

Use cases

• Crypto influencer / KOL tracking — monitor what top CoinMarketCap Community accounts post and how their audience reacts.
• Mindshare & sentiment — pull follower counts, mindshare and post sentiment to track narratives around a coin.
• Trending research — grab the top posts for BTC, ETH, SOL or any coin to see what's driving attention right now.
• Datasets & dashboards — export the JSON into your own crawler pipeline, spreadsheet, database or BI dashboard.

How to run it

Start the actor with an input JSON — from the Apify Console (Input tab), the API, a schedule, or an integration (Make.com, n8n, Zapier…).

{ "mode": "profile-stats", "handle": "goonrich" }

• Async: POST /v2/acts/<actor>/runs → the run finishes → read its dataset (one item) or OUTPUT record.
• Synchronous: POST /v2/acts/<actor>/run-sync-get-dataset-items waits for the run and returns the dataset items directly in the response — handy for Make.com / code that wants the data back in one call.

Results land in the run's dataset — one row per result (each post, or the single profile). Every row includes fetchedAt (ISO / UTC).

Modes & parameters

mode: "post-stats" — an author's recent posts

Param	Required	Default	Notes
handle	yes	—	Gravity user handle — same as the username (the account's @name), with or without @.
limit	no	10	How many recent posts to return (max 100).
proxyConfiguration	no	—	Proxy (Apify Proxy or your own) — see below.

{ "mode": "post-stats", "handle": "goonrich", "limit": 25 }

Dataset: one row per post — each post as CoinMarketCap returns it, with its own owner and fetchedAt.

mode: "profile-stats" — a user profile

Param	Required	Notes
handle	yes	Gravity user handle — same as the username (the account's @name).
proxyConfiguration	no	Proxy (Apify Proxy or your own) — see below.

{ "mode": "profile-stats", "handle": "goonrich" }

Dataset: one row — the profile object (followers, guid, mindshare, …) plus fetchedAt.

mode: "top-posts" — top trending posts for a coin

Already ranked — the top N are the first N.

Param	Required	Default	Notes
coin	yes	—	The coin's CMC slug (e.g. bitcoin, pepe).
limit	no	10	How many top posts to return (max 100).
proxyConfiguration	no	—	Proxy (Apify Proxy or your own) — see below.

How to find the slug: open the coin's page on CoinMarketCap and take the last part of the URL. For example https://coinmarketcap.com/currencies/pepe/ → the slug is pepe. (Tickers like BTC are not used — many coins share a ticker; the slug is unique.)

{ "mode": "top-posts", "coin": "pepe", "limit": 20 }

Dataset: one row per post, each with its author (owner) and fetchedAt, ranked (row 1 = top).

Output

Results go to the run's dataset — one row per result (each post, or the single profile). A short summary (mode, count) is stored in the run's OUTPUT record. Fetch rows via the Apify API or run-sync-get-dataset-items, or export to CSV / JSON / Excel from the dataset.

Startup

Each run starts a fresh container, so it takes a few seconds to boot before it answers. Runs are lightweight (no browser), so they're quick and cheap.

Clean JSON, fields returned as-is

The scraper returns the CoinMarketCap fields unchanged — it does not rename or drop useful data, so new fields keep coming through. It only selects the relevant part of the response and adds fetchedAt. Easy to export to JSON, a dataset, or straight into your own pipeline.

Proxies

Configure proxies with the standard Proxy input — use Apify Proxy or your own proxy URLs (datacenter is fine). The actor rotates across them and skips dead ones. Optional: without a proxy, requests go out directly (fine for most cases — the token is not IP-bound).

Apify Proxy:

{ "mode": "top-posts", "coin": "pepe", "proxyConfiguration": { "useApifyProxy": true } }

Your own proxies:

{ "proxyConfiguration": { "useApifyProxy": false, "proxyUrls": ["http://user:pass@host:port"] } }

Pricing

Pay-per-event — you only pay per successful call:

Mode	Price
post-stats	$4 / 1000 queries
profile-stats	$4 / 1000 queries
top-posts	$10 / 1000 posts returned

Free plan: 20 runs per account to try it out; after that you'll get an "upgrade" result. Paid plans are unlimited.

Notes

• Data comes from a public social platform; profile data may be personal data — handle it in line with your local regulations (e.g. GDPR).
• Scraping may be restricted by CoinMarketCap's Terms of Service. Use responsibly and at your own risk.

---

This is an unofficial tool and is not affiliated with, endorsed by, or sponsored by CoinMarketCap. All trademarks are the property of their respective owners.