RugMaps
RugMaps maps wallets, entities, and money flows. It answers the forensic questions a price chart never will: who deployed this token, who funded them, and are the holders coordinated?
Open it in the app at rugmunch.io/rugmaps, or
call the API directly. Every endpoint below is live on
https://rugmunch.io/api/v1.
โ Live-platform facts on this page verified against production on 2026-08-24.
What it doesโ
| Capability | Question it answers |
|---|---|
| Wallet maps | What does the transaction graph around this token/wallet look like? |
| Entity resolution | Which known entity (exchange, fund, deployer) is behind this address? |
| Fund-flow tracing | Where did the money come from โ and where did it go? |
| Holder graphs | Who holds the token and how are their wallets connected? |
| Cluster analysis | Are supposedly independent holders actually one actor? |
| Anomaly detection | Does the contract show abnormal or exploitative behavior patterns? |
| Auto-labeling | Can we label unknown wallets automatically from clustering? |
API endpointsโ
| Method & path | Purpose |
|---|---|
POST /api/v1/rugmaps/map | Generate the rug map for a token/wallet (nodes + edges) |
GET /api/v1/rugmaps/analyze/{address} | Wallet analysis summary |
GET /api/v1/rugmaps/entity/{address} | Entity resolution for an address |
GET /api/v1/rugmaps/fund-flows | Fund-flow tracing between wallets |
GET /api/v1/rugmaps/token-graph | Token holder graph |
POST /api/v1/rugmaps/cluster-analysis | AI holder cluster analysis |
POST /api/v1/rugmaps/anomaly-detection | AI contract anomaly detection |
POST /api/v1/rugmaps/auto-label | Auto-label wallets via clustering |
GET /api/v1/rugmaps/auto-label/stats | Auto-labeler statistics |
GET /api/v1/rugmaps/wallet-labels | Batch label lookup (see Wallet Intelligence) |
GET /api/v1/rugmaps/health, /ai-health | Service + AI-subsystem health |
Examplesโ
# Generate the map for a token
curl -X POST https://rugmunch.io/api/v1/rugmaps/map \
-H "Content-Type: application/json" \
-d '{"address": "0xTokenAddress", "chain": "ethereum", "depth": 2}'
# Trace where money flowed
curl "https://rugmunch.io/api/v1/rugmaps/fund-flows?address=0xAddress&chain=ethereum"
# Resolve an address to its known entity
curl https://rugmunch.io/api/v1/rugmaps/entity/0xAddress
# AI cluster analysis of holders
curl -X POST https://rugmunch.io/api/v1/rugmaps/cluster-analysis \
-H "Content-Type: application/json" \
-d '{"address": "0xTokenAddress", "chain": "ethereum"}'
The classic rug signatureโ
A typical investigation flows: entity/{address} โ fund-flows โ
cluster-analysis โ auto-label. The pattern that falls out again and again:
A fresh deployer wallet, funded by a funder that also funded five other launches, whose "independent" top holders all bought in the same blocks and all route withdrawals back to one consolidation wallet.
No single-token scanner catches that alone โ it is a graph property, which is exactly what RugMaps exposes.
Pairing with RugChartsโ
RugCharts tells you when something is happening; RugMaps tells you who. A
whale_sell signal plus a fund-flows trace to the deployer is a much
stronger exit signal than either alone โ see
RugCharts.
From an AI agentโ
Both engines are reachable through the MCP server (analytics_query,
get_wallet_analysis) โ see MCP Setup.
Pricingโ
Map generation, entity lookups, and basic labels are trial-eligible. Cluster forensics and AI analysis are paid x402 tools โ see x402 Payments for live per-call pricing.