> feebeam api

> route creator fees to any x, github or twitch account.

> no key, no auth, plain json.

quickstart

curl "https://feebeam.xyz/api/v1/socials/resolve?platform=x&username=someuser"

{ "wallet": "0x9b6a...f335" }

> one call turns a handle into a wallet you can pay fees to — the rest of this page is detail.

how it works

a handle becomes a wallet, the owner claims it

[1]
resolve a handle
you call resolve with a platform and a username. feebeam verifies the account exists and returns a wallet address for it.
[2]
the wallet is keyed to the account
if the account has never been seen before, an embedded wallet is created on the spot — secured by Privy and keyed to the platform's native user id, so renames don't break it. it's non-custodial: feebeam holds no funds.
[3]
the owner logs in and claims
whenever they like, the account owner signs in on feebeam with that same x, github or twitch account and collects everything their wallet has earned.

api reference

endpoints

> base url https://feebeam.xyz. everything returns json, needs no authentication, and sends Access-Control-Allow-Origin: * so you can call it straight from a frontend. please cache responses where you can.

GET/api/v1/socials/resolve?platform={x|github|twitch}&username={handle}

> resolves a social account to its wallet — the same resolution feebeam uses at launch. if the account has never been seen before, an embedded wallet is created for it (secured by Privy, claimable by the account owner via OAuth login). use it to route fees, airdrops or payouts to any social account.

curl "https://feebeam.xyz/api/v1/socials/resolve?platform=x&username=someuser"

{
  "verified": true,
  "username": "someuser",
  "userId": "2094063734041743360",  // platform-native user id
  "platform": "x",
  "wallet": "0x9b6a...f335",
  "walletCreated": true
}

GET/api/v1/tokens

> lists every token launched through feebeam, newest first, with market data.

curl https://feebeam.xyz/api/v1/tokens

{
  "tokens": [
    {
      "mint": "0x1234...abcd",
      "name": "Example",
      "symbol": "EXMPL",
      "imageUri": "https://gateway.pinata.cloud/ipfs/...",
      "createdAt": 1788100000000,
      "creator": { "wallet": "0x...", "username": "someuser", "type": "x" }
    }
  ]
}

GET/api/v1/tokens/{address}

> full detail for one token: metadata, tagged beneficiaries, and live market data.

curl https://feebeam.xyz/api/v1/tokens/0x1234...abcd

{
  "mint": "0x1234...abcd",
  "name": "Example",
  "symbol": "EXMPL",
  "beneficiaries": [
    { "type": "x", "value": "someuser", "walletAddress": "0x...", "percentage": 100 }
  ],
  "priceUsd": 0.0000189,
  "usdMarketCap": 18900,
  "graduated": false,
  "graduationProgress": 37.5
}

POST/api/v1/register

> registers a launched token with feebeam so it gets a page, a live chart and the fees → @handle attribution. registration is trustless: name, ticker, image and socials are re-read on-chain, and beneficiaries are only accepted if they match the on-chain fee recipient — a spoofed body cannot fake any of it.

curl -X POST https://feebeam.xyz/api/v1/register \
  -H "Content-Type: application/json" \
  -d '{
    "mint": "0xYourTokenAddress",
    "beneficiaries": [{
      "platform": "x",
      "username": "someuser",
      "walletAddress": "0xAbc...123"
    }]
  }'

for launch platforms

add social fee routing to your launcher

> if you run a launch tool, a trading terminal or a bot, you can offer social fee routing with two api calls — no key, no contract changes on your side. your users type a handle, feebeam turns it into a wallet, you launch as usual.

[1] resolve the handle into a wallet

works for any existing x, github or twitch account — the wallet is created on the spot if needed.

curl "https://feebeam.xyz/api/v1/socials/resolve?platform=x&username=someuser"
// → { "verified": true, "wallet": "0xAbc...123", ... }

[2] launch with that wallet as the fee recipient

pass the resolved wallet as creatorFeeRecipient in your usual launch call. the launch itself happens through pons v2 — see the pons v2 docs for protocol-level details. the recipient is written into the contract at launch and can never be changed; from the first trade, the creator tax accrues to the account's wallet.

[3] (optional) register the token with feebeam

call POST /api/v1/register (above) and the token gets a feebeam page, explore listing and claim visibility for the tagged account. the claim flow is fully handled by feebeam — the tagged account logs in with their social account and collects, without ever needing to know which tool launched the coin.

fee model

100% to the tagged account

> whoever launches a coin sets a creator tax between 0% and 10% — fixed at launch, never changeable afterwards. on every trade, the tagged x, github or twitch account receives 100% of that tax in its wallet. feebeam charges nothing.

> building an integration? reach out through the support page — we're happy to help, add endpoints, or list your platform.