How access works
Built for Robinhood Chain · chain id 4663

Trade and launch on Robinhood Chain. One API call.

Run multiple wallets, buy any token on the chain, and launch on Pons — all through a REST API built for bots and backends. No API keys: the wallet signing your request just needs to hold 1,000 $PORTAL.

Read the docs How access works
<400msmedian execution
1 callto launch on Pons
∞wallets per account
1,000 $PORTALminimum to sign a request
POST /v1/trades/buy
200 OK · 312ms 
curl https://api.hoodportal.xyz/v1/trades/buy \
  -H "X-Wallet-Address: 0x4dd2...9a71" \
  -H "X-Wallet-Signature: 0x9c1f...02ad" \
  -H "X-Timestamp: 1725556800" \
  -d '{
    "wallet_id": "wl_8f2ac1",
    "token": "0x39dBED3a2bd333467115dE45665cC57F813C4571",
    "amount_eth": 0.05,
    "slippage_bps": 200
  }'

// signing wallet holds 2,140 $PORTAL — request proceeds
{
  "status": "confirmed",
  "venue": "curve",
  "tx_hash": "0x7ad3f1...e02c",
  "tokens_out": "142893.221",
  "price_usd": 0.000041
}

Four endpoints. Everything on Robinhood Chain.

No wallet popups, no browser extension, no manual gas estimation. Send a request, get a confirmed transaction back.

wallets

Create and manage wallets

Spin up sub-wallets under one account and issue scoped session keys — set a spend cap, an expiry, and which contracts a key can touch.

POST /v1/wallets · POST /v1/wallets/:id/session-keys
trades

Buy or sell any token

Auto-routed between a token's Pons bonding curve and its post-graduation Uniswap v4 pool. Slippage protection on every order.

POST /v1/trades/buy · POST /v1/trades/sell
launches

Launch on Pons

Deploy a token and buy your own opening allocation in one atomic call — the opening buy can't be front-run.

POST /v1/launches
hooks

Webhooks

Get notified the instant a trade confirms, a launch graduates, or a creator-fee claim lands — no polling required.

POST /v1/webhooks

Three calls, start to finish.

The same request shape whether you're managing one wallet or four hundred.

POST /v1/trades/buy
{
  "wallet_id": "wl_8f2ac1",
  "token": "0x51a2...c9f0",
  "amount_eth": 0.1,
  "slippage_bps": 150
}

// 200 OK
{ "status": "confirmed", "tokens_out": "88214.5", "tx_hash": "0x9c1..." }
POST /v1/launches
{
  "wallet_id": "wl_8f2ac1",
  "name": "Sherwood",
  "symbol": "SHRWD",
  "quote_asset": "ETH",
  "creator_tax_bps": 100,
  "initial_buy_eth": 0.05
}

// 200 OK
{ "status": "launched", "token": "0x2fe1...a04b", "curve": "0x88ab...11de" }
POST /v1/wallets
{ "label": "sniper-03" }

// 200 OK
{ "wallet_id": "wl_8f2ac1", "address": "0x4dd2...9a71", "status": "ready" }

One balance. That's the whole access model.

No API keys, no metered pricing. Hold $PORTAL in the wallet you sign with, or your requests don't go through.

THE GATE

Every POST request is signed by a wallet. HoodPortal checks that wallet's live $PORTAL balance before executing anything. Below 1,000 $PORTAL, the request is rejected outright — no partial access, no warning tier.

NOT A METER

There's no per-call fee and no rate-limit tier tied to how much you hold. The same 1,000 $PORTAL that unlocks one request unlocks the next ten thousand. Reads (GET) never require a balance at all.

CREATOR REWARDS

Launch a token through HoodPortal instead of directly through Pons, and its trading volume funds a weekly $PORTAL payout to your wallet — on top of your normal Pons creator share.

How a launch pays its creator twice
You launch via HoodPortal POST /v1/launches deploys your token through Pons, same as launching directly.
Pons pays your normal share Your 70% creator cut lands in ETH exactly as it would without HoodPortal involved.
A built-in fee funds rewards Every HoodPortal launch carries a small 0.5% protocol fee, separate from Pons' own, pooled weekly.
Paid out in $PORTAL Half of that pool streams to the launching wallet in $PORTAL, for as long as people trade the token.

There's no way to call a write endpoint without your signing wallet holding at least 1,000 $PORTAL. Price and quote lookups (GET endpoints) are open to anyone.