Cowrie Research

moltspay

3 min read

MoltsPay

  • Name: MoltsPay
  • URL: https://moltspay.com/
  • Category: agent-to-agent payments infrastructure / multi-chain x402 middleware / skill-monetization toolkit
  • Tags: ethereum-ecosystem solana-ecosystem
  • Summary: MoltsPay is best cataloged as an agent-payments control plane rather than as a simple x402 demo, wallet helper, or one-chain SDK. In this pass, the clearest first-party evidence came from the official site, the developer guide, the canonical TypeScript and Python READMEs, the package manifest, and the browser-demo README. Together those sources describe a stack that lets providers publish paid skills from a moltspay.services.json manifest, lets buyers discover and pay for services through CLI, SDK, browser-wallet, MCP, and LangChain surfaces, and routes settlement across several chain-specific payment schemes spanning Base, Polygon, Solana, BNB Chain, and Tempo. The key distinction is that MoltsPay is packaging the operational layer for machine commerce on both the seller and buyer side instead of only exposing a thin x402 wrapper.
  • What it does:
    • Lets service providers publish paid skills and APIs by adding a moltspay.services.json manifest and starting a MoltsPay server around existing exported functions
    • Gives buyers a CLI and SDK that create or connect wallets, discover service manifests, enforce spending limits, and execute paid calls with automatic retry after 402 Payment Required challenges
    • Supports several settlement paths under one product surface, including x402 plus Coinbase CDP on Base and Polygon, Solana SPL-transfer flows with server fee payers, BNB intent-style approval plus settlement flows, and MPP on Tempo
    • Exposes browser-wallet payments through moltspay/web for EIP-1193 wallets and Solana wallet-adapter wallets, including BNB approval handling and Tempo permit flows
    • Ships an MCP server so hosts like Cursor, Claude Code, Windsurf, and similar tools can discover services, inspect balances, and execute payments through guarded tool calls
    • Adds agent-framework integrations such as LangChain tooling and docs for creator, buyer, and testnet workflows
  • Key claims:
    • The homepage repeatedly says developers can “add one JSON file” to turn a skill into a paid service, which is the clearest top-level positioning signal surfaced in this pass
    • The site and docs both frame MoltsPay as gasless for clients, with the server or facilitator handling settlement mechanics so buyers do not need native gas tokens for the normal happy path
    • The current docs and READMEs claim live support across Base, Polygon, Solana, BNB Chain, and Tempo, including both mainnet and testnet variants, which makes the product materially broader than a Base-only x402 wrapper
    • The package manifest shows the project is not just a CLI: it exports separate server, client, web, wallet, facilitator, and MCP modules, plus moltspay and moltspay-mcp binaries
    • The browser demo README says the same SDK can route between EVM and Solana signers and can fall back to permit or approval flows depending on chain, which suggests a deliberate cross-VM abstraction layer rather than a one-off example
    • The docs portal positions MoltsPay around creators, agents, and developers at once, with service discovery APIs, provider manifests, testnet faucets, Python/Node SDKs, and framework integrations, reinforcing that it is trying to be a reusable commerce stack
    • The homepage explicitly ties the project to Zen7 Labs and an “Agent Economy” narrative, but the concrete evidence that matters more is the shipping operational surface: manifests, discovery endpoints, SDK methods, CLI commands, browser support, and chain-specific settlement paths
  • Whitepaper: No canonical standalone MoltsPay whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official site, developer guide, canonical TypeScript and Python READMEs, package manifest, and browser-demo README; see ../whitepapers/moltspay-primary-sources-2026-05-03.md.
  • Sources:

Internal linkages

Graph View