Platform data & API
Read-only views, authenticated actions, and interpreting platform statistics.
What the statistics mean
Platform statistics derive from indexed market events and confirmed execution records. Volume describes trades covered by the index. Card purchases and card deliveries describe separate completed actions.
Missing or unindexed values should remain unavailable rather than being invented from sample tokens. Preview entries are not evidence of platform volume, holders, or completed rewards.
Read endpoints
These routes belong to the SLABZ application. They are not a replacement for the upstream providers’ APIs.
| Route | Purpose |
|---|---|
| GET /api/markets | Registered market listings |
| GET /api/pump/capabilities | Current verified pair, fee, and execution capabilities |
| GET /api/status | Configuration readiness |
| GET /api/eligibility?mint=…&wallet=… | Indicative balance and raffle ticket count |
| GET /api/collection?wallet=… | Confirmed reward delivery history |
| GET /api/rounds/{roundId} | Committed round record and draw proof |
Authenticated actions
Launch creation and preparation require an authenticated account. Transaction submission additionally verifies that signed bytes match the stored preparation and expected signers. A client-provided success flag or transaction signature alone cannot mark a token live.
Do not send API keys, seed phrases, private key files, or provider credentials in browser requests. Operator authentication and marketplace credentials are server configuration.