Alpha Leak exposes a live signal feed and a set of REST endpoints. This guide covers connecting to both — from opening the SSE stream to interpreting your first signal payload.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/0xW1re/solvedocs/llms.txt
Use this file to discover all available pages before exploring further.
Base URL
All endpoints are available at your hosted instance URL. Replaceyour-instance throughout this guide with the host you’ve been given.
Connect to the live feed
The primary interface is a Server-Sent Events stream that pushes signals, graduations, and anti-signals in real time as they occur on-chain. This is the fastest way to consume Alpha Leak data — no polling required.The stream sends a
heartbeat event every 15 seconds to keep connections alive through proxies and load balancers.Fetch recent data on load
Before the live stream has delivered events, use the This endpoint is designed to be called once on page load, with the SSE stream taking over from that point forward.
/api/live/recent endpoint to populate your initial state:Understand signal types
Alpha Leak emits three types of signals on the live feed.
signal — a tracked wallet (one the system has built a quality profile for) has made a significant buy. The payload includes the wallet’s alpha score, ML probability score, token state, buy rank, velocity data, and creator risk.genesis_signal — a newly created token scored highly across the genesis model’s 75-feature vector during its first 60 seconds of life. No tracked wallet needed — this is purely based on launch dynamics.anti_signal — a token with recent buy signals has triggered 2 or more adversarial detection rules simultaneously (for example, coordinated bundle + high bot buyer percentage). Any system acting on the original signal should treat this as an exit cue.Query historical data
All historical signal, wallet, and token data is available via REST:Full parameter reference for each endpoint is in the API Reference.