Pons Launchpad

Pons v2 launchpad intelligence on Robinhood Chain, from the MeshGateway team: live launch feed, full on-chain launch records, graduation events, and claimable creator-fee balances, read straight from the verified factory and fee-escrow contracts. Independent service, not affiliated with Pons. Machine-payable per request.

Robinhood Chain

Offers

Offer	Endpoint	Price
Claimable creator fees Creator fees sitting unclaimed in the Pons fee escrow, in the launch pairing asset. Pass ?token= to resolve the launch current recipient, or ?recipient= to read an address balance directly. Returns wei and ETH amounts plus how to claim.	`/m/pons/fees`	0.01 USDG
Latest graduations Tokens that recently graduated from the bonding curve into a real pool: token, position id, amounts seeded, and the graduation transaction, newest first. Pass ?limit=10 (max 25).	`/m/pons/graduations`	0.02 USDG
Launch record Full on-chain record for one Pons launch: phase (bonding, swept, graduated, rescued), deployer, creator fee recipient plus any pending timelocked recipient change, creator tax, buyback flag, graduation threshold, swept amounts, and the fees claimable right now. Pass ?token= with the ERC-20 address.	`/m/pons/launch`	0.01 USDG
Latest launches The newest tokens launched through Pons v2, newest first: token address, name, symbol, deployer, bonding curve, pairing asset, graduation threshold, and launch transaction. Pass ?limit=20 (max 50).	`/m/pons/launches`	0.02 USDG

Machine-readable: openapi.json with x-payment-info offers.

Try it live

Run the full MPP flow from your browser: catch the 402, sign the payment with your wallet, and watch it settle on-chain.

Pay with an agent

Any MPP or x402-compatible client works. With mppx, payment is automatic:

// x402 exact scheme (permit2) on Robinhood Chain
// 1. GET the endpoint, read the payment-required header (base64 JSON)
// 2. Sign PermitWitnessTransferFrom against Permit2 for the advertised offer
//    (spender = x402ExactPermit2Proxy, witness.to = merchant wallet)
// 3. Retry with the payment-signature header; settlement tx arrives
//    in the payment-response header
const res = await fetch('https://api.meshgateway.co/m/pons/fees', {
  headers: { 'payment-signature': signedPaymentPayload },
})

Or inspect the challenge yourself:

curl -i https://api.meshgateway.co/m/pons/fees
# HTTP/1.1 402 Payment Required
# WWW-Authenticate: Payment id="…", method="evm", intent="charge", …