Kasandra patterns

AI-detected chart patterns on a coin, with bullish/bearish signal and confidence. One call returns a multi-timeframe set — no list endpoint, no pagination.

1 call= a multi-timeframe pattern set

20 patterns per coin per request, across 1D, 1M, 3M, 1Y, 3Y and ALL windows. There is no list endpoint, and the response is a bare JSON array — not an envelope.

What's in a record

Every field the corpus returns for one record. Real shape — walked corpus-wide, not sampled.

id
coin
interval
pattern_type
signal
confidence
start_timestamp
end_timestamp
key_points
modified

[
  {
    "id": 278452859,
    "coin": {
      "id": 1,
      "name": "Bitcoin",
      "ticker": "BTC",
      "slug": "bitcoin",
      "icon": "https://s2.coinmarketcap.com/static/img/coins/64x64/1.png"
    },
    "interval": "3Y",
    "pattern_type": "double_bottom",
    "signal": "bullish",
    "confidence": 0.835,
    "start_timestamp": 1788307200000,
    "end_timestamp": 1788998400000,
    "key_points": [
      { "price": 77333.13, "timestamp": 1788307200000 },
      { "price": 81269.43, "timestamp": 1788393600000 },
      { "price": 76566.61, "timestamp": 1788998400000 }
    ],
    "modified": "2026-09-18T06:41:16.302721Z"
  }
]

Get it

A curl that runs against the live API right now, plus the MCP tool names for the same data.

curl https://api.alphaday.com/kasandra/patterns/bitcoin/

MCP tools

get_kasandra_patterns

What it's for

Three concrete questions this capability answers that a general crypto API does not.

An agent that needs a 'what is this chart doing' opinion per coin without writing a pattern detector. One unauthenticated call returns a complete multi-timeframe set.
Filtering signals client-side by interval and confidence: signal is bullish or bearish, confidence is in [0, 1]. A 'high-confidence bullish, recent' screen is a one-liner.
Overlaying detected key-points onto an existing chart: each pattern carries key_points: [{price, timestamp}] with the trigger prices and the timestamps in epoch milliseconds.

Known limits

Required, not optional. Coverage gaps, staleness and parameter traps that were observed by running the curl above against the live server on 2026-09-18.

Keyed on coin slug, not ticker.

/kasandra/patterns/bitcoin/ returns 20 patterns; /kasandra/patterns/BTC/ returns 404 with detail "coin requested does not exist or is not supported". The slug is the join key, the same convention the news / market endpoints use, but a reader used to a ticker-keyed price feed will type the ticker first and the page must call this out.

There is no list endpoint.

/kasandra/patterns/ returns 404. There is no corpus-wide count of patterns and no list-of-coins endpoint; the coin you can query is whatever the server happens to support, discoverable only by trying the slug.

The response is a bare array of 20, not an envelope.

There is no {count, next, results} shape. Each call returns at most 20 patterns for one coin, and the set covers a fixed six-interval span (1D, 1M, 3M, 1Y, 3Y, ALL). Iterate interval rather than paginating.

Figures and payloads verified against the live API on 2026-09-18. The API needs no key and no signup — see the full endpoint reference and the MCP server.

All 22 capabilities Cookbook: worked use cases

The crypto data layer for humans, apps, and AI agents.

Product

Launch app Dashboards API & MCP Docs Pulse Recipes

Company

Blog Contact Give Feedback Terms of Use Privacy Policy

Crypto 101

What is Bitcoin?What Is Ethereum?What is Wrapped Crypto?What is Arbitrum?What is zkSync?

Learn

Making Money with Cryptocurrency How to Build a Cryptocurrency Dashboard What Is Crypto Halving: A Bitcoin Story How To Set Up Ethereum Wallet How to Read Crypto Charts Crypto Asset Management Guide Staking vs. Liquidity Mining (Yield Farming)