← Back to Skills Marketplace
x402 Compute
by
Ivaavi.eth
· GitHub ↗
· v1.2.0
· MIT-0
734
Downloads
2
Stars
1
Active Installs
10
Versions
Install in OpenClaw
/install x402-compute
Description
This skill should be used when the user asks to "provision GPU instance", "spin up a cloud server", "list compute plans", "browse GPU pricing", "extend compu...
Usage Guidance
This skill appears to implement a legitimate blockchain-paid compute provisioning flow, but take these precautions before installing: 1) Don't export your primary custody private keys into environment variables for this skill — create a dedicated wallet with minimal USDC for provisioning and use that. 2) Prefer installing and configuring OpenWallet/OWS yourself (npm install -g @open-wallet-standard/core) so the scripts use your local binary instead of falling back to 'npx -y' which downloads code at runtime. 3) Be aware the skill will load .env files and environment variables (WALLET_ADDRESS, PRIVATE_KEY, SOLANA_SECRET_KEY, OWS_WALLET, COMPUTE_API_KEY); audit and keep those secrets isolated (use ephemeral test wallets or an isolated execution environment). 4) The registry metadata did not list the env vars the code expects — treat that as a documentation gap and verify expected variables before running. 5) If you are unsure about the service domain (compute.x402layer.cc), verify its legitimacy and review the included scripts locally before running any that sign transactions or send private keys.
Capability Analysis
Type: OpenClaw Skill
Name: x402-compute
Version: 1.2.0
The x402-compute skill bundle provides a legitimate interface for provisioning GPU and VPS instances using blockchain-based payments (USDC on Base and Solana). The scripts (e.g., wallet_signing.py and solana_signing.py) handle sensitive private keys from environment variables but follow security best practices by performing all transaction signing locally and never transmitting raw keys to the service (https://compute.x402layer.cc). The use of subprocesses in ows_cli.py to interact with the Open Wallet Standard is implemented safely without shell=True, and the SKILL.md instructions are strictly aligned with the stated purpose of infrastructure management.
Capability Tags
Capability Assessment
Purpose & Capability
The name/description match the code: scripts list plans/regions, provision/extend/destroy instances, and perform on-chain (Base/Solana) payment signing. Requiring private keys for payment signing is appropriate for the stated purpose. However, the registry metadata says there are no required environment variables or primary credential, while SKILL.md and the scripts clearly expect sensitive env vars (e.g., PRIVATE_KEY / WALLET_ADDRESS, SOLANA_SECRET_KEY, OWS_WALLET, COMPUTE_API_KEY). That documentation mismatch is surprising and should be corrected or clarified.
Instruction Scope
Runtime instructions are focused on compute provisioning and management and warn about private-key handling. The scripts sign payment messages locally and call the documented compute API endpoints. They do read environment variables and may read user-provided files (e.g., SSH key files, dotenv .env), which is expected. The only notable scope expansion is that the code may invoke external tooling (OWS via subprocess/npx); otherwise there are no instructions to access unrelated system data.
Install Mechanism
There is no formal install spec in the registry, but SKILL.md instructs 'pip install -r requirements.txt' and the code will attempt to run OWS via an 'ows' binary or fallback to 'npx -y @open-wallet-standard/core'. That npx fallback can dynamically fetch and run code from npm at runtime, which increases risk if you rely on automatic execution. Requirements (eth-account, web3, solders) are consistent with EVM and Solana signing, but the lack of an explicit install step in the registry and the runtime use of npx are points of friction/risk.
Credentials
The skill uses highly sensitive environment variables (EVM private key, SOLANA_SECRET_KEY, wallet addresses, OWS/COMPUTE_API_KEY) and will load dotenv if present. Those secrets are proportional to paying for compute via blockchain; however the registry metadata declares no required env vars/primary credential, creating an undocumented gap. Also the code suggests setting PRIVATE_KEY or SOLANA_SECRET_KEY as plain env vars — a dangerous practice for high-value wallets. The SKILL.md does warn to use a dedicated throwaway wallet, which mitigates risk but does not remove the concern that secrets might be present in the environment or .env files and that the scripts will load them.
Persistence & Privilege
The skill does not request 'always: true' and does not appear to modify other skills or system-wide agent settings. It runs as-needed and uses subprocesses for OWS if available. No elevated persistence behavior was found.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install x402-compute - After installation, invoke the skill by name or use
/x402-compute - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.0
x402-compute 1.2.0 adds Multi-Provider Payments (MPP) support and updates payment/management flows.
- Introduced MPP/Mppx payment options: Users can now provision and manage GPU/VPS with Tempo or Stripe/card (when enabled) in addition to x402 (USDC on Base/Solana).
- Updated documentation and quick start to cover MPP usage with `mppx` CLI and environment variable setup for management API keys.
- Clarified protocol usage: `X-Payment` for x402, `Authorization: Payment` for MPP.
- Added instructions for extending instances via MPP and handling responses with management API keys.
- Adjusted wording to reflect support for both x402 and MPP methods throughout workflows and API descriptions.
v1.1.0
x402-compute 1.1.0 introduces optional OpenWallet/OWS-based authentication and expands management options.
- Added OpenWallet (OWS) support as an optional authentication and agent key management layer.
- New script: ows_cli.py for running OWS wallet, sign-message, and key commands.
- Auth/environment setup now includes OWS options; direct signing still supported.
- Documentation expanded: see references/openwallet-ows.md for OWS usage and details.
- No breaking changes to existing direct wallet/private key provisioning or payment flows.
v1.0.7
- Updated environment variable documentation for clarity, grouping EVM and Solana payment options under explicit "Option A" and "Option B".
- Changed recommended authentication in metadata: now prefers COMPUTE_API_KEY over raw private keys for management.
- Updated credential configuration to prioritize API key usage.
- No code changes or functionality updates; documentation only.
v1.0.6
x402-compute 1.0.6 introduces support for daily instance provisioning and updates workflows for short-duration compute.
- Adds support for `--days` flag to provision instances by day, enabling short-term "daily" and "cheaper use-and-throw" compute.
- Updates documentation with examples for provisioning and extending instances by days, in addition to by month.
- Workflow examples now include provisioning for 1 or 3 days, and extending instances by 1 day or 1 month.
- No code or file changes; changelog reflects updated docs and usage patterns only.
v1.0.5
x402-compute v1.0.5
Release Date: 2026-02-20
Overview
This release adds full Solana payment support to all compute scripts and fixes
an authentication issue that caused 401 errors during paid retries.
Changes
Added
- Full Solana payment support for extend_instance.py
- The --network solana flag is now fully supported for extend operations
- Builds and signs a Solana VersionedTransaction
- Uses SPL transferChecked instruction for USDC payments
- Automatically creates the recipient USDC token account if it does not exist
- Payment flow now matches provision.py
Fixed
- Fixed 401 Unauthorized errors during paid retry requests
- Removed stale compute authentication headers (X-Auth-*) from paid retries
- Fix applied to both provision.py and extend_instance.py
Removed
- Removed all legacy AWAL mode references from extend_instance.py
Technical Notes
- The 401 issue was caused by nonce reuse
- The nonce from the initial 402 response was already recorded by the backend
- Re-sending X-Auth-* headers on the paid retry caused authentication failure
- The x402 X-Payment header alone is sufficient for authentication
- On-chain USDC payment verifies the payer
- No additional auth headers are required during the payment step
v1.0.4
- Added Solana network support for provisioning and managing compute instances.
- Introduced scripts/solana_signing.py for internal Solana x402 payment signing.
- Updated environment variables to support Solana keys (SOLANA_SECRET_KEY, SOLANA_WALLET_ADDRESS, COMPUTE_AUTH_CHAIN).
- Clarified workflows and script usage for both Base (EVM) and Solana modes.
- Removed deprecated AWAL bridge script.
v1.0.3
v1.0.3 Changelog:
- Bumped x402-compute skill version to 1.0.3.
- Added one-time password fallback support docs and script (`get_one_time_password.py`).
- Added AWAL support for `provision.py` and `extend_instance.py`.
- AWAL mode now requires `COMPUTE_API_KEY` for compute management auth.
- Added `awal_bridge.py` helper for AWAL CLI integration.
- Improved `provision.py` handling for `201 Created` success responses.
- Improved AWAL error messages when `COMPUTE_API_KEY` is missing.
- Updated plan-list script to support current API pricing fields.
- Updated list/details scripts to show plan and region correctly from API response.
- Added SSH-key-first guidance with explicit key generation example (`ssh-keygen ... ~/.ssh/x402_compute`).
- Synced skill updates to SGL docs skill folder.
- Updated old worker hosted skill manifest/installer to include new script and guidance.
- Added compute UI "Password" action in Your Fleet cards with one-time credential modal.
- Created external changelog file outside skill folder (as requested).
v1.0.2
x402-compute v1.0.2 Changelog
Fixed:
- Registry metadata fix: Removed X402_USE_AWAL and X402_AUTH_MODE from required env vars(they are optional)
- Added credentials.primary: PRIVATE_KEY declaration to properly indicate the primary credential
v1.0.1
x402-compute v1.0.1
Fixed:
- instance_details.py now displays VPS credentials (root password, IPv6) when available
- Previously, the API returned vultr_default_password but the script wasn't showing it
- Added a note in the provisioning workflow to clarify that users should wait 2-3 minutes after provisioning for Vultr setup to complete before fetching instance credentials.
- No other changes or feature updates included in this version.
v1.0.0
x402-compute 1.0.0 – Initial release
- Provision and manage GPU/VPS cloud instances with USDC payment on Base or Solana networks via x402 payment protocol.
- Supports operations like listing compute plans, provisioning or destroying GPU/VPS servers, extending instance lifetime, and checking status.
- CLI scripts provided for browsing plans, provisioning, instance management, and payment handling.
- Requires local wallet credentials or integration with Coinbase Agentic Wallet for signing transactions.
- Security guidance included for handling private keys and wallet setup.
- Detailed environment variable and workflow documentation is provided in SKILL.md.
Metadata
Frequently Asked Questions
What is x402 Compute?
This skill should be used when the user asks to "provision GPU instance", "spin up a cloud server", "list compute plans", "browse GPU pricing", "extend compu... It is an AI Agent Skill for Claude Code / OpenClaw, with 734 downloads so far.
How do I install x402 Compute?
Run "/install x402-compute" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is x402 Compute free?
Yes, x402 Compute is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does x402 Compute support?
x402 Compute is cross-platform and runs anywhere OpenClaw / Claude Code is available (linux, darwin).
Who created x402 Compute?
It is built and maintained by Ivaavi.eth (@ivaavimusic); the current version is v1.2.0.
More Skills