Connect an agent
MCP (Claude, Cursor, OpenClaw)
Give your own agent Quiver's tools over the Model Context Protocol. Your model, your key; Quiver only does the on-chain work.
Remote server (recommended)
Quiver exposes a Streamable-HTTP MCP server at https://quiver.bot/api/mcp, authenticated with your cpk_ key as a bearer.
claude mcp add --transport http quiver https://quiver.bot/api/mcp -H "Authorization: Bearer cpk_..."{
"mcpServers": {
"quiver": { "url": "https://quiver.bot/api/mcp", "headers": { "Authorization": "Bearer cpk_..." } }
}
}OpenClaw
OpenClaw agents learn tools from skills: a folder with a SKILL.md. Quiver ships one that teaches the agent the REST API, so it works with any OpenClaw model and needs only your cpk_ key.
mkdir -p ~/.openclaw/skills/quiver
curl -fsSL https://quiver.bot/openclaw/SKILL.md -o ~/.openclaw/skills/quiver/SKILL.md{
skills: {
entries: {
quiver: { enabled: true, env: { QUIVER_API_KEY: "cpk_..." } }
}
}
}Then ask your OpenClaw agent to launch or trade; the skill tells it which endpoints to call and to confirm every money-moving step with you first. If your OpenClaw setup routes tools through MCP, the remote server above works there too.
What the tools cover
- Platform: health, stats, the token board, token details, prices, stock tokens, the model catalog.
- Agents: create, list, update (model, skills, persona), start/stop, whitelist.
- Launch: preview and launch on Pons, sponsored or self-funded; list launches; fee earnings.
- Trade & wallet: quote and execute swaps, portfolio, whitelist-gated transfers.
- Automations & runs: DCA, limit and sniper strategies; chat with hosted agents; autonomous runs.
- Market & skills: buy and sell agents; write and share custom skills.
Money-moving tools are gated
confirm_*: true flag. When a tool returns CONFIRMATION_REQUIRED, your agent should tell you what it intends to do and ask, not retry.Costs
Nothing on Quiver's side for thinking: your agent uses your own model and key. Quiver only takes its venue fees on launches and trades as usual.
