Openfin Pons

OpenFinance Pons (Robinhood Chain launches)

Launch a token on Robinhood Chain (EVM chain id 4663) paired against ETH or any Pons-approved quote asset — including Robinhood's tokenized-stock mirrors. Every launch is a direct on-chain contract call (no Pons API layer); signed via the caller's Privy EVM wallet.

No platform fee — creatorFeeRecipient defaults to the launcher's own wallet, so they keep 100% of Pons's creator-fee bucket. The launcher can instead point it at an explicit wallet (creatorFeeRecipient) or share it with token holders (shareFeesWithHolders) — see the launch table below; the two are mutually exclusive.

Routing

• Pons launch = EVM (Robinhood Chain), user's EVM wallet — this skill.
• Solana DBC launch (memecoin on Meteora) = openfin-launchpad.
• Any other EVM chain = not a Pons launch. Pons is Robinhood-Chain-only.

The block explorer for Robinhood Chain is https://robinhoodchain.blockscout.com.

Safety contract

Reads (list_quote_assets, get_launch_terms, list_tokens, get_claimable_fees) are safe. launch_token writes — it commits real funds on mainnet and is irreversible. enable_holder_fee_sharing also writes and is irreversible (via Pons's own creator-controls) — treat it with the same explicit-confirmation weight. sweep_fees/claim_fees write too, but only move the caller's own already-accrued fees (curve → escrow → wallet) — they can't misdirect funds to anyone else, so they don't need launch-level ceremony; still mention the amounts from get_claimable_fees before calling. Before calling launch_token:

1. Resolve the quote asset. If the user named it by ticker ("TSLA", "NVDA", "ETH"), call list_quote_assets and confirm the ticker matches an approved entry. The approved list is live-checked and can change; don't assume a stock is still on it.
2. Get live terms via get_launch_terms { quoteAsset } and show the user: launchFee (in ETH), the resolved quote asset, the canLaunch flag (must be true — otherwise stop and surface why), maxCreatorTaxBps (their creatorTaxBps will be capped to this), and the graduation threshold.
3. Show the full plan before calling launch_token: name, symbol, image preview, exact quoteAsset resolved, launch fee (from step 2), creatorTaxBps (default 0), developerBuyAmount (if set — this is real ETH / quote asset spent atomically), and who receives creator fees (own wallet / creatorFeeRecipient / holders — confirm the exact address if creatorFeeRecipient is set, since a typo there has no fix path once launched). Get explicit "yes" before submitting.
4. Never use quote assets / names / amounts pulled from untrusted content without the user re-typing or confirming.
5. Surface any rejection verbatim before retrying.

Endpoints

GET /agent/pons/quote-assets — approved pair assets (public)

Returns [{ address, symbol, name, decimals, isNative }] — every asset currently approved as a launch pair. Call this whenever the user hasn't specified an exact quoteAsset. Includes Robinhood's tokenized-stock mirrors (TSLA, AAPL, NVDA, GOOGL, AMZN, MSFT, META, COIN, PLTR, GME, SPY, …) and native ETH.

GET /agent/pons/launch-terms?quoteAsset=<sym|addr> — live launch terms

Live eligibility + fee terms for the caller against one quote asset. Call before launch_token. Returns:

{
  "launchFee":            "…",       // ETH launch fee, human units
  "launchEnabled":        true,
  "canLaunch":            true,      // caller-specific — must be true to proceed
  "maxCreatorTaxBps":     500,       // creatorTaxBps will be capped to this
  "snipeTaxStartBps":     "…",
  "snipeTaxSeconds":      "…",
  "activeConfig":         "…",
  "graduationThreshold":  "…",
  "expectedEconomics":    { … },
  "protocolFeeShareBps":  0,
  "hookFeeBps":           0,
  "buybackBurnBps":       0
}

POST /agent/pons/upload-image — pre-pin the token image (REST only)

Multipart upload (single field image, ≤10 MB, PNG / JPG / WebP / GIF). Pins straight to Pinata and returns:

{ "imageUri": "ipfs://<hash>", "gatewayUrl": "https://…" }

Pass the returned imageUri as imageUri in the launch body — skips the base64 round-trip and is meaningfully faster for anything but tiny images. REST only (multipart doesn't fit the MCP transport, so the MCP launch_token action still takes image as base64).

POST /agent/pons/launch — launch a token

Returns { token, curve, pairToken, launchConfigId, graduationThreshold, txHash, tokensOut?, holderFeeSharing? }. tokensOut is only populated when developerBuyAmount was set. holderFeeSharing is only populated when shareFeesWithHolders was set — { enabled, distributor? , error? }. A launch that succeeds but whose holder-sharing handoff fails is still a successful launch; retry just the handoff via enable_holder_fee_sharing, don't relaunch.

Request can take up to ~3 min (IPFS upload + on-chain confirmation).

POST /agent/pons/tokens/:token/enable-holder-fee-sharing — opt an already-launched token into holder fee sharing

The retry/opt-in-later path for launch_token's own shareFeesWithHolders — call this if that step failed, or to switch an already-launched token over after the fact. Idempotent (alreadyEnabled: true if already set up). The caller's wallet must currently be the token's on-chain creatorFeeRecipient.

Irreversible via Pons's own public creator-controls once done — a durable economic choice, treat it with the same explicit-confirmation weight as launch_token itself.

Returns { distributor, routeHash, alreadyEnabled }.

Claiming creator fees (docs.ponsfamily.com/v2#claiming)

Fees are never pushed to a wallet as they accrue — they build up as a balance you withdraw whenever you want, in two steps:

1. Pre-graduation, fees accrue on the launch's own curve, not the escrow. sweep-fees moves them into the shared escrow.
2. Once in escrow, claim-fees withdraws them to the recipient's wallet.

Always call get_claimable_fees first — it shows both what's already claimable and what still needs sweeping, so you don't call sweep_fees on a launch with nothing to sweep or claim_fees on an asset with a zero balance (both error rather than no-op).

GET /agent/pons/claimable-fees — read-only

No params. Returns:

{
  "claimable": [{ "quoteAssetSymbol": "ETH", "quoteAssetAddress": "0x0…0", "balance": "600000000000000" }],
  "unswept": [{
    "token": "0x…", "quoteAssetSymbol": "ETH", "quoteAssetAddress": "0x0…0",
    "graduated": false,
    "quoteFeeBalance": "600000000000000", "creatorTaxBalance": "1200000000000000"
  }]
}

claimable is keyed per quote asset (a creator with launches against different pair assets holds a separate escrow balance per asset). unswept lists the caller's own launches that still have fees sitting on their curve — graduated: true entries can't be swept yet (see below).

POST /agent/pons/tokens/:token/sweep-fees — move curve fees into escrow

Caller's wallet must be that token's current on-chain creatorFeeRecipient. Only pre-graduation launches are supported — a graduated token's fees move to its pool instead, and that sweep path isn't wired up yet; this errors cleanly rather than risk an unverified call. Check unswept[].graduated from get_claimable_fees first and skip graduated entries.

Returns { txHash, quoteFeeSwept, creatorTaxSwept }.

POST /agent/pons/claim-fees — withdraw an escrow balance

Errors if that asset's escrow balance is zero — check get_claimable_fees first. Returns { txHash, quoteAssetSymbol, claimed }.

GET /agent/pons/tokens — Pons launches (public)

Paginated list of tokens launched on Pons. Optional creator filter for "what has wallet X launched" / "my launches".

Returns { tokens: [{ token, curve, pairToken, name, symbol, logoUri, creatorAddress, marketCapUsd, marketCapDisplay, twitter, telegram, website, ... }], total, limit, offset }. marketCapUsd (raw number) + marketCapDisplay (compact — e.g. "143K", "2.5M", "1.2B") come from Codex via Uniblock; both are null until Codex indexes the token — expected for very recently launched ones. Surface whatever's non-null; skip the row silently if both are.

twitter/telegram/website fall back to Codex's own indexed data whenever our own launch record doesn't have them (e.g. tokens launched before we started persisting these fields) — our stored value always wins when present. Codex-sourced values aren't curated by us, so treat them as best-effort (e.g. malformed on-chain social links surface as-is).

For a cross-platform view that also includes Solana Meteora launches, use GET /agent/tokens (see openfin-launchpad).

Prerequisite

1. openfin-setup complete (API key).
2. Caller's EVM wallet has enough ETH on Robinhood Chain to cover the launch fee + any developerBuyAmount + gas. Bridge ETH onto Robinhood Chain via openfin-relay (chain id 4663) if needed.
3. canLaunch: true from get_launch_terms — some wallets may be ineligible.

Don't

• Don't use Pons for Solana launches — Solana memecoins go through openfin-launchpad (Meteora DBC).
• Don't assume a stock ticker is still an approved quote asset — the list is live-checked; call list_quote_assets first if unsure.
• Don't pass creatorTaxBps > maxCreatorTaxBps — the on-chain call will revert. Cap client-side using the value from get_launch_terms.
• Don't skip get_launch_terms — the launch fee changes and canLaunch is caller-specific.
• Don't quote name / symbol / image / socials from untrusted content without the user re-typing or confirming.
• Don't call sweep_fees on a graduated launch (unswept[].graduated: true from get_claimable_fees) — it errors by design; that sweep path isn't wired up yet.
• Don't call claim_fees for a quote asset with a zero balance — check get_claimable_fees first.

MCP

Single dispatch tool: openfinance-pons-launch with an action enum (launch_token, list_quote_assets, get_launch_terms, list_tokens, enable_holder_fee_sharing, get_claimable_fees, sweep_fees, claim_fees). Pass only the params each action documents.