How it works.

Ask for your wallet and the bot creates one mapped to your handle, or gives you the same address back if you already have one. The reply links to its public page, where anyone can check the address and its holdings.

• No wallet address goes in your post - the handle is the account
• The same handle always resolves to the same wallet
• The private key stays exportable, on request, from day one

Ask for the CA of any token launched through JellyPons and the bot replies with the address and a link to its page. It answers for our launches only — if we did not deploy it, it says it has no record rather than printing an address it cannot vouch for.

• Name a ticker with or without the leading $
• If two launches share a ticker, both are shown and you choose
• A read, not a transaction — nothing is signed and nothing is spent

Name the token and an amount in dollars, in ETH, or in the pool’s own paired asset. If a dollar or ETH purchase needs a different pair, the bot acquires that asset first and reports one final result rather than two half-finished ones.

• Amounts as $25, 0.02 ETH, or an exact paired amount such as 5 MSFT
• Paired-asset funding is handled for you in the same request
• Buy and send in one post - only the tokens from that purchase move on

Name the token and say how much: an exact token amount, a dollar value, an ETH value, a percentage, half, or all. The reply confirms what you actually received, not what was quoted.

• 10 $JELLY, $25 of $JELLY, or 0.001 ETH of $JELLY all parse
• Percentages, half and all are understood
• The token can be named by contract address instead of ticker

Swap a dollar value of one token into another. Use the explicit form below so the source and destination are never ambiguous - the bot takes a direct paired route when one exists and otherwise routes through ETH.

• Write it as: swap $25 of ETH to USDG
• Tickers or full contract addresses, either side
• Keep enough ETH for gas on every hop the route needs

Send ETH or a token to an X handle or a wallet address. Include the amount, the asset and the destination. A combined buy-and-send moves only the tokens that purchase produced.

• An @username or a complete 0x address as the destination
• Exact amounts, percentages, half and all are supported
• A combined buy and send handles one token and one recipient

Burning sends tokens to the burn address, permanently. Name the token and the amount, or ask explicitly for a buy-and-burn to destroy only what that purchase produced.

• Burns cannot be undone - read the amount twice
• A combined action must contain both words, buy and burn
• The reply carries both hashes when it is two steps

Creator fees are credited in each launch’s paired asset. Ask to claim everything, or name one launch. The bot confirms the amount from the on-chain event rather than from its own arithmetic.

• Say claim my fees for everything the combined workflow covers
• Name a ticker to claim only that launch
• Launches paired against something other than ETH are claimed one at a time

A name and a ticker are all that is required. Artwork, description, website, X account, Telegram link, pairing asset and a developer buy are all optional. Dollar or ETH dev buys are converted into your chosen pair first.

• Attach your artwork to the post, or launch without it
• Add a website, an X account or a t.me/… link to be shown on the token page
• Pick ETH or another supported pair; add dev buy $100 or dev buy 0.02 ETH

Ask for the current pairing list before you launch. Robinhood Chain carries tokenised equities, so a token can be paired against something other than ETH - and the list changes.

• One pair per launch, chosen at creation and fixed afterwards
• Contract approval is checked at the moment the launch is requested
• Ask again before launching; the published list is not frozen