Birdeye Sprint 4 Token Radar

This is a compact Birdeye Data demo for the Birdeye Data 4-Week BIP Competition — Sprint 4.

It builds a Solana trending-token radar by combining Birdeye's live trending feed with token overview and price data. The output is a ranked Markdown report plus a machine-readable JSON report and API call log.

What It Does

• Fetches the current Solana trending tokens.
• Enriches the top tokens with token overview data.
• Fetches a fresh price snapshot for each token.
• Produces a practical radar score using liquidity, volume, holder count, and 24h price change.
• Records a call log so the run can prove it made at least 50 Birdeye API calls.

Birdeye Endpoints Used

• GET /defi/token_trending
  • Used to discover the current Solana tokens gaining attention.
• GET /defi/token_overview
  • Used to enrich each candidate with liquidity, volume, holder, and market fields.
• GET /defi/price
  • Used to capture a fresh price snapshot for each candidate.
  • Reused for additional refresh snapshots when needed to reach the 50+ API-call qualification threshold.

The script sends the API key through the X-API-KEY header and uses x-chain: solana.

Run

cp .env.example .env
# put your Birdeye Data API key in .env
npm run radar -- --target-calls 51 --limit 20 --delay-ms 1300

The report is written to:

• data/radar-summary.md
• data/radar-report.json
• data/call-log.json

For a quick syntax check:

npm run check

Scoring Model

The score is deliberately transparent:

• Liquidity: favors tokens with enough depth to inspect.
• 24h volume: favors tokens with active markets.
• Holder count: adds a simple distribution signal when available.
• 24h price change: rewards momentum but caps the effect so extreme moves do not dominate.

This is not financial advice and should not be used as a trading signal. It is a data product prototype showing how Birdeye endpoints can be combined into a useful developer workflow.

Notes

The free API plan may rate-limit aggressively. Use --delay-ms to slow down calls. Failed calls are recorded in the log and the script keeps going where possible.