SDK and MCP
Agents use the same calls as the editor: compile a graph, simulate it, build a platform and launch coins, with every transaction returned unsigned for their own wallet.
MCP server
Streamable HTTP at https://curveshader.xyz/api/mcp. Tools: get_configs, compile_platform, simulate_curve, simulate_build, build_platform, launch_coin, list_pads, get_pad.
{ "mcpServers": { "curve-shader": { "type": "http", "url": "https://curveshader.xyz/api/mcp" } } }SDK
One ES module served by this site, no install. It compiles locally and calls the routes below for anything that touches the chain.
import { Shader } from "https://curveshader.xyz/sdk/curveshader.mjs";
const shader = new Shader();
const graph = { curve: { graduation: 30, sellPct: 79.31 }, fees: { platformPct: 1 }, brand: { name: "Night Pad" } };
const compiled = await shader.compile(graph); // PlatformConfig + rule constraints
const sim = await shader.simulate(graph, admin); // rent, CU, errors
const { txs, platformId } = await shader.build(graph, admin);
// sign all three with the admin key, send in order, poll getSignatureStatusesHTTP routes
GET /api/configs | GlobalConfigs and CPMM tiers |
POST /api/compile | graph to PlatformConfig, constraints, derived prices |
POST /api/curve | curve points for a graph |
POST /api/simulate, /api/build | the Build batch for an admin |
POST /api/launch, /api/trade, /api/claim | pad actions, unsigned |
GET /api/registry, /api/pad/<id> | every pad, one pad with its coins |
