PoofBit API

Use the Poof Chaos Index and the Poof Index in your bots, dashboards and AI agents.

The Poof Chaos Index (PCI) is a market-wide, direction-neutral measure of turbulence from 0 to 100, computed from public market data. It is designed to be read next to Fear & Greed: sentiment tells you which way the crowd leans, PCI tells you how violently the market is moving.

The Poof Index assesses single coins from 11 to 111: the higher, the deeper the coin is in a poof state. Everything is available as JSON over HTTPS and as tools for AI agents over MCP.

Get an API key

Free and instant. Every request to /api/* and /mcp needs a key. Need higher limits? Create an account to get account tokens (120/min) and a watchlist.

Quick start

Plain JSON over HTTPS. Put your key in an environment variable and send it as a Bearer token:

export POOFBIT_KEY=pb_your_key_here
curl -H "Authorization: Bearer $POOFBIT_KEY" https://poofbit.com/api/pci

Authentication

Send your key with every request, in either header:

• Authorization: Bearer YOUR_KEY (preferred)
• X-API-Key: YOUR_KEY

Keys are never accepted in the URL, because URLs end up in logs and browser history. We store only a hash of your key, so a lost key can't be recovered: create a new one.

A missing, unknown or revoked key returns 401 with a WWW-Authenticate: Bearer header:

{ "error": "Missing or invalid API key", "docs": "https://poofbit.com/docs#authentication" }

Going over the rate limit returns 429.

Free vs account

Account tokens look and work exactly like API keys (same headers). Limits count per key; days are UTC. Every keyed response tells you where you stand:

• X-RateLimit-Limit: requests allowed per minute for this key.
• X-RateLimit-Remaining: requests left in the current minute.
• X-RateLimit-Tier: free or account.

GET /api/pci

Returns the current Poof Chaos Index with its zone, the weighted components, the Fear & Greed reading, the combined quadrant, the daily history and the Global Poof Index.

Example response:

{
  "pci": 34,
  "zone": { "key": "choppy", "name": "Choppy Waters", "emoji": "🌊" },
  "components": [
    { "key": "volatility", "label": "Volatility", "weight": 0.3, "risk": 0.31, "detail": "Median daily swing ≈ 3.6%" },
    { "key": "breadth", "label": "Breadth of big moves", "weight": 0.2, "risk": 0.26, "detail": "13 of 50 coins moved more than 5%" },
    { "key": "dispersion", "label": "Dispersion", "weight": 0.15, "risk": 0.4, "detail": "Spread of 24h moves 3.1%" },
    { "key": "swing", "label": "Market cap swing", "weight": 0.15, "risk": 0.22, "detail": "Top 48 market cap +1.1% in 24h" },
    { "key": "volume", "label": "Volume surge", "weight": 0.1, "risk": 0.45, "detail": "24h volume is 2.6% of the top 48 market cap" },
    { "key": "mania", "label": "Memecoin mania", "weight": 0.1, "risk": 0.52, "detail": "Trending coins average Poof Index 52" }
  ],
  "fear_greed": { "value": 59, "classification": "Greed" },
  "quadrant": { "key": "calm-greed", "emoji": "😌", "name": "Calm Greed", "text": "Complacency mode. The quiet before the poof." },
  "history": [
    { "date": "2026-10-07", "pci": 29, "source": "reconstructed" },
    { "date": "2026-10-08", "pci": 31, "source": "live" },
    { "date": "2026-10-09", "pci": 34, "source": "live" }
  ],
  "history_days": 3,
  "stale": false,
  "updated_at": "2026-10-09T12:00:00+00:00",
  "methodology": "v2",
  "gpci": { "value": 24, "zone": { "key": "sus", "name": "Slightly Sus", "emoji": "🤨" }, "share_in_poof": 0.08 }
}

GET /api/coins

Coins with their Poof Index, filtered, sorted and paged like the Poof Index table: the same parameters, the same result. Invalid parameter values fall back to the defaults (never an error). Repeat a parameter to pass several values.

curl -H "Authorization: Bearer $POOFBIT_KEY" "https://poofbit.com/api/coins?tab=all&zone=red&zone=poof&futures=1&sort=mcap&per_page=25"

Example response (one coin shown):

{
  "coins": [
    {
      "id": "bitcoin", "name": "Bitcoin", "symbol": "BTC",
      "price": 65000.0, "market_cap": 1300000000000, "rank": 1, "change_24h": 1.0,
      "poof": 14, "change_7d": 2.1, "has_futures": true, "flags": [], "market_beta": 1.0,
      "zone": { "key": "solid", "name": "Boringly Solid", "emoji": "🧱" },
      "components": [
        { "key": "vol30", "label": "30-day volatility", "value": 0.021, "contribution": -0.32 },
        { "key": "dd90", "label": "Drop from 90-day high", "value": 0.08, "contribution": -0.72 }
      ]
    }
  ],
  "tab": "all", "sort": "mcap", "dir": "desc",
  "page": 1, "per_page": 25, "total": 7, "pages": 1,
  "filters": { "q": "", "zone": ["red", "poof"], "futures": true, "...": "..." },
  "stale": false,
  "updated_at": "2026-10-09T12:00:00+00:00",
  "methodology": "v3"
}

GET /api/coins/{id}

One coin by CoinGecko id (lowercase letters, digits and dashes, e.g. bitcoin): the coin object from /api/coins plus its history.

An invalid or unknown id returns 404 {"error": "Unknown coin"}.

curl -H "Authorization: Bearer $POOFBIT_KEY" https://poofbit.com/api/coins/bitcoin

Watchlist

The coins on your account's watchlist. Needs an account token; anonymous keys get 403:

{ "error": "Watchlist needs an account token" }

GET /api/watchlist

{"coins", "stale", "updated_at", "methodology"}, with the same coin objects as /api/coins.

PUT /api/watchlist/{id}

DELETE /api/watchlist/{id}

Add or remove one coin by CoinGecko id. Both answer {"ok": true} and are safe to repeat. Unknown id on PUT: 404 (DELETE answers ok for any id). Adding beyond 50 coins: 409.

curl -H "Authorization: Bearer $POOFBIT_TOKEN" https://poofbit.com/api/watchlist
curl -X PUT -H "Authorization: Bearer $POOFBIT_TOKEN" https://poofbit.com/api/watchlist/bitcoin
curl -X DELETE -H "Authorization: Bearer $POOFBIT_TOKEN" https://poofbit.com/api/watchlist/bitcoin

MCP for AI agents

PoofBit is a remote Model Context Protocol server, so Claude, Cursor and other agents can read the indexes as tools. Endpoint https://poofbit.com/mcp (Streamable HTTP), same API key and rate limit as the REST API. Use the https URL in production; some clients (mcp-remote) refuse plain http unless you pass --allow-http.

Claude Code

claude mcp add --transport http poofbit https://poofbit.com/mcp --header "Authorization: Bearer YOUR_KEY"

Cursor

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "poofbit": {
      "url": "https://poofbit.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_KEY" }
    }
  }
}

Claude Desktop and other stdio-only clients

Bridge with mcp-remote (needs Node.js). Add to claude_desktop_config.json; the key goes in an environment variable so the header has no space in it:

{
  "mcpServers": {
    "poofbit": {
      "command": "npx",
      "args": ["mcp-remote", "https://poofbit.com/mcp", "--header", "Authorization:${AUTH_HEADER}"],
      "env": { "AUTH_HEADER": "Bearer YOUR_KEY" }
    }
  }
}

The key goes in the Authorization: Bearer … header, as in every snippet above. The URL is /mcp (a trailing slash also works). If your client says the server needs OAuth or authentication, the API key is missing, wrong or revoked: check the header.

Tools

Try asking: “What's the Poof Chaos Index right now and which top-50 coins have the highest poof risk?”

Reading the index

Poof Chaos Index (market-wide, 0–100)

How turbulent the market has been over the last 24 hours and 7 days, 0–100, direction-neutral: a crash and a pump are equally chaotic: it describes now, not next week. Read it next to Fear & Greed as a second, independent axis. Computed over the top 50 coins by market cap, leaving out stablecoins and wrapped or staked tokens.

Zones

Quadrants

PCI is direction-neutral, so it is combined with Fear & Greed to tell calm from panic.

Components

Global Poof Index (market-wide, 11–111)

How much of the market is in a poof state right now. It has no model of its own: it averages the Poof Index of the first 100 coins of the PCI universe that have one, weighted by the square root of market cap (no coin above 15%), with a power mean that lets a few coins deep in a poof pull it up. Shown on the Poof Index scale and zones. Next to it: the share of the market in Red Flag Parade or worse. It describes the present state only and gives no early warning: PCI stays the turbulence gauge (see Does it work?).

Poof Index (one coin, 11–111)

An assessment of a coin's current poof state, learned from 9 years of Binance daily prices, delisted coins included. Six signals from the coin's daily closes go through a logistic model, then a calibration: L (0–100) is the share of similar past coin-states that were in a poof. The index is 11 + L, rounded; 11 is the floor, because crypto is never 0% poof.

A coin needs 31 daily closes for a value; until then lists show “—”. “Why N?” on a coin page shows how far each signal pushes the index up or down compared with a typical coin. Coin age counts from the first daily close we know: a coin known for a year or more counts as old, because our price history starts there.

Context (shown, not scored)

• Size — Smaller market cap = easier to push around.
• Dilution — Fully diluted value vs market cap: how many tokens are still waiting to be dumped on you.
• Crash from ATH — How far the price has fallen from its all-time high.
• Volume anomaly — Trading volume vs market cap. Too much smells like wash trading.

Positioning (context, not scored)

Coins with a Binance perpetual show funding, open interest, long/short and taker ratios, and an estimated liquidation pressure: a model that spreads each day's new open interest over 10x / 25x / 50x leverage (50 / 30 / 20 %) at that day's price. Flags: Funding hot (7-day mean ≥ 0.05 % per 8 h), Shorts paying (≤ −0.03 %), Leverage piling up (open interest +100 % in 28 days), Crowded longs / Crowded shorts (long/short accounts ≥ 3 / ≤ 0.5), Long liquidations stacked below (half the open interest within 10 % below). The market beta is the 60-day beta against the top-10 coins. None of this feeds the Poof Index: tested, it did not make the index better.

Every payload carries methodology ("v3" for the Poof Index, "v2" for PCI) so you can tell formula versions apart. The Poof Index describes now, not next week.

Does it work?

Poof Index

Tested walk-forward, year by year from 2021 to 2025: each year was scored by a model trained only on the years before it.

• What it does: it tells coins in a poof state from the rest with an AUC of 0.695. It flagged 9% of 1,221 collapses before they were obvious (before the drawdown passed 50%), a median 36 days earlier, with 1.5% false alarms. It never flagged BTC, ETH or SOL. Lead times are from the backtest, not a promise.
• A heavier model: a heavier research model tested alongside (not shipped) flagged 17%, 26 days earlier, at 1.75% false alarms.
• What it can't: LUNA and FTX gave no warning: what broke them was outside price data. Hacks, frauds, unlocks and exchange trouble show up only once the price moves.
• Levels drift: the share of coins in a poof state ran from 2% to 38% a year, so the same number overstates the risk in a calm year and understates it in a crash.

Global Poof Index

It describes the present state only. Its correlation with the share of the market in a poof state at the time is 0.40 [0.11, 0.59], against 0.15 for PCI (55 monthly points). Against what happened over the following 90 days it did worse than PCI (0.12 vs 0.43): PCI stays the turbulence gauge and G-PCI is not an early-warning signal.

Poof Chaos Index

We backtested PCI on a year of daily CoinGecko data for 150 coins, fitted every constant on the first 8 months and tested once on the last 4 (June–October 2026). 95% confidence intervals in brackets.

• Survivorship: the backtest only had coins that are still around.
• Calm test quarter: expect lower accuracy in a stressed market; one year of data is one market regime.
• Memecoin mania has no history to calibrate on yet; its scale will be re-anchored on live data.

Code examples

curl

curl -s -H "Authorization: Bearer $POOFBIT_KEY" https://poofbit.com/api/pci

Python

import os
import requests

key = os.environ["POOFBIT_KEY"]
headers = {"Authorization": f"Bearer {key}"}
data = requests.get("https://poofbit.com/api/pci", headers=headers, timeout=10).json()
print(data["pci"], data["zone"]["name"])

JavaScript

const res = await fetch("https://poofbit.com/api/pci", {
  headers: { Authorization: `Bearer ${process.env.POOFBIT_KEY}` },
});
const data = await res.json();
console.log(data.pci, data.zone.name);

Errors & caching

• 401: missing, unknown or revoked key. See Authentication.
• 403: the watchlist needs an account token.
• 404: unknown coin id (/api/coins/{id} and watchlist).
• 409: the watchlist is full (50 coins).
• 429: rate limit exceeded. Wait Retry-After seconds.
• 503 with {"error": "..."}: the data is temporarily unavailable. Retry in a minute.
• Successful responses carry Cache-Control: private, max-age=60, except /api/watchlist, which is private, no-cache. Market data refreshes every 5 minutes.
• Request bodies are limited to 64 KB.
• stale: true means the data missed three refreshes in a row; updated_at says when it was last refreshed.

Rate limits

• Free keys: 30 requests per minute and 1,000 per day. Account tokens: 120 per minute and 20,000 per day. REST and MCP count together; days are UTC.
• Over the per-minute limit you get 429 {"error": "Rate limit exceeded", "retry_after": 12} and a Retry-After header.
• Over the daily limit you get 429 {"error": "Daily limit exceeded", "retry_after": 3600}, with Retry-After counting down to 00:00 UTC.
• Data freshness is 5 minutes, so polling more than once a minute returns nothing new.
• Up to 3 new keys per network per hour.

Satire. Not financial advice. Poof risk and the Poof Chaos Index are computed mechanically from public market data (CoinGecko, alternative.me); they are not claims that any project is a scam. Do your own research, then do it again.