pay-for-service

Automate paid API calls by paying USDC on x402 endpoints.

1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/clawgame/clawgame --skill pay-for-service-clawgame
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pay-for-service
Source: https://github.com/clawgame/clawgame/tree/main/.agents/skills/pay-for-service
Command: npx skills add https://github.com/clawgame/clawgame --skill pay-for-service-clawgame

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow enables automated payment for API calls by automatically paying USDC on x402 endpoints, removing manual payment steps and simplifying access to paid services.

Core Features & Use Cases

  • Auto-pay paid APIs and paid services via x402 on Base.
  • Supports configurable HTTP method, headers, and payload with max-amount enforcement.
  • Use cases include accessing paid data, paid analytics, or any API that charges per call.

Quick Start

Authenticate your wallet, then run a paid x402 request to the desired URL using npx awal@latest x402 pay.

Frequently Asked Questions about pay-for-service

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate USDC payments for paid API calls on Base?

To automate USDC payments for paid API calls on Base, you use the x402 pay workflow to send HTTP requests with optional payloads and headers. It requires wallet authentication and sufficient USDC balance to automatically pay x402 endpoints.

What is the x402 payment protocol for accessing paid services?

The x402 payment protocol is a standard that enables automated USDC payments on Base to access paid APIs. It removes manual payment steps by facilitating HTTP requests that automatically settle per-call charges directly through wallet authentication.

Do I need a specific wallet balance to use x402 endpoints?

Yes, to use x402 endpoints you need a wallet with authentication enabled and a sufficient USDC balance on Base. The workflow enforces max-amount controls during the paid API request, but it cannot proceed if your wallet lacks funds.

Can I send custom headers and payloads when paying for APIs via x402?

Yes, you can send custom HTTP headers and payloads when automating paid API calls via x402. The workflow supports configurable HTTP methods and includes max-amount enforcement to control your USDC spending on each request.

Why does my automated x402 payment fail on a discovered API endpoint?

Your automated x402 payment fails if the target endpoint is not compatible with the x402 payment workflow. Additionally, the request will fail if your wallet lacks authentication or does not have a sufficient USDC balance on Base.

How do I execute a paid x402 request from the command line?

To execute a paid x402 request from the command line, authenticate your wallet and run the command `npx awal@latest x402 pay` with your desired URL. This triggers the automated USDC payment workflow for the target API endpoint.