Payment terms arrive over HTTP
The checkout route returns a canonical x402 v2 PAYMENT-REQUIRED challenge that binds the authorization to the requested resource.
04 / HTTP 402 / machine-payable compute
Buy a Linux VPS through an x402 flow.
WarpMetal turns a server lease into an explicit HTTP transaction: prepare the order, receive live payment requirements, sign once, then poll the same task to ready.
No account required for eligible workloads. Live API readiness, inventory, and HTTP 402 terms determine whether checkout can proceed.
Fastest start / one message
Pass the guide to your agent.
A web-enabled agent can read the canonical instructions and live catalog. If it cannot open URLs, paste the full contents of llms.txt into the conversation.
Prompt for an x402-capable agent
Read https://warpmetal.com/llms.txt and explain the WarpMetal x402 VPS purchase flow. Fetch the live catalog, prepare an idempotent order for [describe workload], and stop before signing any PAYMENT-REQUIRED challenge so I can verify the amount, asset, network, and recipient.Designed for controlled autonomy
The agent can do the work. You keep the authority.
Retries do not mean repaying
Ambiguous 202, 503, timeout, and transport outcomes reuse the exact request and exact signature according to the agent guide.
Settlement and fulfillment are separate
Payment finality queues provisioning. The durable task remains pollable while compute creation and device readiness complete.
Provider details stay private
The buyer uses public resource classes and provider-neutral server IDs. Internal infrastructure credentials never enter the client contract.
Four public resource classes
Pick the amount of machine the work needs.
Prices cover one 30-day term. Exact operating systems and purchase availability come from the live catalog; exact payment details come only from the live x402 challenge.
01 / vps.standard
Standard
$12 / 30 days
- Compute
- 2 vCPU
- Memory
- 4 GB RAM
- Disk
- 40 GB NVMe
- Transfer
- 10 TB
02 / vps.agentRecommended
Agent
$20 / 30 days
- Compute
- 4 vCPU
- Memory
- 8 GB RAM
- Disk
- 80 GB NVMe
- Transfer
- 10 TB
03 / vps.build
Build
$45 / 30 days
- Compute
- 8 vCPU
- Memory
- 16 GB RAM
- Disk
- 160 GB NVMe
- Transfer
- 10 TB
04 / vps.heavy
Heavy
$75 / 30 days
- Compute
- 12 vCPU
- Memory
- 24 GB RAM
- Disk
- 240 GB NVMe
- Transfer
- 10 TB
Good fit / explicit environment
Workloads that benefit from a real host.
Agent-owned execution capacity
A funded, policy-controlled agent can acquire a machine without an invoice account or cloud-provider API key.
Protocol integration testing
Exercise challenge handling, signature replay rules, settlement status, fulfillment polling, and renewal against a real compute product.
Fixed-term infrastructure
Purchase exactly 30 days of Linux capacity and renew only when the workload still needs it.
Purchase flow / four boundaries
From workload to SSH.
The browser page explains the product. The machine contract and live API control every operational decision.
- 01
Read the contract
The agent reads llms.txt before preparing any order.
GET /llms.txt - 02
Choose live capacity
It selects a public plan and exact free Linux image.
GET /api/catalog - 03
Prepare, review, and pay
You review the live x402 amount, asset, network, and recipient.
POST /api/checkout - 04
Poll and connect
The task becomes ready with an IP and your installed SSH key.
ssh root@IP
Before first boot
Questions for x402 developers.
01Which networks and assets does WarpMetal accept?+
The current public contract supports Solana USDT, TRON USDT, and Base USDC. The live HTTP 402 response is authoritative for every transaction.
02Does preparing an order charge the wallet?+
No. POST /api/orders validates inventory and creates an idempotent task. Payment begins only when the matching checkout endpoint returns its live challenge.
03What happens after settlement?+
A durable worker provisions the server, waits for the device to become ready, and attaches the public IP to the provider-neutral task and server ID.
04Can an agent discover WarpMetal without this page?+
Yes. robots.txt, sitemap.xml, llms.txt, the agent card, OpenAPI, and HTTP discovery headers all point agents to the public machine contract.