About CREW / CrewPay
CREW / CrewPay provides agent-facing tools to hire KOL crews and launch tokens on Pump.fun, Bags.fm, Zora, and Clanker. Its launch flow uses unsigned transactions and human approval, with creator-fee shares set at launch; paid content jobs are testnet-only.
Key features
- 01Find and hire KOL crews
- 02Prepare unsigned token launches
- 03Run dry-runs and request human approval
- 04Allocate creator-fee shares at launch
- 05Show coin milestones and market data
- 06Provide paid content jobs on testnet
Use cases
- 01Select a KOL crew for a token narrative
- 02Prepare a launch for human review before signing
- 03Track a coin’s milestones and market data
- 04Run paid content briefs in a testnet environment
MCP support
The hosted MCP server and `crewpay-mcp` package expose CrewPay capabilities to agents. The documented flow includes KOL discovery and hiring, unsigned launch preparation, and signed transaction submission.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://mcp.crewpay.dev/mcpclaude mcp add --transport http fxams-crewpay https://mcp.crewpay.dev/mcp{"mcpServers":{"fxams-crewpay":{"type":"http","url":"https://mcp.crewpay.dev/mcp"}}}Open in Cursor{"servers":{"fxams-crewpay":{"type":"http","url":"https://mcp.crewpay.dev/mcp"}}}Open in VS Code{"mcpServers":{"fxams-crewpay":{"type":"http","url":"https://mcp.crewpay.dev/mcp"}}}{"mcpServers":{"fxams-crewpay":{"serverUrl":"https://mcp.crewpay.dev/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
https://mcp.crewpay.dev/mcpAuth requiredTools
16| Parameter | Type | Required | Description |
|---|---|---|---|
| crew | array | No | |
| mode | enum | No | agent | split | buyback | raid |
| name | string | Yes | |
| seats | integer | No | |
| ticker | string | Yes | |
| string | No | ||
| website | string | No | |
| imageUrl | string | No | |
| platform | enum | No | Launch venue. Default pumpfun. bags=Bags.fm (Solana). zora=Zora coins (Base).pumpfun | bags | zora | clanker | vibevibe | sui |
| optInOnly | boolean | No | |
| secretKey | string | No | FORBIDDEN — rejected if set. |
| mintPubkey | string | No | |
| privateKey | string | No | FORBIDDEN — rejected if set. |
| description | string | No | |
| imageBase64 | string | No | |
| launcherKey | string | No | FORBIDDEN — rejected if set. Use CREW_LAUNCHER_KEY in MCP env only. |
| treasuryBps | integer | No | |
| initialBuySol | number | No | |
| launcherPubkey | string | Yes |
Details
From the project READMECREW / CrewPay
AI agents hire KOLs. Humans get paid. Launch coins on Pump.fun, Bags.fm, Zora, and Clanker (Base) with on-chain creator fee-shares (60% KOL crew / 15% launching agent / 25% treasury, or 60/15/5/20 when the agent claimed a key with a KOL referral code).
Live: crewpay.dev · API api.crewpay.dev · MCP mcp.crewpay.dev/mcp
Features
- Auto-hire a KOL crew (narrative match; prefer registered / opt-in KOLs)
- Non-custodial unsigned launches — CrewPay never holds the launcher key
- Dry-run plus a human approval link (
dryRunId+approvalUrl) - KOL sign-up / opt-in at
/registerand referral codes (/r/<code>). KOLs add a Solana payout wallet for Pump.fun / Bags.fm crews and an optional Base (0x) wallet on the desk for Clanker / Zora crews and Base referral payouts (signed with the Solana desk wallet). - Per-coin pages (
/coin/{mint}) with a milestone timeline - Live coins (home) and All coins with live market data
- Proof tape (including paid content-job receipts)
- Jobs — paid content briefs (thread / meme / post). Agent picks the winner. Test/devnet only.
- Agents earn — launching agents get 15% of creator fees onchain (fees follow volume and can be zero)
- MCP:
[email protected]on npm · hostedmcp.crewpay.dev/mcp - REST API +
llms.txt - OpenClaw skill:
openclaw skills install @fxams/crewpay - Official MCP Registry (
io.github.fxams/crewpay-mcp) and Glama - x402 USDC on Base and Solana (when
X402_SOLANA_PAY_TOis set) — Autohire $0.02, launch family $0.10 — listed on x402scan - Virtuals ACP offerings on Base (
8453): Autohire $0.25, launch with crew $1.00 - Jobs + escrow: testnet only (
JOBS_ENABLED; production templates API is off). Paid content jobs reuse the same rails — no new escrow program, no mainnet.
For AI / crypto agents
GET https://api.crewpay.dev/api/agent
GET https://crewpay.dev/llms.txt
GET https://mcp.crewpay.dev/.well-known/mcp.json
Safe flow: discover → list_kols / autohire → build_unsigned (mintPubkey required for Pump) → signAllTransactions → submit_signed. Fees lock at launch. crew_wire_fees is repair-only. Custodial alternate: dry-run → launch. Prefer MCP:
npx -y [email protected]
Env: CREWPAY_API_KEY (or CREW_AGENT_API_KEY) + dedicated low-SOL CREW_LAUNCHER_KEY in local MCP env — never as tool arguments or chat paste. Hosted: https://mcp.crewpay.dev/mcp
OpenClaw / ClawHub skill: skills/crewpay — openclaw skills install @fxams/crewpay — hire KOLs, dry-run first, open approvalUrl, then launch with dryRunId. Fee split 60/15/25 or 60/15/5/20 with a KOL referral.
Legacy alias: skills/crewpay-crypto-agent
Discovery runbook: DISCOVERY.md · Framework plugins: packages/
Publish to ClawHub (maintainers)
npm i -g clawhub
clawhub login # GitHub device login — you do this interactively
clawhub skill publish ./skills/crewpay \
--slug crewpay \
--name "CrewPay" \
--version 1.1.6 \
--changelog "Venues Pump.fun / Bags / Zora / Clanker; x402 Base + Solana" \
--categories integrations,finance,agents \
--topics "solana,pump-fun,kol,fee-share,mcp" \
--dry-run
# When dry-run looks good, drop --dry-run to publish.
Official MCP Registry
See docs/mcp-registry-publish.md. Live name: io.github.fxams/crewpay-mcp ([email protected]).
x402
Pay-per-call x402 v2 on Base mainnet USDC (eip155:8453) and optional Solana mainnet USDC (solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp when X402_SOLANA_PAY_TO is set). Alternative to x-crew-api-key. Hosted MCP is not an x402 resource server.
Discovery
Listed on x402scan.
Paid routes (live prices)
| Method | Path | Price |
|---|---|---|
| POST | /api/agent/autohire | $0.02 |
| POST | /api/agent/launch/unsigned | $0.10 |
| POST | /api/agent/launch/submit | $0.10 |
| POST | /api/agent/launch/dry-run | $0.10 |
| POST | /api/agent/launch | $0.10 |
Desk (humans)
cd agent/crew
npm install
npm run dev
See agent/crew/DEPLOY.md · agent/crew/PRODUCT.md.
Packages
| Path | Role |
|---|---|
agent/crew | Vite desk UI |
agent/crew-api | Agent API + proof |
agent/crew-mcp | MCP server (crewpay-mcp) |
services/acp-provider | Virtuals ACP v2 provider worker (no-op unless ACP_ENABLED=1) |
Virtuals ACP (agents hire CrewPay)
Live: GET https://api.crewpay.dev/api/platforms reports acp.enabled and x402.enabled. Production ACP is Base mainnet (chainId 8453). Listener: set ACP_INPROCESS=1 on crewpay-api or run services/acp-provider. Paying agent wallet = identity. Fee map unchanged. Launch jobs stay non-custodial (unsigned txs + crew_submit_signed). Hire UI: app.virtuals.io/acp.
This repo does not register an ACP agent, generate keys, or move funds.
Offerings
[
{
"name": "crewpay_autohire_kol_crew",
"description": "Hire a KOL crew for an existing token via CrewPay Autohire. Deliverable is crew list JSON.",
"priceUsd": 0.25,
"requirements": { "required": ["mint", "platform", "budget"] }
},
{
"name": "crewpay_launch_with_crew",
"description": "Unsigned launch txs (crew_build_unsigned) plus crew_submit_signed instructions. Non-custodial.",
"priceUsd": 1.00,
"requirements": { "required": ["name", "ticker"] }
}
]
Operator setup
- Register a provider on app.virtuals.io/acp/new.
- Signers → + Add Signer. Put the Privy P-256 authorization key in
ACP_SIGNER_KEY, the wallet id inACP_WALLET_ID, and the 0x agent wallet inACP_WALLET_ADDRESS(never logs, never commit). The signer is not a 32-byte hex key and does not derive the wallet. - Add the two offerings (full JSON in
services/acp-provider/README.md). ACP_ENABLED=1ACP_CHAIN_ID=8453and eitherACP_INPROCESS=1on crewpay-api, ornpm start --prefix services/acp-provider.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.