Payments for AI-powered services

Request payment.
Deliver after verification.

Connect your agent to MochiPay with runtime tools. Give users on-site or hosted checkout, then verify payment on your server before delivering their result.

USDT · USDC · BTC · ETH · SOL, on their supported networks.

MOCHIPAYA paid service workflow
01
Request a reportYour app saves the topic, price and owner
02
Complete checkoutON_SITE or HPP, using one payment order
03
Verify and deliverThe server checks payment and unlocks once
FREE MCP SERVER · VERSION 1.0.0

Tools your agent can call

A local, single-merchant stdio server. Python 3.10+ and the official MCP Python SDK are required. Connect it to an AI host that supports launching local MCP servers.

CREATE

create_payment_request

Create a request with an exact decimal-string amount, chosen asset/network and stable request ID. ON_SITE is the default; HPP returns the same saved order's hosted link.

{"request_id":"report-sale-001", "amount":"10.00",
 "currency":"USD", "payment_method":"USDT_TRC20",
 "checkout_mode":"ON_SITE"}
QUERY

get_payment_status

Query a request created by your local installation. payment_verified requires the bound order to be PAID with the exact received amount. Your application controls delivery.

{"request_id":"report-sale-001"}

These tools request and track payment. They do not sign wallet transactions or spend funds.

English README, configuration example, source and validation summary are inside the ZIP.

LOCAL INSTALLATION

Extract. Configure. Connect.

1. Install dependencies

Extract the mochipay-mcp folder. Run from that folder:

python3 -m venv .venv
.venv/bin/python -m pip install -r requirements.txt

Windows PowerShell:

py -3 -m venv .venv
.\.venv\Scripts\python.exe -m pip install -r requirements.txt

2. Configure your MCP host

Use the included mcp-config.example.json. Set absolute interpreter/server/state paths and merchant credentials privately. Your client's documented configuration location may differ.

Creation is disabled unless MOCHIPAY_ALLOW_CREATE=true. Keep the private SQLite state file so retries reuse the original order. The configured maximum is a nominal per-order amount in the requested currency.

Restart or reconnect the host and check that both tools appear. This local server is a separate download from the integration Skill.

3. Ask your connected agent

Use MochiPay to create a 10 USD payment request for report access.
Use USDT TRC20, HPP, and request_id report-sale-001.
Then query report-sale-001 and tell me whether payment is verified.

Reuse the same request ID and details after a timeout. A new ID creates a separate order. ON_SITE returns fields for your application's checkout; it does not embed a payment dialog in an arbitrary chat client.

PHP REPORT UNLOCK DEMO · VERSION 1.0.0

A complete payment and unlock example

Request a topic, save an order, complete ON_SITE or HPP checkout, and unlock a downloadable report only after a signed server query verifies payment.

Two checkout modes, one order

ON_SITE: payment amount, network, address QR and status appear in a dialog on your PHP page.

HPP: continue to the validated MochiPay hosted payment page and return to your application.

Changing modes and recovering a lost create response reuse the saved payment. Do not round the exact chain amount.

Delivery stays on your server

The sample checks ownership, the saved order, original price, currency, asset/network, receiving address and exact paid amount. Browser return parameters and callback payloads cannot unlock it by themselves.

The included report is clearly marked sample content, not generated by a live AI model. Connect your own AI provider and persistent job queue for production generation.

PHP 7.0–8.x · cURL, JSON, sessions and HTTPS · persistent private storage outside the document root. Install on a protected staging host; set credentials, public URL, storage path and access code as described in the included README.

The MCP server and PHP demo keep separate request records. To connect them in your own app, bind your business order and customer to the payment deliberately. Installing MCP does not automatically unlock a demo report.

CHOOSE YOUR STARTING POINT

Instructions, runtime tools or application code

PackagePurposeWhere it runs
Integration SkillHelps an assistant choose plugins and build an integrationA skills-compatible development assistant
MCP serverCreates requests and queries payment at runtimeA local MCP host, with private merchant credentials
Report demoShows checkout and verified paid accessYour PHP staging server

Native store plugins and custom integrations support ON_SITE and HPP. Classic SaaS supports HPP only.

This release uses the existing MochiPay order API. It does not implement x402 or autonomous wallet payments.