CREW / CrewPay

Registre officiel Autres

Unsigned Pump/Bags/Zora/Clanker launches. mintPubkey required. Fees lock at launch.

Que pouvez-vous faire avec CREW / CrewPay ?

  • 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 /register and 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 referra...
  • 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.

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code
claude mcp add --transport http crew-crewpay 'https://mcp.crewpay.dev/mcp' --header 'x-crew-api-key: <crew_ak_… from crew_claim_key / POST /api/agent/keys/claim (required for writes). Hosted MCP is publicMode and cannot hold a launcher secret.>'
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "crew-crewpay": {
            "type": "http",
            "url": "https://mcp.crewpay.dev/mcp",
            "headers": {
                "x-crew-api-key": "<crew_ak_… from crew_claim_key / POST /api/agent/keys/claim (required for writes). Hosted MCP is publicMode and cannot hold a launcher secret.>"
            }
        }
    }
}
NPM package crewpay-mcp
Claude Code
claude mcp add crew-crewpay -e 'CREW_AGENT_API_KEY=<your crew_agent_api_key>' -e 'CREW_LAUNCHER_KEY=<your crew_launcher_key>' -e 'CREW_API_URL=<CREW_API_URL>' -e 'CREWPAY_REFERRAL_CODE=<CREWPAY_REFERRAL_CODE>' -e 'X402_EVM_PRIVATE_KEY=<your x402_evm_private_key>' -- npx -y crewpay-mcp@1.2.14
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "crew-crewpay": {
            "command": "npx",
            "args": [
                "-y",
                "crewpay-mcp@1.2.14"
            ],
            "env": {
                "CREW_AGENT_API_KEY": "<your crew_agent_api_key>",
                "CREW_LAUNCHER_KEY": "<your crew_launcher_key>",
                "CREW_API_URL": "<CREW_API_URL>",
                "CREWPAY_REFERRAL_CODE": "<CREWPAY_REFERRAL_CODE>",
                "X402_EVM_PRIVATE_KEY": "<your x402_evm_private_key>"
            }
        }
    }
}

Variables d'environnement

  • CREW_AGENT_API_KEY obligatoire secret crew_ak_… from crew_claim_key / POST /api/agent/keys/claim, or operator key
  • CREW_LAUNCHER_KEY secret Dedicated low-SOL burner Solana secret for launch/wire/lock (local env only — never a tool arg). Not used by hosted remote.
  • CREW_API_URL API base URL (default https://api.crewpay.dev)
  • CREWPAY_REFERRAL_CODE Optional KOL referral code used by crew_claim_key when referral_code arg omitted
  • X402_EVM_PRIVATE_KEY secret Optional hex private key for Base USDC x402 pay-per-call (alternative to CREW_AGENT_API_KEY). Local env only — never a tool arg. Not used by hosted remote.

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. CREW / CrewPay
  2. Features
  3. For AI / crypto agents
  4. x402
  5. Desk (humans)
  6. Packages
  7. Virtuals ACP (agents hire CrewPay)

CREW / 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 /register and 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: crewpay-mcp@1.2.14 on npm · hosted mcp.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_TO is 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 crewpay-mcp@1.2.14

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 (crewpay-mcp@1.2.14).

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)

MethodPathPrice
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

PathRole
agent/crewVite desk UI
agent/crew-apiAgent API + proof
agent/crew-mcpMCP server (crewpay-mcp)
services/acp-providerVirtuals 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
  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=8453 and either ACP_INPROCESS=1 on crewpay-api, or npm start --prefix services/acp-provider.

Questions fréquentes

Qu'est-ce que CREW / CrewPay ?

Unsigned Pump/Bags/Zora/Clanker launches. mintPubkey required. Fees lock at launch.

Comment installer CREW / CrewPay ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http crew-crewpay 'https://mcp.crewpay.dev/mcp' --header 'x-crew-api-key: <crew_ak_… from crew_claim_key / POST /api/agent/keys/claim (required for writes). Hosted MCP is publicMode and cannot hold a launcher secret.>'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour CREW / CrewPay ?

Oui. Il attend CREW_AGENT_API_KEY, CREW_LAUNCHER_KEY, X402_EVM_PRIVATE_KEY, x-crew-api-key, à renseigner dans sa configuration.

CREW / CrewPay est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient CREW / CrewPay ?

Il est publié par fxams. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.