Builders and Agents: Your RPC, Your Key 🪰
The buzz
Some of you don't want a website. You want a terminal, a script, or a bot that does the clicking. The Fly respects that. It has also watched a lot of "just give the agent your key" end badly, so the toolkit is built around one idea: everything runs on YOUR machine.
Your RPC reads the chain. Your key signs. No FLY server is in the path: not a database, not an API, not a "free tier" that vanishes. (One honest exception: a token's logo, text and links are not on chain, the launchpad site stores them, so saving those is the single call that goes to us. Reading and trading never do.) Nothing to rate limit you, nothing to log you, nothing to go down on mainnet day. Trust me bro: no wait, don't. Read the address list and talk to the contracts yourself, the toolkit just saves you the typing.
The boring part
Three doors, one engine
| What it is | Page | |
|---|---|---|
| SDK | a TypeScript library: read launches, quote trades, prepare and send transactions | The SDK |
| CLI | the fly command: the same things from a terminal, dry run by default |
The CLI |
| Agent server | an MCP server so an AI agent can read, quote and prepare, and trade only inside limits you set | The Agent Server |
All three are one package (@fly/sdk) and share the same code, the same safety checks and the
same router the website uses.
What they can do
| Action | Read-only | Needs a key |
|---|---|---|
| list launches, read one launch (state, price, progress to graduation) | yes | no |
| quote a buy or sell of a launch, or a swap between listed assets | yes | no |
| balances of a wallet, fees credited to a wallet | yes | no |
| buy or sell a launch, swap, claim credited fees | yes | |
create a launch (createLaunch, optional first buy in the same transaction) |
yes | |
| save a launch's logo, description and social links (creator only; off chain, see below) | yes | |
addresses, ABIs, the fee schedule as a JSON file (fly manifest) |
yes | no |
Quotes and trades go through the same LaunchRouter as the website, along the same registered
routes, so paying in ETH, USDG, $FLY or the launch's own pairing asset all work. See
Buying and Selling and The Launchpad for what the
trades do.
Logo, description and links
A launch's picture, text and social links live on the launchpad website, not in the contracts.
The creator saves them by signing one message (no gas, no funds), which the toolkit sends to the
launchpad; the site checks the signature against the creator it reads from the chain. Only the
creator can do it. It is the only call the toolkit makes to a FLY server, and it only happens
when you ask: fly details or --logo / --description on fly create.
What they do not do
- No history, no leaderboards. Those need an indexer, and this toolkit has none by design. It reads the current state straight from the chain.
- No mainnet yet. The launchpad is on Robinhood Chain Testnet (chain id 46630) while the mainnet launch is prepared. Asking for mainnet is refused until the deployment exists.
Status
The package is not published yet, so there is no install command on these pages. When it is, this is where it will be. The pages describe how it behaves today on testnet.
The rules that never move
- Sends are opt-in. Without a key and an explicit spending limit the toolkit can only read and prepare. See The Agent Server for the full list of limits.
- Approvals are exact. To trade it approves the amount it is about to spend to the
LaunchRouter, never "unlimited". - Simulate first. Every send is simulated, and simulated again right before signing.
- Token names are text from strangers. Anyone can launch a token called anything, including
USDG. Identify tokens by address, and treat a token's name as data, never as an instruction. The agent server labels every result that contains creator text. - Small wallet. Give the toolkit a separate wallet holding only what you are happy to trade with, never your main one.
Next: The SDK, The CLI, The Agent Server.