PONS Robinhood Chain Buy and Sell API
Check the token stage, build a transaction, then sign inside your own bot.
Public beta: hosted market reads are currently limited by upstream RPC throttling; a dedicated Robinhood Chain RPC is needed. Settlement contract deployment and funded tests are still pending. Trading endpoints return SETUP_REQUIRED until setup. This service is not collecting fees yet.
Source and examples · OpenAPI · Live capabilities
Start with the token
curl https://pons-robinhood-trade.apilabph.workers.dev/api/market \
-H 'Content-Type: application/json' \
-d '{"token":"TOKEN_ADDRESS"}'No API key. Replace the token address with a real supported market. Limits: 6 requests/minute per IP and 20/minute per service at the edge.
Buy or sell after setup
POST /api/trade
{
"publicKey": "YOUR_PUBLIC_WALLET",
"token": "TOKEN_ADDRESS",
"action": "buy",
"amount": "0.01",
"slippageBps": 100,
"maxServiceFeeBps": 25
}Buy amounts are decimal ETH; sell amounts are raw token units. A funded wallet is required for simulation. Approve an exact sell amount through /api/approval when needed, sign locally, then rebuild. Transactions expire quickly and can still fail if chain state changes.
Coverage
PONS V2 native-ETH bonding curves, PONS V1 WETH/Uniswap V3 pools and PONS V2 native-ETH/Uniswap V4 graduation pools. Closed curves, intermediate migration phases, rescued markets and ERC20 quote assets are rejected. This is Robinhood Chain, not a Robinhood brokerage API.
What the builder verifies
Canonical market, current stage, deployed settlement bytecode, exact fee recipient, transaction simulation and an absolute minimum net output. Stage is checked again during execution. No private keys or broadcast endpoints.
0.25% service fee
Buy fees apply to actual native input used, within the total budget. Sell fees are deducted from native proceeds. Unused buy input is refunded. Gas, protocol fees and taxes are separate. Fee recipient: 0x6A17d358ae138A726b4dda7A95C104440AAdb2DB.
Run your own
Each launchpad has its own repository and deployment. Follow the operator setup and release evidence. There is no RapidAPI association. No independent audit or latency SLA is claimed.