AIXBT Docs

Intel

Timeline of detected events for a project

The Intel tab shows a chronological timeline of events detected for a project. Each piece of intel represents a discrete, verifiable fact derived from tracked discussions.

The Timeline

Intel appears in reverse chronological order with the most recent at the top. Each entry shows a category badge indicating the type of event, followed by a concise description of what happened. Scroll to navigate through the project's intel history.

Intel Categories

AIXBT classifies intel into the following categories:

CategoryDescription
FINANCIAL EVENTToken sales, TGEs, airdrops, funding rounds, grants, incentive programs
TOKEN ECONOMICSEmissions, burns, supply changes, fee distribution, staking/locking terms
TECH EVENTMainnet/testnet launches, upgrades, feature releases, audits, major infra changes
MARKET ACTIVITYListings, delistings, new trading pairs, liquidity pools, market-making programs
ONCHAIN METRICSAchieved TVL, volume, fees, user counts, active addresses
PARTNERSHIPIntegrations, collaborations, co-launches, co-marketing with named counterparties
TEAM UPDATEFounders/leads joining or leaving, major hires, role changes
REGULATORYLicenses, approvals, bans, enforcement actions, legal/regulatory moves
WHALE ACTIVITYVery large transfers, accumulations, distributions, position changes
RISK ALERTHacks, exploits, outages, halts, critical bugs, recovery events
VISIBILITY EVENTConference talks, hackathons, AMAs, interviews, media coverage, award nominations

What Becomes Intel

Intel is detected when tracked discussions describe:

  • A specific change or confirmed future change for the project
  • An onchain or market metric that has been achieved

General marketing, vague hype, and simple project descriptions do not become intel. Neither do predictions about future metrics ("could reach X") or speculation about what might happen.

One real-world fact produces one piece of intel. If multiple sources report the same event, the intel is reinforced.

Reinforcement

When multiple sources report the same event, they reinforce a single piece of intel rather than creating duplicates. Each reinforcement updates the timestamp and is recorded in the activity log.

Intel created days ago can still be relevant if it continues to receive reinforcements. This indicates the event remains part of active discussion. The Indigo agent factors in reinforcement activity when assessing what matters now, so older intel that is still being talked about surfaces alongside recent entries.

Activity

Each piece of intel includes an activity log showing the sequence of reinforcement events. Activity entries record the cluster the information originated from and how the description evolved with each new piece of evidence. This data is available in the terminal and through the API.

The first report of an event is rarely the most detailed. Early intel often captures the headline while later reinforcements add specifics like figures, timelines, and counterparties. For example, if the first tweet says "ETH exchange balances hit record lows" and a later tweet adds "10.5M ETH, representing 8.7% of supply", the description may be updated to include those figures.

Activity makes this evolution visible, enabling information flow analysis: tracking which clusters surface a story first, how it spreads across communities, and how the description sharpens over time.

Empty Intel Tab

Some projects show no intel. This happens when:

  • The project is new and hasn't generated noteworthy activity
  • Recent discussions have been general chatter without concrete events
  • The project primarily attracts opinion rather than news

Activity still contributes to momentum even when it doesn't produce intel. The momentum bars and score reflect all tracked mentions, while the intel tab filters down to detected events.

On this page