Flicker public API: crypto analysis, zones and market data over REST

Flicker has a public REST API. It serves the same read the web and mobile apps show, so your own code can ask what Flicker reads on an asset: the verdict, its reasons, and the exit before the entry.

There are two ways in, and both come with a free Flicker account:

• The REST API, with an API key you create yourself, for your own code.
• The MCP server, with an OAuth sign-in, for AI assistants such as Claude and ChatGPT. See Flicker's MCP server.

The full walkthrough lives on the developer portal.

---

What the API serves

One host serves every endpoint: https://api.flicker.finance. The major version is in the path (/v1, /v2). An API key reaches the read-only market-data part of it:

• Analysis of one asset. The verdict (buy, hold or sell) comes from six factors: trend direction, momentum, Fear & Greed, breakout setup, risk level and cycle phase. The response says how many of them agree with it; that is agreement, not a probability. Alongside it come the zones, each with its stop, up to two targets, its entry range and its risk/reward, plus the chart candles.
• A written overview of an asset. AI writes it in plain words, in any of the seven app languages. The verdict, zones and stops it describes are computed, not written by AI.
• Assets: search and filter the list of coins, stocks, currencies and metals Flicker reads, each with its verdict on the default timeframe, and screen for assets currently inside a buy or sell zone.
• Sentiment: a Fear & Greed score from 0 to 100 per asset, its daily history, and a leaderboard across assets.
• Market data: global market stats, an asset's markets by volume, funding rates on derivatives venues, and the list of exchanges Flicker covers.

Every route, parameter and response shape is in the interactive reference, with the machine-readable OpenAPI 3.1 document at https://api.flicker.finance/docs/openapi.json.

What a key cannot do

A key cannot place an order, move funds or read anyone's account. Flicker reads, marks and explains; it has no path that trades. If your project needs execution, that part goes through an exchange's own API.

---

Getting started

1. Create a Flicker account. Keys are made from an account, so the account is the sign-up.
2. Create a key on the API keys page of your account. You can list and revoke keys there too, and see the day's credits used.
3. Send it in the x-api-key header of every request.

A first call:

Responses are JSON. There is no anonymous tier: a request without a valid key is refused with a 403.

---

Limits and errors

• Rate limit: a budget of 2,000 weighted units per 60 seconds per client IP. Heavier endpoints cost more units than light ones. Every response reports where you stand in the x-ratelimit-limit, x-ratelimit-remaining, x-ratelimit-used and x-ratelimit-window headers; a 429 adds retry-after.
• Daily credits: each account has a daily allowance of API calls, which resets at 00:00 UTC. The API keys page shows how many you have used, and GET /v1/users/api_keys/credits returns the same. The allowance is larger on Pro and Elite.
• Errors: every error body has the same shape, { "success": false, "code": "…", "message": "…" }. Branch on code; message is for logs.

---

What your plan changes

API keys and the MCP server are account features, not a separate paid plan. The plan you already have decides which reads a key can open, the same way it does in the app:

• Free: the default timeframe, the daily read, with its verdict, zones, stops and targets, and 500 candles of chart history. DEX tokens are open at every timeframe their source serves.
• Pro: every other timeframe and deeper chart history. A request outside your plan answers 402 with a code that names which limit it hit.

Claiming a partner promotion also unlocks 30 days of Pro.

---

What people build with it

• A dashboard for the assets you follow: the verdict, how many factors agree, and each zone's stop and targets in one view.
• A bot that posts the read to your own Telegram or Discord channel. It reports what Flicker reads; it doesn't trade.
• A watch script that checks your list once a day and tells you which assets sit inside a zone, with the stop and target to look at before deciding.
• A research notebook that pulls an asset's sentiment history next to its price.

If you only want Flicker data on a website, you don't need a key: a widget is one snippet, free and with no sign-up.

---

AI assistants: the MCP server

The MCP server gives Claude, ChatGPT, Cursor and other MCP clients the same analysis as tools, plus, once you approve it, your own portfolio, watchlist and alerts. It doesn't use an API key. You add the server URL to your client, sign in to Flicker once, and approve the connection; you can disconnect the app from your account's security settings at any time. No tool places an order.

• Flicker MCP server: what it is and what the tools cover.
• Connect Claude and ChatGPT to live crypto data: the setup in three steps.

---

FAQ

Is the Flicker API free?

Creating an API key is free with any Flicker account. A free account reads the daily timeframe, within a daily credit allowance. Pro opens the other timeframes and a larger allowance.

Can the API place trades for me?

No. The API reads and reports. A key reaches market data only; it cannot place an order, move funds or read an account.

What does the analysis endpoint return?

The verdict and how many of the six factors agree with it, every zone with its stop, targets, entry range and risk/reward, and the chart candles. The reference lists every field.

Does the MCP server use my API key?

No. The MCP server uses an OAuth sign-in to your Flicker account; API keys are for the REST API.

What is the rate limit?

2,000 weighted units per 60 seconds per client IP, reported in the response headers, plus a daily credit allowance per account.

We analyze. You decide. We never trade for you.

---

Related:

• Flicker MCP server — connect AI assistants to Flicker's analysis.
• Connect Claude and ChatGPT to live crypto data — the MCP setup in three steps.