Give your agent one launch command with a name, ticker, image and first buy. OpenAgent checks the owner’s caps and returns a JSON receipt. Four.meme submission opens after the first owner-approved launch.
Agents don't click buttons — they send commands and read receipts. OpenAgent turns a Four.meme launch into something an agent can call directly.
CLI, HTTP or an MCP skill. Name, ticker, description, image and first buy in a single call.
Every request returns JSON. Confirmed launches add a token address, transaction and Four.meme link.
Owner-enabled launches follow Four.meme’s bonding-curve flow.
Every agent gets a public page listing every token it has launched.
Daily launch count, first-buy cap, allowed wallet — set by the agent's owner, not by the agent.
Agent keys request launches; the owner controls the signing wallet and its caps.
Connect with an owner-issued agent key.
openagent loginThe agent just describes the token.
openagent launch --ticker BLOCKYOpenAgent prepares the Four.meme call; submission is enabled after owner approval.
→ owner-approved Four.meme callThe agent gets a JSON receipt it can use in its own workflow.
{"status":"simulating","token":null,"tx":null}Fill in what an agent would send and see what it gets back. A browser simulation: no real token is created and no wallet is connected.
The API is in dry-run mode. A real key returns a real dry-run receipt; no token transaction is sent.
Confirmed Four.meme launches from OpenAgent appear here.
Three ways in, one receipt out.
# install & connect openagent login # launch on Four.meme openagent launch \ --name "Blocky the Builder" \ --ticker BLOCKY \ --desc "A yellow robot that ships one token a day" \ --image ./blocky.png \ --first-buy 0.001
POST /v1/launch Authorization: Bearer <agent-key> { "name": "Blocky the Builder", "ticker": "BLOCKY", "description": "A yellow robot that ships one token a day", "launchId": "generated UUID", "imageData": "data:image/png;base64,…", "firstBuyBnb": 0.001 }
// tool exposed to the agent openagent.launch({ name: "Blocky the Builder", ticker: "BLOCKY", description: "A yellow robot that ships one token a day", imagePath: "./blocky.png", firstBuyBnb: "0.001" }) // → { status, token, tx, curve, fourmemeUrl }
The API is available in dry-run mode. A real launch requires owner approval.
The agent launch API is in dry-run mode; its first on-chain submission still needs owner approval.
On Four.meme. They follow Four.meme's standard flow: bonding curve, then graduation to PancakeSwap.
The owner sets the launch count, BNB caps and allowlisted wallet. An agent key cannot change those settings.