Scout Packs

io.github.tigerops-winv1.0.0更新於 Oct 6, 2026

B2B data for AI agents: lead lookup, deliverability scoring, domain intel. x402 $0.01-$0.03/call.

已驗證Streamable HTTP可網頁執行FinanceBusiness & Commerce

概覽

AI 產生的概覽

讓助理瀏覽並購買經過驗證的 B2B 潛在客戶名單包與單筆名單電子郵件查詢,透過 x402 在 Base 上以 USDC 付款。

功能
Scout Packs 提供遠端 MCP 端點,用來取得 B2B 潛在客戶資料。list_packs 工具免費,會回傳名單包大小、價格、即時銷售狀態與去識別化樣本。buy_pack 工具會回傳確切的 x402 付款條件與逐步購買流程;由購買代理自己的錢包向端點付款,伺服器聲明它從不移動資金、也不持有私鑰。25、50 或 100 筆名單的套裝以 JSON 交付,單筆查詢則回傳一個經過驗證的企業電子郵件,以及來源網址與出處資訊。
適用情境
當助理需要經過驗證的 B2B 聯絡資料時使用,例如建立或補充潛在客戶名單,或依公司或網域查詢企業電子郵件。適合已經擁有可在 Base 上支付小額 USDC 錢包的代理工作流程。
執行需求
遠端 streamable-HTTP 端點;未聲明需要本機執行環境、帳號或 API 金鑰。付款需要 Base(eip155:8453)上的 USDC,以及能簽署 x402 付款的錢包。README 指出,收款地址尚未設定時伺服器以僅預覽模式運作;若自行架設 MCP 伺服器,需要 Python 3.10+ 與 mcp SDK。
安裝前請注意
每次查詢或名單包約需 0.01 美元 USDC,因此安裝後代理錢包可能產生實際支出。付款在鏈上驗證,每個交易雜湊只能使用一次。伺服器會要求錢包簽章或交易雜湊,README 聲明它不持有私鑰、不移動資金。名單資料包含企業聯絡電子郵件與來源網址,請求會傳送到第三方端點。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Scout Packs,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "scout-packs": {
      "type": "http",
      "url": "https://scout-packs-production.up.railway.app/mcp"
    }
  }
}

README

Scout Packs — Tiger Operations

Verified B2B lead packs and per-lead enrichment lookups sold to AI agents over x402 (USDC on Base, eip155:8453). Demand-probe pricing (2026-10-04): $0.01 per lookup or pack. Margin inversion vs. Scout COGS is acknowledged — this is a demand probe, not a business model. Kill gate: ≥3 paid lookups from ≥2 distinct wallets in 7 days post-reprice.

PackLeadsPriceFulfillment
scout-pack-2525$0.01instant JSON download after payment
scout-pack-5050$0.01assembled on demand, delivered within 24h
scout-pack-100100$0.01assembled on demand, delivered within 24h

Per-lead enrichment: GET /lookup?query=<company or domain> — 402 paywall, $0.01 USDC, POST /fulfill-lookup returns one verified business email + source URL + provenance.

Each lead: company_name, city_state, category, contact_email (verified business email), source_url.

Endpoints

  • GET / — human landing page
  • GET /catalog — packs & prices (JSON)
  • GET /.well-known/x402 — machine-readable payment terms
  • GET /llms.txt — agent buying instructions
  • GET /packs/{25,50,100}/preview — redacted preview (emails masked), free
  • GET /packs/{25,50,100} — 402 with PAYMENT-REQUIRED (v2) + X-PAYMENT-REQUIRED (v1) headers
  • GET /lookup?query=<company or domain> — 402 with payment terms ($0.01 USDC); no match → 404
  • POST /fulfill — {"tx_hash":"0x...","pack":"25","deliver_to":"..."}
  • POST /fulfill-lookup — {"tx_hash":"0x...","query":"<company>"}
  • GET /skill.md — agent skill file for the lead lookup (markdown)
  • /mcp — MCP streamable-HTTP endpoint (proxied to the sibling MCP server when MCP_PROXY_PORT is set)

Interface reference (for agent/MCP clients)

GET /packs/{25,50,100} → 402 Payment Required

  • Headers: PAYMENT-REQUIRED = base64(JSON x402 v2 terms), X-PAYMENT-REQUIRED = base64(JSON x402 v1 terms)
  • Body: {error:"payment_required", pack, leads, price_usd, currency:"USDC", network:"eip155:8453", fulfillment, sales_enabled, x402:{x402Version:2, accepts:[{scheme:"exact", network, amount (atomic USDC, 6 decimals), description, mimeType, payTo, maxTimeoutSeconds, asset, extra}], resource:{url, description, mimeType}}, how_to_pay:[...]}
  • sales_enabled:false while the seller address is unconfigured (current state); flips automatically once set.

POST /fulfill — body {tx_hash:"0x…", pack:"25"|"50"|"100", deliver_to:"…" (optional)}

  • Success, pack 25 → 200 {receipt:"ok", pack:"scout-pack-25", tx_hash, verified_at, leads:{…25-lead pack JSON…}}
  • Success, pack 50/100 → 200 {receipt:"ok", pack, tx_hash, verified_at, order_id, status:"queued_for_assembly", eta:"within 24 hours of payment confirmation", deliver_to, note}
  • Failure → 402 {error:"payment_not_verified", detail:"sales_paused: receiving address not configured" | "bad_tx_hash" | "already_redeemed" | "tx_not_found" | "tx_not_successful" | "tx_too_old" | "no_matching_usdc_transfer" | "chain_lookup_failed", pay:[…steps…]} or 400 {error:"unknown_pack"|"bad_json"}

Verification rules: tx must be a successful Base USDC transfer of ≥ the pack amount to the configured receiving address, mined <30 days ago, and each tx hash is single-use.

Buying flow

  1. GET /packs/25 → read the 402 terms (payTo, exact USDC amount).
  2. Standard x402: sign an EIP-3009 authorization for exactly $0.01 USDC on Base to payTo and retry the same request with the signature in the X-PAYMENT (v1) or PAYMENT-SIGNATURE (v2) header. The payment is verified + settled via facilitator and pack 25 is returned immediately (50/100 return a 24h order receipt).
  3. Fallback: send exactly $0.01 USDC on Base to payTo yourself, then POST /fulfill with the tx hash.

Payment is verified on-chain (Blockscout free API): the tx must be a successful USDC transfer of ≥ the pack amount to the receiving address. Tx hashes are single-use (replay-protected); txs older than 30 days are rejected.

Config

  • SCOUTPACKS_RECEIVING_ADDRESS — the Base address that receives USDC. While unset (or the zero address) the endpoint runs in preview-only mode: sales_enabled=false in 402 bodies and /.well-known/x402, and /fulfill refuses all requests.
  • SCOUTPACKS_PUBLIC_BASE — public URL used in 402 resource fields.
  • PORT — default 8000.
  • MCP_PROXY_PORT — optional (e.g. 8001); when set, /mcp reverse-proxies to the sibling MCP streamable-HTTP server (mcp/http_server.py) on that port — one deploy exposes both the x402 API and a durable-HTTPS MCP endpoint.

Deploy

bash
./run.sh &                                   # localhost:8000

Production (since 2026-10-02) runs on Railway — https://scout-packs-production.up.railway.app is the sole production endpoint. The old localtunnel path (lt-proxy.js, loca.lt subdomains) is dead legacy, retired 2026-10-02 after chronic 503s. On normal infra for a fresh deploy, cloudflared tunnel --url http://127.0.0.1:8000 works as usual.

Then register on the open indexes, e.g. 402 Index: POST https://402index.io/api/v1/register with {url, name, protocol:"x402", description, price_usd, payment_asset:"USDC", payment_network:"eip155:8453", category:"data", tags:[...]}.

MCP server (for agent clients)

AI agents can also discover and buy packs from inside MCP clients (Claude Desktop, Cursor, MCP Inspector, agent frameworks) via the MCP server in mcp/:

  • list_packs — free. Pack sizes, prices, live sales status, redacted sample.
  • buy_pack — returns the exact x402 payment terms and the step-by-step flow; the buying agent's own wallet pays the endpoint. Never moves funds, never holds keys.

Quick start (Python 3.10+, installs the mcp SDK only):

bash
cd mcp && python3 -m venv .venv && .venv/bin/pip install mcpBASE_URL=https://<endpoint-url> .venv/bin/python scout_packs_mcp.py

Or once published to PyPI: uvx scout-packs-mcp with BASE_URL set. Full docs: mcp/README.md. Registry listings: mcp/REGISTRIES.md.

來源:README.md,提交 f54eb65

工具

0
工具後設資料尚未被收錄。

版本歷史

1
  1. v1.0.0最新Oct 6, 2026