Data Guide

This guide covers the concepts and patterns you need to work effectively with AIXBT data, regardless of which surface you use (CLI, MCP, or REST API).

Core Concepts

Momentum

momentumScore measures the rate at which new clusters pick up a project. This is not mention volume -- a project discussed by 15 independent clusters scores higher than one with more total mentions confined to 2-3 groups. Momentum captures narrative spread, not loudness.

Popularity

popularityScore is the number of hours in the last 24 that had at least one mention (0-24). High popularity means sustained, consistent attention. A project can have high popularity but low momentum (established, stable attention) or high momentum but moderate popularity (rapidly emerging but still early).

Signals

Structured events extracted from community discussion. Each signal has a category, a description, timestamps, and source clusters. Signals are deduplicated: if multiple sources report the same event, they reinforce a single signal rather than creating duplicates.

Key fields:

• detectedAt -- When the signal was first spotted
• reinforcedAt -- When it was last reinforced by new evidence
• activity[] -- Reinforcement history (length = total detection count). Each entry has date, source, cluster, and what the new evidence said
• hasOfficialSource -- The project's own account appears in the activity

Signal Categories

Clusters

Distinct community segments identified via social graph analysis. Cross-cluster convergence -- independent communities discussing the same project -- carries more weight than single-cluster volume. When multiple unrelated clusters converge on the same signal, the information is more likely to be significant.

Metrics

Market data available on project objects without an external lookup: price, market cap, 24h volume, 24h change, 24h high/low, and 7d/14d/30d price change.

Grounding

Structured market context covering macro, crypto, traditional finance, and geopolitics. Updated hourly. Free, no key required. Use it to contextualize signal and momentum data against broader market conditions.

Query Patterns

These describe analysis workflows. Map to your surface's commands or tools.

Research a project

Look up by name, ticker, or contract address. Get full details. Check momentum history. Scan recent signals.

Assess: is momentum rising or declining? Which clusters are driving it? What signal categories dominate? Heavy TECH_EVENT signals mean development progress. Heavy OPINION_SPECULATION means narrative without substance.

Note: project detail responses include the 10 most recent signals. Use the signals endpoint directly for a fuller history.

Market overview

Fetch top projects by momentum (what's spreading fastest) or popularity (what has sustained attention). Fetch recent signals across all projects. Cross-reference: which projects appear in both?

To identify narratives, fetch a larger set and synthesize across the results -- group projects that share signal themes or cluster overlap.

Community-specific

List clusters. Identify relevant ones by name and description. Fetch signals from those clusters. Compare against the broader momentum list to find what a group noticed that the market hasn't.

Category scan

Filter signals by category. Combine strategically:

Time-based queries

• Use detectedAfter/detectedBefore to find signals by when they were first spotted
• Use reinforcedAfter/reinforcedBefore to find signals actively discussed in a period
• Use the momentum endpoint with start/end for how attention evolved over time

These can be combined: "signals detected in the last month that are still being reinforced today" uses both date filter types.

Interpreting Patterns

High momentum, few signals -- Talked about but sparse events. Could be hype, speculation, or early-stage buzz before developments are announced. Treat with caution.

Many reinforced signals across clusters -- Strong narrative with substance. Multiple independent communities confirming the same events. Highest-conviction pattern.

High momentum, single cluster -- One community is excited, but it hasn't spread. Could be organic early discovery or coordinated promotion.

Momentum declining, signals still active -- The news is real but attention is fading. The story may be priced in or losing novelty.

Old signal, recent reinforcement -- An event from days or weeks ago is still being discussed. Often means the implications are still unfolding.

No signals, but project is tracked -- Activity exists but hasn't produced verifiable events. Common for meme tokens and speculation-driven projects.

Cluster progression in activity log -- Track which cluster reported first and how it spread. Early clusters often have better signal quality for that domain.

Cross-Referencing with External Data

AIXBT includes identifiers for looking up projects in other systems:

• xHandle -- The project's X/Twitter handle
• coingeckoData.apiId -- For historical price data and deeper market context
• tokens[].address + tokens[].chain -- Contract addresses for on-chain lookups, DEX data, or block explorers
• coingeckoData.categories -- Sector tags for grouping projects by theme