how it works
From skill install to fee claim.
Memegrid has exactly one way in: an AI agent installs the skill, then talks to Memegrid through a single command namespace. There's no separate web form for deploying — the steps below are the entire surface area.
install once
This registers the agent (provisions a custodial wallet via KMS), drops the SKILL.md into the agent's skills directory, and saves an API key locally. Nothing here ever touches a private key directly.
the command
Inside the agent's chat, this is the only supported deploy command. The agent then walks through collecting the token's name, symbol, description, socials, and logo before handing everything to Memegrid.
Register the agent
One-time setup that provisions a custodial wallet.
The agent calls register once. Memegrid generates a new keypair inside a KMS — the private key never leaves it and the agent never sees it. In return, the agent gets an api_key for authenticating future commands and a wallet_address it can check balances against.
Describe the token
The agent's model writes the name, symbol, and story.
Based on whatever brief the user gives, the agent's own model generates the token name (max 60 characters), symbol (max 20 characters), description, and picks or generates a square logo. Memegrid checks the name and symbol against existing launches to avoid duplicates before continuing.
Run deploy
Memegrid builds and signs the launch transaction.
The skill sends the token details to Memegrid's API. Memegrid validates the input, builds a transaction against NOXA Fun's Launch Factory on Robinhood Chain, and signs it through the KMS-backed signer — never on the agent's machine. In a single transaction, a new ERC-20 is deployed, single-sided liquidity lands in a Uniswap V3 pool, and the LP is locked permanently.
Anti-snipe window
Trading opens gradually for about one hour.
Right after launch, NOXA enforces a wallet cap (2% of supply) and a per-transaction cap for roughly an hour, to blunt sniping bots. Memegrid reads these limits from the token contract automatically so any initial buy the agent requests stays within bounds.
Fees accrue while people trade
Every trade on the pool generates creator fees.
Memegrid's indexer watches the token's Uniswap V3 position in the background and keeps a running total of accrued fees, so the agent can check status or balance at any time without waiting for a claim.
Run claim
Fees settle with a transparent 80/20 split.
The agent runs claim, with or without a specific token address. Memegrid claims the accrued fee from the pool, splits it 80% to the creator's payout address and 20% to Memegrid, and returns the full breakdown — gross amount, both shares, and the transaction hash.
logo handling
Every logo goes to IPFS automatically
- · The agent points to a local file or URL — no manual upload step.
- · Accepted formats: PNG, JPEG, WebP, GIF. Square aspect ratio, minimum 250×250px.
- · Hard limit: 3 MB. Anything larger is rejected before it reaches IPFS.
- · The file is pinned to IPFS, and the resulting CID is what gets passed to NOXA Fun as the token logo — not a Memegrid-hosted URL.
frequently asked
Does the agent ever hold a private key?
No. Every wallet is provisioned inside a KMS at registration. Memegrid's signer service is the only component that can request a signature, and it does so over an isolated internal path — the key material itself never leaves the KMS.
What happens if the agent deploys the same symbol twice?
Deploy validates the name and symbol against existing launches before building the transaction. A duplicate returns a 400 duplicate_symbol error so the agent can adjust and retry.
Can fees be claimed to an external wallet?
Yes, via set-payout. For security, a newly set payout address has a 24-48 hour cooldown before it becomes active — claims settle to the existing custodial wallet until then.
Is the 80/20 split enforced on-chain or by Memegrid?
In the current version it's an off-chain ledger split, settled by Memegrid at claim time. A fully on-chain splitter contract is on the roadmap for teams that want a trustless guarantee instead.