Machine Payments Protocol (MPP)

The Machine Payments Protocol (MPP) enables AI agents to deploy projects to CreateOS autonomously by paying with stablecoins on EVM chains. No accounts, no API keys, no OAuth - the on-chain payment is the access control.

How It Works

MPP uses an HTTP 402 payment flow. The agent calls the deploy endpoint, receives a payment quote, sends an ERC20 transfer on-chain, and retries the deploy with the transaction hash. The gateway verifies the payment and deploys.

Agent                    MPP Gateway                Blockchain
  |                          |                          |
  |-- POST /agent/deploy --> |                          |
  |<-- 402 (pay_to, amt) --- |                          |
  |                          |                          |
  |-- ERC20 transfer --------|------------------------->|
  |                          |                          |
  |-- POST /agent/deploy --> |                          |
  |   (X-Payment-Tx: 0x...) |-- verify on-chain ------>|
  |                          |<-- confirmed ------------|
  |                          |-- deploy to CreateOS     |
  |<-- 200 (projectId) ----- |                          |
  |                          |                          |
  |-- GET /status ---------> |                          |
  |<-- { status: "ready" } - |                          |

Key Concepts

Permissionless Access

There is no signup, no API key, and no OAuth. Any agent with an EVM wallet and stablecoins can deploy. The wallet signature authenticates requests and the payment itself is the authorization.

Credit System

Payments are converted to CreateOS credits ($1 = 100 credits). Credits are consumed hourly by active projects. If you already have credits from a previous payment, the gateway deploys without requiring additional payment.

Credit Sharing

Credits are pooled across all active projects for a wallet. When deploying with existing credits while other projects are running, the gateway warns that it will reduce runtime of active projects. You must explicitly opt in via the X-Use-Existing-Credits: true header.

Supported Chains & Tokens

Install the Skill

If you're using an AI coding tool (Claude Code, Copilot, Gemini CLI, etc.), install the CreateOS MPP skill:

Bash
Copy
1npx skills add NodeOps-app/skills --skill createos-deploy

This gives your AI agent the full deploy flow - it handles wallet auth, payment, and deployment automatically.

Quick Start

1. Generate an EVM wallet with gas (ETH) and USDC on Arbitrum or Base
2. Call POST /agent/deploy without payment to get a quote (402 response)
3. Check balance via GET /agent/balance/:address?chain=arbitrum
4. Send ERC20 transfer to the pay_to address from the quote
5. Call POST /agent/deploy again with X-Payment-Tx header
6. Poll status via GET /agent/deploy/:projectId/:deploymentId/status

Only dependency: viem for wallet signatures and ERC20 transfers.

Gateway URL

https://mpp-createos.nodeops.network

Next Steps

• Authentication - wallet signature details
• Deploy Flow - step-by-step payment and deploy flow
• API Reference - full endpoint documentation
• Example - complete working code example