openclaw-x402-skill_skill

This skill helps you discover, filter, and pay for x402 API endpoints and MCP tools using USDC on Base with no keys.
  • Python

2.6k

GitHub Stars

4

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill openclaw-x402-skill

  • _meta.json295 B
  • README.md23.7 KB
  • SKILL.md7.7 KB
  • x402-MCP.md15.1 KB

Overview

This skill lets agents discover, browse, filter, inspect, and pay for x402-compatible API endpoints and MCP tools from the x402 Bazaar. It supports read-only discovery with no keys and on-demand paid calls using USDC on Base (requires a Base private key in .env). Use it to find payable APIs, check payment requirements, and execute a single micropaid request without API keys or account setup.

How this skill works

The skill queries one or more x402 discovery catalogs, merges results, and presents structured metadata (URL, type, price, network, updated). For paid endpoints it follows the x402 402 Payment Required flow: discover → receive 402 with payment details → pay via facilitator using USDC on Base → resend request with payment proof and return the paid response. It also exposes discovered services as MCP tools for automatic use in MCP-enabled clients.

When to use it

  • Discover available x402 services for a task (weather, scraping, AI inference, market data).
  • Browse the Bazaar without any wallet or API keys to evaluate options and prices.
  • Find services under a specific price threshold or filter by type/network.
  • Pay for and call a discovered x402 endpoint using USDC on Base.
  • Expose x402 services to MCP servers for autonomous agent access.

Best practices

  • Use browse-only mode to survey services before spending funds.
  • Set MAX_SPEND_PER_CALL in .env to cap per-call expenditure and avoid surprises.
  • Fund a Base wallet with USDC and add EVM_PRIVATE_KEY to .env only when ready to make paid calls.
  • Filter by network (e.g., eip155:8453) to avoid unsupported chains or token mismatches.
  • Inspect the 402 response headers to confirm payment requirements and maxAmountRequired before consenting to pay.

Example use cases

  • Find the cheapest weather API on x402 and fetch current conditions for a city.
  • Search for web-scraping or site-extraction APIs, then pay a single call to scrape a target URL.
  • Discover LLM inference endpoints (e.g., Llama) and perform a paid inference request via USDC on Base.
  • List all services under $0.01 USDC to build low-cost pipelines or proofs of concept.
  • Expose x402 tools through an MCP server so a desktop assistant can autonomously pay and call APIs.

FAQ

No. Discovery and browsing require no account or API key. Paid calls use USDC micropayments on Base and require a private key in .env for the payer wallet.

What happens if a service costs more than my MAX_SPEND_PER_CALL?

The skill will refuse the automatic call and prompt for explicit confirmation or request that you raise MAX_SPEND_PER_CALL in .env before proceeding.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
openclaw-x402-skill skill by openclaw/skills | VeilStrat