--:--:--LOCAL ·--:--UTC
    MKT CAP$2.03T-5.5%
    24H VOL$246.3B
    BTC DOM57.4%
    HEALTH21BEARISH
    FEAR/GREED10
    SHORT-TERM25BEARISH
    LONG-TERM17BEARISH
    OI$10.1B
    BTC FUND+0.002%
    24H LIQ$123M
    LONG/SHORT71.9% / 28.1%
    REGIME (LT)ESTABLISHED BEAR MARKET
    REGIME (ST)VOLATILITY SPIKE
    HL OI$5.6B
    WHALESSHORT 41.9%
    MKT CAP$2.03T-5.5%
    24H VOL$246.3B
    BTC DOM57.4%
    HEALTH21BEARISH
    FEAR/GREED10
    SHORT-TERM25BEARISH
    LONG-TERM17BEARISH
    OI$10.1B
    BTC FUND+0.002%
    24H LIQ$123M
    LONG/SHORT71.9% / 28.1%
    REGIME (LT)ESTABLISHED BEAR MARKET
    REGIME (ST)VOLATILITY SPIKE
    HL OI$5.6B
    WHALESSHORT 41.9%
    Plug real-time crypto data into your AI agent — one command: Get your free API key →
    LoginGet API Key

    MemeCoreM

    Rank #44 LIVE Website X.com
    $0.7754
    24h -7.21% 7d -7.50% 30d -1.94%
    MARKET CAP
    $1.78B
    Rank #44 by market cap
    24H VOLUME
    $3.06M
    spot · all venues
    CIRCULATING SUPPLY
    2,300,177,912 M
    max 10,000,000,000
    ALL-TIME HIGH
    $5.64
    -86.26% from ATH · 2026-07-02
    MemeCore Price LIVE
    curl -H "X-API-Key: cdk_live_…" \
      "https://cryptodataapi.com/api/v1/market-data/klines?symbol=MUSDT&interval=1d&limit=90"
    WEBSITE PREVIEW Full signal detail is free on every coin page for now. Page data is ~30-min delayed — the API is real-time.
    Live market data & quant signals for M
    Event & Security Catalysts · M
    Token Unlock in 11d
    M $34.5M
    2026-12-02 · 1.93% of float ecosystem
    Dated events on M's forward calendar. Unlock size is measured against circulating float — the full schedule is on token unlocks. Net bias neutral.

    Scheduled and unscheduled catalysts for this coin: news scored for real price impact, security incidents, and upcoming token unlocks that add supply.

    Market-Moving News & Events →

    Things that could move the price: news, security problems, and token unlocks — dates when a batch of new coins is released to early investors and team members, adding to the supply. An empty panel genuinely means nothing is scheduled, rather than data failing to load.

    This feeds event-driven and catalyst trading. Token unlocks support a supply-shock trade — the size and date are public, so the weakness often arrives before the unlock rather than on it. Scheduled news drives the buy-the-rumour, sell-the-news pattern, where the move happens into the announcement and reverses on it.

    Prompt — have an agent design a new strategy on this metric
    Design a new event-driven strategy for M using /api/v1/event/regime/M and the unlock schedule. The rules must be executable in advance — no reacting to news after the fact — so define how many days before a catalyst you act and what closes the position. Validate on /api/v1/backtesting/news-events and /api/v1/backtesting/snapshots?data_type=token_unlocks, and be explicit about any lookahead you had to avoid.

    /backtesting/news-events is the archived catalyst tape with the same scoring you see here. Token unlocks have their own snapshot type, /backtesting/snapshots?data_type=token_unlocks, which matters because unlock dates are known ahead of time and are therefore testable without lookahead.

    Prompt — paste into any agent connected to the MCP server
    Using CryptoDataAPI, test how M trades around scheduled catalysts. Pull /api/v1/backtesting/news-events and /api/v1/backtesting/snapshots?data_type=token_unlocks, then measure returns from 7 days before each unlock to 7 days after, using price bars from /api/v1/backtesting/klines. Report whether weakness arrived before or on the date, and whether unlock size relative to float predicted the size of the move.
    curl -H "X-API-Key: cdk_live_…"   "https://cryptodataapi.com/api/v1/event/regime/M"
    24h Liquidations · M
    100.0%LONGS
    0.0%SHORTS
    $4.6K longs— shorts
    Total (24h)$4.6K

    Positions force-closed in this coin over the last 24 hours, split by side. A long liquidation is forced selling; a short liquidation is forced buying.

    Crypto Liquidations →

    A liquidation is a trader being forced out of a bet because the price moved too far against them. Longs being liquidated means forced selling; shorts being liquidated means forced buying. Judge the size against what is normal for this coin: $5M is enormous for a small coin and barely noticeable for Bitcoin.

    Liquidation-cascade fades are built on this: forced selling overshoots, so the sharpest bounces tend to follow the biggest one-sided prints. Long and short squeeze plays work the same mechanism in reverse, and stop-hunt reversals look for price being pushed into a cluster of stops precisely to trigger them.

    Prompt — have an agent design a new strategy on this metric
    Design a new strategy for M that trades around forced liquidations, using /api/v1/market-intelligence/liquidations?symbol=M live. Define what counts as a cascade, which side you take, how quickly you exit, and how you avoid being liquidated yourself. Validate on the per-event tape at /api/v1/backtesting/hl-liquidations plus /api/v1/backtesting/klines, and report the worst single loss, not just the average.

    /backtesting/liquidations gives the aggregated series, and /backtesting/hl-liquidations gives the exact per-event Hyperliquid tape — every individual fill, with its venue. For the price levels where liquidations cluster, use /backtesting/snapshots?data_type=liquidation_map.

    Prompt — paste into any agent connected to the MCP server
    Using CryptoDataAPI, backtest the liquidation-cascade fade on M. Pull the per-event tape from /api/v1/backtesting/hl-liquidations and price bars from /api/v1/backtesting/klines. Define a cascade as a 5-minute bucket in the top 1% of one-sided liquidation size, then measure forward returns at 15m, 1h and 4h from taking the opposite side. Charge taker fees and report the hit rate and worst loss.
    Free
    curl -H "X-API-Key: cdk_live_…"   "https://cryptodataapi.com/api/v1/market-intelligence/liquidations?symbol=M"
    Related coins

    Every metric on this page is one API call away

    MemeCore price, derivatives, on-chain flows and quant regimes — plus 180+ endpoints across the whole market. The free tier is real: 1,000 requests/day, no card required.

    GET/api/v1/coins/M· Free
    GET/api/v1/market-data/klines?symbol=MUSDT· Free
    GET/api/v1/market-intelligence/liquidations?symbol=M· Free
    GET/api/v1/backtesting/klines?symbol=M&interval=1h· Pro Plus
    GET/api/v1/backtesting/funding?symbol=M· Pro Plus
    GET/api/v1/backtesting/daily-snapshots/2026-08-01· Pro Plus
    GET/api/v1/backtesting/hl-liquidations?coin=M· Pro Plus
    GET/api/v1/quant/regimes/history· Pro Plus
    GET/api/v1/backtesting/archives/index· Pro Plus
    MCP-native · works in Claude & Cursor

    Quick Start for AI Agents

    Add the MCP server in one line — then your agent answers crypto questions by calling the API for you. No endpoints to wire up, no keys to juggle. Just ask.

    Claude · cryptodataapi connected
    What regime is crypto in right now, and does the short-term quant model agree?
    On it — checking the cycle regime and the 24h quant model.
    ⚙GET/regimes/current
    ⚙GET/quant/market?horizon=24h
    The cycle regime is Established Bear Market. The 24h quant HMM reads Volatility Spike. The 24h model sees a volatility spike, so expect fast moves both ways and widen stops.
    Where are the Hyperliquid whales positioned, and which strategy fits this regime?
    ⚙GET/quant/whales
    ⚙GET/strategies/post-liquidation-rebound
    Whales (every ≥$100k Hyperliquid account) are 42% long, net short. Post-Liquidation Rebound fits: it enters after a liquidation flush has cleared out the over-levered positions. Want me to backtest it on 90 days of Hyperliquid data?
    Add it in one line
    setup cryptodataapi-mcp
    Cursor? Same command — paste it into the MCP settings.
    1
    Connect
    Registers with Claude or Cursor instantly. Free API key created on sign-up.
    2
    Ask in plain English
    Describe the data you want — no endpoints to recall, no params to format.
    3
    Get live JSON back
    The agent picks the endpoint, calls it, and returns clean structured data.
    190+ endpoints across 20+ data groups
    Read the full quickstart →