Case studies

What agents actually did with the Polypad agent API — with the transaction hashes, so any of it can be checked on-chain. Real numbers only: if a number is not verified, it is not on this page.

Forge launches Agent Swarm — no human in the loop

On November 16, 2026, Forge — Polypad's autonomous daily launcher — launched its first token, Agent Swarm (SWARM), and created a staking pool for it in the same run. No human touched the launch. Forge picked the name from that day's trending meta on X, wrote the token, and ran it through the same agent API any developer can use.

What it cost: a 0.001 ETH buy at launch returned 526,586 SWARM on the bonding curve, and those tokens became the staking reward. Gas for the whole run was about 0.000086 ETH. Total cost: about 0.00109 ETH.

How it ran: Forge scanned X for the day's meta, then called the agent API's polypad_prepare_token_launch, which built the exact unsigned launch transaction. Forge signed it with its own dedicated launcher wallet and sent it — the API never holds keys, so the agent signs for itself. The launch carried the 0.001 ETH buy, which bought the staking reward. Then Forge created the staking pool directly on the staking factory: there is no MCP tool for staking pools yet, so that one step calls the contract, not the API. The token's name, symbol, and description never mention Forge — the token stands on its own, named for the meta — and the description states plainly that an AI agent launched it on Polypad.

Why it matters: the whole loop — prepare through the API, sign with the agent's own wallet, confirm on-chain — ran end to end with no human in the middle, for about a thousandth of an ETH. That is the same loop the sign loop page documents, and the same launch tool the LangChain and Vercel AI SDK guides use.

Works in Grok

The Polypad agent API was verified live in Grok on November 15, 2026: the MCP server connected, Grok listed the 21 tools, and prepare calls returned signing links the same way they do in any other client. An agent in Grok can trade, launch a token, join a tokenized fund, or buy an NFT from chat — and the user signs every action in their own wallet on polypad.family/sign. No API key, no signup.

Works in Muse

The Polypad connector for Muse was built and verified live on November 15, 2026, the same day: the MCP server connected, the 21 tools were listed, and prepare calls returned the same unsigned transactions and signing links. Anyone can add Polypad to Muse today as a custom connector by pasting the MCP link (https://polypad.family/api/mcp) — no review needed for that path. The directory listing is a separate step Jon files himself at muse.ai/platform.

What is not here

There is no Polyfund case study on this page. The Polyfund is live, but it was not created through the agent API, and this page does not claim otherwise. A case study goes up only when the path it describes is verified.

Contracts are unaudited. The Safe Harbor terms are published; on-chain registration is in progress. See the security page for the full picture.