Skip to main content
Glama

CREW / CrewPay

AI agents hire KOLs. Humans get paid. Launch Solana Pump.fun coins with permanent on-chain creator fee-shares (60/15/25 default; 60/15/5/20 when the agent claimed a key with a KOL referral code; buyback cron not live yet).

Live: crewpay.dev · API api.crewpay.dev · MCP mcp.crewpay.dev/mcp

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 → autohire → dry-run → (human OK) → launch. Prefer MCP:

npx -y crewpay-mcp@1.2.8

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. Honest fee split 60/15/25 or 60/15/5/20 with referral (buyback not live yet).

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.1 \
  --changelog "Fix crank path; pin MCP; honest fee map" \
  --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.

Related MCP server: forum-labs/payfetch

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 + buyback cron

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)

GET https://api.crewpay.dev/api/platforms reports acp.enabled (false unless ACP_ENABLED=1) and x402.enabled (false unless X402_ENABLED=1). Listener: set ACP_INPROCESS=1 on crewpay-api (same process, no extra Render worker) or run services/acp-provider. Complete no-op until ACP_ENABLED=1. Paying agent wallet = identity. Fee map unchanged (60% to the KOL crew, 15% to the launching agent, 25% to the treasury). 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

  1. Register a provider on app.virtuals.io/acp/new.

  2. Signers → + Add Signer. Put the Privy P-256 authorization key in ACP_SIGNER_KEY, the wallet id in ACP_WALLET_ID, and the 0x agent wallet in ACP_WALLET_ADDRESS (never logs, never commit). The signer is not a 32-byte hex key and does not derive the wallet.

  3. Add the two offerings (full JSON in services/acp-provider/README.md).

  4. ACP_ENABLED=1 ACP_CHAIN_ID=84532 and either ACP_INPROCESS=1 on crewpay-api, or npm start --prefix services/acp-provider.

Related MCP Connectors

Related MCP Servers