Overview

HoodPortal is a REST layer over Robinhood Chain. It manages wallets, executes trades, and launches tokens on Pons — so you can automate all three from a backend instead of a browser wallet.

There are no API keys. Every write request is signed by the wallet performing the action, and HoodPortal checks that wallet's live $PORTAL balance before it executes anything — hold at least 1,000 $PORTAL, or the request is rejected. See Access for the exact mechanics.

Access

No API keys. Access is tied to the wallet signing each request, not to an account or a plan.

Every write request (POST) must be signed by the wallet performing the action. HoodPortal recovers the signer from that signature, confirms it matches the wallet you're claiming to act as, and reads that wallet's live $PORTAL balance on-chain before doing anything else.

Signing a request

Sign the message hoodportal:{timestamp}:{sha256(body)} with the wallet's private key, then attach the result as headers:

X-Wallet-Address: 0x4dd2...9a71
X-Wallet-Signature: 0x9c1f...02ad
X-Timestamp: 1725556800

Wallets

Create sub-wallets under one account and issue scoped session keys for each.

POST/wallets

Creates a new wallet. Funds must be deposited to its address before it can trade, and it needs at least 1,000 $PORTAL before it can sign any further request.

{ "label": "sniper-03" }

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

POST/wallets/:id/session-keys

Issues a scoped session key for a wallet. HoodPortal uses this key to execute trades and launches on the wallet's behalf — it can never exceed the scope you set here, and it stops working the moment the wallet's $PORTAL balance drops below 1,000, regardless of expiry.

{
  "spend_cap_eth": 2.0,
  "daily_cap_eth": 0.5,
  "expires_in": "30d"
}

// 200 OK
{ "session_key_id": "sk_9d41", "expires_at": "2026-10-05T00:00:00Z" }

GET/wallets/:id

Returns balances across every token the wallet holds, plus its active session keys. No signature or $PORTAL balance required to read.

Trading

Buy or sell any Robinhood Chain token. HoodPortal reads the token's phase and routes the order to its Pons curve or its Uniswap v4 pool automatically.

POST/trades/buy

{
  "wallet_id": "wl_8f2ac1",
  "token": "0x39dBED3a2bd333467115dE45665cC57F813C4571",
  "amount_eth": 0.05,
  "slippage_bps": 200
}

// 200 OK
{
  "status": "confirmed",
  "venue": "curve",
  "tx_hash": "0x7ad3f1...e02c",
  "tokens_out": "142893.221",
  "price_usd": 0.000041
}

POST/trades/sell

Same shape, in reverse — pass a token amount instead of an ETH amount.

{
  "wallet_id": "wl_8f2ac1",
  "token": "0x39dBED3a2bd333467115dE45665cC57F813C4571",
  "amount_tokens": "50000",
  "slippage_bps": 200
}

GET/tokens/:address

Live price, market cap, phase (curve or graduated pool), and graduation progress for any token on the chain. No signature or balance required.

{
  "phase": "curve",
  "price_usd": 0.000041,
  "market_cap_usd": 41000,
  "graduation_progress": 0.71
}

Launching on Pons

Deploy a new token and, optionally, buy your own opening allocation — atomically, so nothing can trade in between.

POST/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",
  "tx_hash": "0x51ac...90fd"
}

Webhooks

Subscribe to an event instead of polling for it.

{
  "url": "https://yourapp.com/hooks/hoodportal",
  "events": ["trade.confirmed", "launch.graduated"]
}

Errors

Errors return a 4xx or 5xx status with a machine-readable code.

$PORTAL & rewards

$PORTAL gates access and funds creator rewards. There is no fee tier, no subscription, and no metering.

The access requirement

Creator rewards

Launching through POST /v1/launches instead of directly through Pons adds a second, ongoing reward stream on top of your normal Pons creator fees:

1. Your token trades — on the curve, then in its graduated pool.
2. Pons pays your standard creator share directly, in the launch's quote asset, exactly as it would without HoodPortal involved.
3. Every HoodPortal launch also carries a small built-in 0.5% protocol fee, separate from Pons' own, pooled weekly.
4. Half of that pool is paid out weekly, in $PORTAL, to the wallet that launched the token — for as long as it keeps trading.

{
  "token": "0x2fe1...a04b",
  "week_ending": "2026-09-06",
  "volume_usd": 184200,
  "portal_reward": "412.6 PORTAL",
  "claimable": true
}