Third-party bots can read Bonker 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 carries both. deployer is the wallet that actually sent the transaction — for anything launched through the Farcaster, Telegram, or MoltBook bots that is Bonker's one shared deployer wallet, not a person. creator is the human who asked for it. If you are attributing a token to somebody, or looking up their unclaimed fees, use creator.
Every creator also has a public profile at /profile/<wallet> — their launches, totals, and where they sit on the leaderboard. It is keyed on creator, so a bot launch shows up on the human's profile rather than the shared deployer's. Profiles are public and need no wallet to view; they never show linked X, Telegram, or Farcaster accounts.