Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
docs(finish): retire order 956 after verifying funded launch intents, pairs, tests and docs are shipped
nirholas5d2d6e817cf8
diff --git a/prompts/finish/956-pump-self-funded-launch-and-pairs.md b/prompts/finish/956-pump-self-funded-launch-and-pairs.mddeleted file mode 100644index 190188cf9..000000000--- a/prompts/finish/956-pump-self-funded-launch-and-pairs.md+++ /dev/null@@ -1,9 +0,0 @@-Launching is session-signed and the x402 route is pay then launch. What is missing is the developer-friendly path where an agent funds its own launch: ask for a quote, pay the exact quoted amount from the agent wallet within a validity window, then retry with the payment proof, safely idempotent so a timeout never charges twice. Also missing: a list of supported pairs and the creator fee range, so a launcher can choose.--Build GET /api/pump/pairs returning the supported quote assets (SOL, USDC and the stable pairs api/_lib/pump-quote.js already classifies) with their live status and the allowed creator-fee range read from config. Build the quote flow: a launch intent with name, symbol, description, image, quote asset, initial buy and creator fee returns a quote with every fee line and its expiry; payment from the agent wallet is a gated spend (recipient, amount, asset, chain, explicit yes) and the proof (transaction signature plus a preflight token) is accepted once and replays the same result. Honour the repo rule that launching signs only from a same-site session: the funding and the final launch confirmation happen in the browser or approval flow, and the CLI or API only creates the intent and polls. No bearer token can sign a launch.--Let the creator pick the creator-fee bps within the range and show what that does to earnings. Return a launch status endpoint with stages (quote, paid, submitted, confirmed, indexed). Dry-run test against a launch lane that never touches mainnet; real launches are the owner's action.-------This brief is standalone. Assume no other brief has run, and keep working if others run at the same time: use names unique to this work for tables, routes and files, give migrations a fresh timestamp, append to shared files instead of rewriting them, and re-read a shared file before you edit it. CLAUDE.md governs everything, including its spend gate (anything that signs or moves funds shows recipient, amount, asset and chain and waits for an explicit yes; test with devnet, simulation or paper mode) and the rule that nothing naming another crypto project is committed without the owner's approval, so list any new third-party names you introduce in your report. Never name any competitor in a committed file. Finish it fully: wire it, document it, add the changelog entry, verify it for real, and report what you observed.