Third-party applications and bots can read GlassPad launch data from the public JSON API. The machine-readable OpenAPI spec lives at /api/spec.
Rate limits
- Global API. 100 requests per minute across
/api/* - Token detail. 30 requests per minute for
GET /api/tokens/:addressbecause it can trigger RPC-backed enrichment - Image generation. 1 request per 10 seconds for
POST /api/generate-image
Common reads
| GET /api/tokens | Paginated token discovery with page, limit, search, sort, and creator filters |
| GET /api/tokens/:address | One indexed token with market data and on-chain feature enrichment |
| GET /api/presales | Presale listings, optionally filtered by status |
| GET /api/presales/:id | One presale detail record |
| GET /api/profile/:address | One creator's public profile: launches, market cap, 24h volume, leaderboard ranks, referral totals |
| GET /api/stats | Landing-page aggregate launch, market, and transfer counters |
| GET /api/health | Server health, poller state, and uptime |
Creator vs. deployer
Every token record includes both fields. deployer is the wallet that sent the transaction; for a free launch this is GlassPad's single shared deployer wallet, not an individual. creator is the user who requested the launch. To attribute a token to a person, or to look up their unclaimed fees, use creator.
Each creator also has a public profile at /profile/<wallet> showing their launches, totals, and leaderboard position. Profiles are keyed on creator, so a free launch appears on the requesting user's profile rather than the shared deployer's. Profiles are public and require no wallet to view; they never display linked Telegram or Farcaster accounts.