Documentation
FomoQuant docs
What FomoQuant measures
Fomo has theses, users, timing, tokens, attention and outcomes. FomoQuant continuously ingests that activity, joins it with market and onchain context, and turns it into:
- Token scores — Momentum, Conviction, Crowding, Early Quality, Narrative Velocity, Divergence and Smart Cohort, each with drivers, confidence and a model version (Scores).
- Signals — versioned rules over scores and features with neutral reasons and historical analog statistics (Signals).
- User metrics — point-in-time hit rate, lead time, false positives and a research score that is never follower-based (Users).
- Cohorts and narratives — convergence of user groups and the rotation of attention between stories (Cohorts & narratives).
- Backtests and event studies — strict time-series research with drawdowns and full distributions (Backtests).
Data: live mainnet only
Every number comes from the live dataset: authorized Fomo theses from fomoapi.io on mainnet chains — Robinhood Chain, Solana, Base, BNB Chain, Ethereum and Arc — with real DexScreener / GeckoTerminal market data and public onchain data for the same tokens. Nothing is simulated and no test network is ingested. Every object says so with "dataset": "live" and "livemode": true.
History is point in time and grows with the live feed. Outcomes resolve 72 hours after each thesis, so author track records, early-quality scores, analogs and backtests carry their sample size and confidence — a young history is shown as such, never padded.
API keys and scopes
Create keys on the API page after signing in with your email. A key is shown once; we store only a salted SHA-256 hash and a 12-character display prefix. Keys are live keys (fq_live_…) on every plan; the plan sets the rate limit. Default rate limits are 60 requests per minute on Free, 600 on Pro and 2,000 on Team.
| Scope | Grants |
|---|---|
tokens:read | Token quant snapshots, token lists, analogs and the scanner. |
signals:read | The signal feed and signal detail. |
users:read | User (author) quant profiles. |
cohorts:read | Algorithmic cohorts and your own cohorts, with convergence events. |
backtests:read | Backtest runs and event studies. |
backtests:write | Queue backtests (Pro / Team). |
narratives:read | Narrative map, rotation and heatmap. |
webhooks:write | Create, list, test and delete webhooks. |
stream:read | The realtime WebSocket stream. |
Plans: every plan reads live data over the API; Pro and Team add higher rate limits and backtests. See pricing.
Base URL
REST https://fomoquant.app/v1/...
OpenAPI https://fomoquant.app/openapi.json
WebSocket GET https://fomoquant.app/v1/stream/info → "url": "wss://…/v1/stream"The realtime WebSocket runs on a separate host whose address can change, so it is discovered rather than fixed: GET /v1/stream/info returns the current url (or available: false with a message while that host is offline — REST and webhooks keep working). The SDK's stream() does this on every reconnect.
Authenticate with Authorization: Bearer fq_live_… (or the x-api-key header). Every response carries an X-Request-Id; include it when you report a problem.
Conventions
- JSON is snake_case and serialised from the same read models the web app renders — the API returns the same numbers you see on screen.
- Quant objects include
model_versions(e.g.momentum-v1.0) andfreshness(last Fomo event, last market point, stale flag and human-readablestale_reasons). nullmeans “not available” — never zero. Scores are null when there is not enough data; the score'sconfidencesays why.- Timestamps are ISO-8601 UTC. Percentages are fractions (
0.168= +16.8%). Ids are stable and prefixed (tk_,fp_,sig_,cohort_,btr_). - Lists are cursor-paginated:
{ object: "list", data, has_more, next_cursor }.
Where next
FomoQuant provides analytics and historical/statistical context, not financial advice or guaranteed predictions.