x402Compute

GPU compute marketplace powered by x402 and MPP payments. Provision cloud instances on Vultr or DigitalOcean, pay with USDC on Base or Solana, or use MPP with Tempo-compatible clients such as mppx.

🖥️ Compute API is available at compute.x402layer.cc

Current release: v1.2.0. x402 Base/Solana remains live, MPP Tempo USDC.e payments are live, and DigitalOcean is code-ready as an additional provider once its API token is configured. Stripe card payments are code-ready pending Stripe Machine Payments access.

Provider support: Vultr is live. DigitalOcean plans appear with a do: prefix and require SSH key access.

Overview

x402Compute lets you provision GPU-powered virtual machines using x402 or MPP payment flows. Instances are provisioned via Vultr or DigitalOcean infrastructure and can be managed entirely through the API or the Compute Dashboard. Compute auth and management flows also support optional OpenWallet / OWS usage.

💳 Pay-Per-Provision

Pay with x402 USDC or MPP Tempo USDC.e. No subscriptions required.

⏳ Extend Anytime

Extend your instance's lifetime from 1 week to 6 months.

🔌 Full API Access

SSH access, root control, and full API for programmatic management.

☁️ Multi-Provider

Vultr live, DigitalOcean code-ready for extra capacity.

Instance Lifecycle

1. Browse Plans→2. Provision (x402 or MPP Pay)→3. Active→4. Extend / Destroy→5. Expired

API Reference

Base URL: https://compute.x402layer.cc

Auth: Management endpoints require either signed auth headers (X-Auth-*) or anX-API-Key issued viaPOST /compute/api-keys. You can use direct Base/Solana signing keys or optional OWS-backed auth for API-key creation and management. Paid provision and extend support x402, and MPP clients can pay with Authorization: Payment.

Method	Endpoint	Description	Auth
GET	/compute/plans	List available GPU plans with pricing	None
GET	/compute/regions	List available deployment regions	None
GET	/compute/os	List available OS images	None
POST	/compute/provision	Provision a new Vultr or DigitalOcean instance	x402 / MPP
POST	/compute/api-keys	Create API key for agents	Signature only
GET	/compute/api-keys	List API keys	Signature or X-API-Key
DELETE	/compute/api-keys/:id	Revoke API key	Signature only
GET	/compute/instances	List your instances	Signature or X-API-Key
GET	/compute/instances/:id	Get instance details	Signature or X-API-Key
DELETE	/compute/instances/:id	Destroy an instance	Signature or X-API-Key
POST	/compute/instances/:id/password	Retrieve one-time root password fallback	Signature or X-API-Key
POST	/compute/instances/:id/extend	Extend instance lifetime	x402 / MPP + Auth

Quick Start

1. Browse Available Plans

curl https://compute.x402layer.cc/compute/plans

# Response includes GPU plans with pricing:
# {
#   "plans": [
#     {
#       "id": "vcg-a100-1c-2g-6gb",
#       "name": "A100 1 GPU",
#       "vcpu_count": 12,
#       "ram": 120832,
#       "gpu_vram_gb": 80,
#       "monthly_cost": 90,
#       ...
#     }
#   ]
# }

2. Provision an Instance

The provision endpoint returns a 402 response with x402 and MPP payment requirements. Use the x402-compute skill, an x402-aware client, or npx mppx to handle payment automatically.

# Step 1: Request provision — get 402 challenge
curl -X POST https://compute.x402layer.cc/compute/provision \
  -H "Content-Type: application/json" \
  -H "X-API-Key: your_api_key" \
  -d '{
    "plan": "vcg-a100-1c-2g-6gb",
    "region": "lax",
    "os_id": 2284,
    "label": "my-gpu-instance",
    "prepaid_hours": 720,
    "ssh_public_key": "ssh-ed25519 AAAA... user@host",
    "network": "base"
  }'

# Step 2: Pay via x402 (handled automatically by x402 clients)
# Step 3: Instance is provisioned. SSH access uses your public key (no password returned).

2a. Provision with MPP / mppx

npx mppx https://compute.x402layer.cc/compute/provision \
  -X POST \
  -J '{"plan":"vc2-1c-1gb","region":"ewr","os_id":2284,"label":"mpp-vps","prepaid_hours":24,"ssh_public_key":"ssh-ed25519 AAAA... agent"}'

# If you do not include wallet/API-key auth, the response includes management_api_key.
# Store it once and use it for list/details/extend/destroy calls.

2b. Provision on DigitalOcean

# DigitalOcean plans are prefixed with do:
# DigitalOcean requires SSH key access; password fallback is Vultr-only.
npx mppx https://compute.x402layer.cc/compute/provision \
  -X POST \
  -J '{"plan":"do:s-1vcpu-1gb","provider":"digitalocean","region":"nyc3","os_id":123456789,"label":"do-vps","prepaid_hours":24,"ssh_public_key":"ssh-ed25519 AAAA... agent"}'

2c. Optional OpenWallet / OWS auth path

npm install -g @open-wallet-standard/core
export OWS_WALLET="compute-wallet"
export COMPUTE_AUTH_MODE="ows"
python scripts/create_api_key.py --label "my-agent"

# Then use COMPUTE_API_KEY for routine management
python scripts/list_instances.py

OWS scope: OWS is currently best for compute auth and management/API-key flows. Provision and extend still use the current direct Base or Solana payment-signing paths.

2d. One-Time Password Fallback (Optional)

# Use only if you did not provide ssh_public_key
curl -X POST https://compute.x402layer.cc/compute/instances/YOUR_ID/password \
  -H "X-API-Key: your_api_key"

# Returns root username + password once.
# Subsequent requests return 409.

3. List Your Instances

curl https://compute.x402layer.cc/compute/instances \
  -H "X-API-Key: your_api_key"

# Returns all instances with status, IP, expiry, etc.

4. Extend an Instance

# Extend by 720 hours (1 month)
curl -X POST https://compute.x402layer.cc/compute/instances/YOUR_ID/extend \
  -H "Content-Type: application/json" \
  -H "X-API-Key: your_api_key" \
  -d '{
    "extend_hours": 720,
    "network": "base"
  }'

# Returns 402 challenge → pay → instance extended

4a. Extend with MPP / mppx

npx mppx https://compute.x402layer.cc/compute/instances/YOUR_ID/extend \
  -X POST \
  -H "X-API-Key: $COMPUTE_API_KEY" \
  -J '{"extend_hours":720}'

# MPP extension requires compute auth so the server can verify instance ownership.

5. Destroy an Instance

curl -X DELETE https://compute.x402layer.cc/compute/instances/YOUR_ID \
  -H "X-API-Key: your_api_key"

# Instance is destroyed immediately

Payment Flow

x402Compute supports x402 and MPP payment protocols for provisioning and extending instances:

1. Request → 402 Challenge

Send a provision/extend request. The server responds with HTTP 402 containing x402 JSON requirements and MPP WWW-Authenticate: Payment headers.

2. Client Pays

An x402-aware client sends X-Payment. An MPP-aware client sends Authorization: Payment and receives Payment-Receipt on success.

3. Verify → Settle → Provision

The server verifies the payment through the x402 facilitator or MPP method handler, then provisions or extends the instance.

Supported Payment Options

Base (EVM)

USDC on Base • 100% reliable • Recommended

Solana

USDC on Solana • ~75% success rate • Retry recommended

MPP Tempo

Tempo mainnet USDC.e • Works with mppx CLI • Live

MPP Stripe Cards

Code-ready • Pending Stripe Machine Payments / SPT access

Resources

🖥️ Compute Dashboard

Visual UI for managing instances

🛒 Marketplace

Browse all x402 services