Skip to content

tempoxyz/openclaw-mpp

Repository files navigation

MPP for OpenClaw

npm CI License

Give OpenClaw access to pay-per-use APIs without managing a separate API key or subscription for every service. The plugin installs a payment-aware fetch in the Gateway so HTTP and MCP calls can handle MPP HTTP 402 charges and streaming sessions using a capped, expiring Tempo Wallet access key.

Maintained by Tempo, the team behind MPP.

Quick start

Important

Tempo Wallet setup uses Tempo mainnet and authorizes real USDC spending. The default access key expires after seven days and has a total 10 USDC spending limit.

Install from ClawHub, connect Tempo Wallet, and restart the active gateway:

openclaw plugins install clawhub:openclaw-mpp
openclaw mpp setup
openclaw gateway restart

Verify both the wallet and the live gateway runtime:

openclaw mpp status
openclaw plugins inspect mpp --runtime --json

During OpenClaw's registry transition, npm remains available as an explicit fallback:

openclaw plugins install npm:openclaw-mpp

Make a first paid request

Send this prompt through OpenClaw:

Use mpp_fetch to GET https://mpp.dev/api/ping/paid and report the HTTP status and payment receipt.

This test spends real USDC. A successful request returns HTTP 200 and includes the payment receipt in the tool result. If OpenClaw selects its built-in web_fetch tool instead, explicitly ask it to use mpp_fetch; built-in web_fetch is not payment-aware.

Connect a wallet

Tempo Wallet

openclaw mpp setup uses the Tempo Accounts SDK to open a Tempo Wallet approval flow. Your wallet authorizes a seven-day access key with a 10 USDC spending limit; your wallet's root private key is never shared with OpenClaw.

Customize the access key policy or create one for Tempo testnet:

openclaw mpp setup --expires 24h --limit USDC=25 --no-deposit
openclaw mpp setup --network testnet
openclaw mpp status --network testnet

Authorize an access key for each network the agent uses. Payment challenges select the matching network automatically. Restart a running gateway after setup with openclaw gateway restart.

Existing access key

To select an access key already stored by Tempo Wallet, add its address to openclaw.json:

{
  "plugins": {
    "entries": {
      "mpp": {
        "config": {
          "wallet": {
            "type": "tempo",
            "accessKey": "0x..."
          }
        }
      }
    }
  }
}

Private key

Set TEMPO_PRIVATE_KEY before starting OpenClaw to use a Tempo private key directly:

TEMPO_PRIVATE_KEY=0x... openclaw gateway run

What it provides

The Gateway payment-aware fetch supports:

  • free HTTP requests
  • Tempo charge and session challenges
  • paid SSE session streams
  • fetch-backed MCP tool calls

The mpp_fetch tool uses the same fetch explicitly. OpenClaw's built-in web_fetch and managed MCP transports use separate HTTP clients and are not covered yet.

The mpp_wallet_setup and mpp_wallet_status tools let an agent start wallet setup and inspect mainnet or testnet access keys. If the active tool profile filters plugin tools, add mpp to the existing tools.alsoAllow list. Gateway startup only loads existing wallet configuration and never opens an authorization flow.

Development

pnpm install
pnpm test
pnpm check
pnpm lint
pnpm pack --dry-run
openclaw plugins install --link .

Package

  • Plugin id: mpp
  • Package: openclaw-mpp
  • Minimum OpenClaw host: 2026.6.11

Security

Report vulnerabilities privately as described in SECURITY.md.

License

MIT

About

Pay-per-use APIs for OpenClaw with automatic MPP HTTP 402 payments and capped Tempo Wallet access keys.

Topics

Resources

License

Contributing

Security policy

Stars

1 star

Watchers

0 watching

Forks

Packages

 
 
 

Contributors