BetaBeta — blockchain transfers are, in principle, irreversible. Details

OpenPay

Connect

OpenPay Agent

Let your AI pay in JPYC.

OpenPay never holds your wallet or your private key.

Connect your agent

Hand this prompt to your agent. It does the setup itself.

Set me up to pay in JPYC through OpenPay.

Run `curl -sL https://open-pay.jp/agent/setup.md` and follow the returned instructions.

Rules:
- Never ask me for a private key, and never read, print, log, or send one anywhere (not to this chat, not to OpenPay, not to any third party). For Local Wallet, the MCP server creates the wallet key on this machine and shows you only its public address. For Kova, the person manages the wallet in Kova. For MetaMask, the key stays in MetaMask’s server wallet; this machine only needs an `mm` login performed by the person.
- Assume a dedicated low-balance agent wallet, not my main wallet.
- Set the per-call, per-session, and daily spending limits and the allowed hosts. Ask me for the amounts if I have not given them.
- Do not make any real payment during setup.

When you are done, report: the config you wrote, the limits you applied, the agent wallet address and the link where I can fund it and check its JPYC balance, and which JPYC resources on the OpenPay AI Store this agent can buy right now (with a quote for one of them).
Or open inClaudeCodex

If the app is installed, it opens with the prompt filled in (Claude opens in Claude Code). You press send. For agents with shell access, such as Claude Code, Codex CLI, and Hermes. For chat-only hosts, use “Write the config yourself” below. Read the instructions your agent follows (setup.md)

The same instructions are also available as an Agent Skill: npx skills add cipherwebllc/openpay

Two ways to use it

Don't hand the AI a wallet

Human pays

The AI prepares the order; you approve the payment in your own wallet. No key needed.

Guide: order with your AI

Give the AI a budget

Agent pays

The AI pays from a small dedicated wallet, within limits you set.

Guide: how AI pays

Agent wallet

What you can ask your agent

Copy one and paste it into your agent. Shop orders also work with “Human pays.”

  • Free

    List the JPYC data and APIs I can buy on OpenPay right now, with the price and fee for each. Do not pay.

  • Pays · 3 JPYC

    Buy the JPYC Service Monitor with a 3 JPYC cap and summarize what changed in the last month in five lines.

    Nothing above the cap in the prompt is paid. If the limit on the agent side is lower, the payment is refused.

    It can return only what changed since your last check, so it also works as a weekly routine. A free freshness check tells you whether anything changed before you buy.

    Real run: on 2026-09-22 an agent bought it for 3 JPYC (price at the time) and got back the dated change list with source URLs. View the transaction

  • You pay yourself

    Find shops where I can order with JPYC and show me the menu and the total. I will pay myself.

More requests (4)
  • Free

    Show me what you bought recently, with amounts and transaction hashes.

  • Free

    Tell me my current spending limits and how much I have spent today.

  • Free

    Open my purchase history on the web.

  • Free

    I want to switch my agent’s payment method. Show me the current config and limits first, then switch to Kova or MetaMask Agent Wallet following https://open-pay.jp/agent/setup.md. Never ask me for a key.

About spending limits

Enforced by the MCP/SDK on the agent side
  • Limits are enforced by the MCP on the agent’s side. OpenPay’s servers are not involved.
  • Fund only a small amount you can afford to lose. The balance is the real cap.
  • Set the limits yourself, not the AI. An AI that can run shell commands can change them.
  • This page never asks for a private key. Any OpenPay screen that does is fake.
Details

Spending limits and allowed hosts are local safety settings applied by the MCP/SDK on the machine that runs your agent. OpenPay's servers do not know them and do not guarantee them. This page never changes your agent's settings.

  • Fund the dedicated agent wallet only with what you are willing to spend. Its balance is the effective ceiling.
  • The limits are in your AI app's MCP settings, and the daily total and purchase log are in ~/.openpay-x402 on this machine. An AI that can run shell commands can change both, so set or change the limits yourself. Check what was actually paid in Activity and Purchases on this page (on-chain and OpenPay's records).
  • This page has no private-key field. Any OpenPay screen asking for a key is fake.
  • The wallet key is created and kept by the MCP on your own machine, where your agent runs. It never enters the chat or reaches OpenPay. Anything that can run commands as you can still read it, so fund it only with a small amount you can afford to lose. OpenPay cannot recover the key.
  • Where the agent runs decides which mode you can use. Claude Code or Codex on your own PC can use the Local Wallet, Kova, MetaMask Agent Wallet, or Steward. The Claude mobile app's Code tab and Claude Code on the web run in a disposable cloud environment: a Local Wallet created there disappears with its key (do not fund it), and Kova needs its CLI and credentials on the same machine, so it does not work there either. MetaMask Agent Wallet also needs an mm session on the same machine as the MCP and cannot run there. From a phone or browser, choose Human pays (approve the payment link in your own wallet), or use Steward if the agent must pay.
  • To stop the agent from paying right away, remove the OpenPay MCP (openpay-x402) from your AI app’s settings (Claude Code: claude mcp remove openpay-x402). Each payment is a one-time signature with no token approval, and any signature already given expires within 20 minutes at most (10 by default), so there is nothing else to cancel.
  • The Local Wallet has no way to export its key. Fund it only with what you plan to spend. If you want to manage the balance yourself or take it back later, choose MetaMask Agent Wallet, where the key stays in MetaMask, and move the funds in MetaMask yourself.

Write the config yourself (manual)For switching the payment method (local / Kova / MetaMask) or hosts where the agent can’t write its own config

Builds the config to paste into your agent’s environment. You do the pasting.

Ceiling for price plus fee

Resets when the MCP restarts

Blank applies the session limit as the daily limit · survives restarts (UTC day)

Comma-separated host names

URLs in the OpenPay catalog are payable without adding their host; for those, payment terms that differ from the listing are refused. Hosts you add yourself are not checked against the catalog.

Run in your terminal

claude mcp add openpay-x402 -e SIGNER_MODE=keystore -e MAX_PER_CALL_JPYC=10 -e MAX_SESSION_JPYC=100 -e ALLOWED_HOSTS=open-pay.jp -e CATALOG_TRUST=true -- npx --yes openpay-x402-mcp@0.20

This config contains no private key. After pasting it and restarting your agent’s host, ask the agent to “call wallet_init”. The MCP creates a wallet on your machine and returns only its address and a funding link. Send JPYC to that address and paying is enabled.

The buyer pays the price plus the x402 fee of 1% (minimum 1 JPYC). Size the per-call limit for the total.

Learn more