For bot developers

Every AnchorPad launch, verified, with its exact fee.

AnchorPad coins launch on Meteora Dynamic Bonding Curve pools (the default) or, optionally, on Raydium LaunchLab. Two read-only tools let your bot find them: a public JSON feed, and a single-file watcher that verifies each new pool straight from the chain.

Read-only. Nothing here signs, trades, or needs a wallet or an API key. We don't ask anyone to buy. Fees come from each pool's on-chain config.

Downloads

Two files, no install

On-chain watcher

Subscribes to Meteora DBC and Raydium LaunchLab program logs, reads each new pool and its config, and prints only AnchorPad launches as JSON lines, with the fee schedule. One file, Node.js 20+.

anchorpad-watcher.mjs

Feed sample

Polls the verified HTTP feed, overlaps windows by one second and removes duplicates by pool. No packages, Node.js 18+. Meteora launches by default; add --all-venues for Raydium too.

feed.mjs

# first block: bring your own RPC (HTTP + WebSocket)
RPC_URL=https://your-rpc.example WS_URL=wss://your-rpc.example node anchorpad-watcher.mjs --watch

# check one pool-creation transaction
node anchorpad-watcher.mjs --verify <signature>

# follow the HTTP feed
node feed.mjs --from <epoch-ms>

The HTTP feed lists a launch only after its pool is on-chain and verified (ANCHORCAT and HMM listed about 2 seconds after landing; not a guarantee), so watching the chain is always faster.

The feed

`GET /api/launches`

Newest first. Poll with ?since=<created_at of the newest launch you have>&limit=500; answers are cached for 2 seconds.

Field	Meaning
`pool`, `mint`, `venue`	Pool address, coin mint, `meteora-dbc` or `raydium-launchlab`
`quote_mint`, `quote_symbol`	The pair asset (SOL, USDC, …)
`created_at`	When AnchorPad listed it (ms). Use it as your `since` cursor.
`activated_at`	When trading opened, read from the pool (ms)
`signature`	The pool-creating transaction, when known
`uri`, `image`	Token metadata and image
`fee` (Meteora)	`feeBps` (100 = 1%) and `sniperShield`: `null`, or `{startBps, endBps, periods, periodSeconds, startsAt, endsAt}` for coins that open with a higher fee (new launches: 10% falling to 1% over the first two minutes; earlier coins keep their own schedule, e.g. 15% over one minute)
`fee` (Raydium)	Flat, no Sniper Shield: `feeBps`, `split {raydiumBps, creatorBps, platformBps}`, `verified`, `readAt`, read from Raydium's GlobalConfig and AnchorPad's LaunchLab PlatformConfig

How a pool is verified

What makes it an AnchorPad launch

Meteora DBC (program dbcij3LWUppWqq96dh6gJWwBifmcGfLSB5D4DuSMaqN): the pool's config pays fees to AijuZFq2eP4Um2ovaWNmCoZeX4NXrW7hU4efSdQC3BWz on the published schedule (1%: 0.4% creator, 0.4% AnchorPad, 0.2% Meteora), with AnchorPad's creator share, locked-LP split, migration and an audited pair asset.
Raydium LaunchLab (program LanMV9sAd7wArD4vJFi2qDdfnVhFxYSUg6eADduJ3uj): the pool names AnchorPad's platform DQ7uRyNQxo37JD9MSDBCBYV16h9rgPPsMqHFag2mig6i and the pair's constant-product GlobalConfig (1%: 0.375% creator, 0.375% AnchorPad, 0.25% Raydium).
Anyone can create a pool that names a platform, so never trust a name or a ticker: check the config, as the watcher does.

Test your parser on real launches: ANCHORCAT (Meteora, Sniper Shield), pool transaction 2dPFVJUqS4QXPBtwm1HZMT5s7oVrjix3kS9UT6QZmWxoZ4Co2Gym7474bTkLDo91oNgXmnT1T7UXsp4bYS52unhz; PAID (Raydium, flat 1%), 2Uebp5fv5zwLRminpFz5ESnmeiGrBFYESPRwm8v91UCtqye7a3zVFrwibHbPdFtqe15i8wwkNkwPUskEZBkoEzpS.

Found a missing field or a wrong value? Tell us on X: @anchorpadlabs.