Cowrie Research

monapi

3 min read

Monapi

  • Name: Monapi
  • URL: https://monapi.dev/
  • Category: x402 seller middleware / API paywall wrapper
  • Tags: ethereum-ecosystem
  • Summary: Monapi is x402 seller middleware. It prices routes, wraps MCP tools, and handles the 402 choreography so developers do not have to wire the protocol by hand. Useful glue, not a payment rail.
  • What it does:
    • Wraps Express routes with a monapi() middleware so protected endpoints return 402 Payment Required until the caller pays in USDC through x402-compatible flows
    • Wraps Next.js handlers with withMonapi() and supports multi-route protection with monapiProxy()
    • Wraps MCP tool handlers with monapiMcp() so AI-agent tools can be sold on a pay-per-call basis rather than only via subscriptions or API keys
    • Supports either one global price or per-route pricing maps, plus optional payment callbacks for post-payment logging or workflow hooks
    • Supports Base, Arbitrum, and Polygon plus testnets, with USDC as the documented payment token in the current release
    • Ships an npx monapi init wizard that detects the framework, helps configure a wallet, and generates starter configuration and code
  • Key claims:
    • The official site and README both describe Monapi as letting developers “Monetize any API with one line of code,” which is the clearest top-level positioning signal surfaced in this pass
    • The README says raw x402 integration requires understanding CAIP-2 network IDs, token contract addresses, facilitator configuration, and scheme registration, while Monapi compresses that into a single function call
    • The official materials say Monapi supports Express, Next.js, and MCP, which makes it more than a single-framework helper and closer to a reusable monetization layer for developer services and agent tools
    • The README says “No monapi account needed. No dashboard, no API keys, no middleman,” and says payments go directly from the client to the developer’s wallet onchain
    • The same materials say x402-compatible agents can automatically pay and retry requests, and that gas is sponsored by the facilitator via EIP-3009 so agents only need USDC rather than native gas tokens
    • The config docs show route-level pricing, custom facilitator URLs, payment-event hooks, and network selection, which indicates the product is trying to simplify operational deployment rather than only demonstrate a toy x402 example
    • The roadmap is worth reading as aspiration, not current scope. The live note is still a route-paywall wrapper, not a broader trust or compliance stack yet
  • Whitepaper: No canonical standalone Monapi whitepaper or litepaper surfaced in this pass. The clearest current source of truth was the official site and canonical GitHub repository/README; see ../whitepapers/monapi-primary-sources-2026-05-03.md.
  • Sources:

Internal linkages

  • Keep this on the strongest upward reads: x402 and open-payments.

  • Last reviewed: 2026-06-02 UTC

Graph View