pay-for-service

coinbase/agentic-wallet-skills · updated Apr 8, 2026

$npx skills add https://github.com/coinbase/agentic-wallet-skills --skill pay-for-service
0 commentsdiscussion
summary

Call paid APIs on Base with automatic USDC payment via x402 protocol.

  • Executes HTTP requests (GET, POST, etc.) to x402-enabled endpoints with atomic USDC payments handled automatically
  • Supports request customization through method, JSON body, query parameters, and custom headers
  • Includes payment controls: set maximum USDC amount per request and group related operations with correlation IDs
  • Requires wallet authentication and sufficient USDC balance; validates all user input to prev
skill.md

Making Paid x402 Requests

Use the npx awal@2.0.3 x402 pay command to call paid API endpoints with automatic USDC payment on Base.

Confirm wallet is initialized and authed

npx awal@2.0.3 status

If the wallet is not authenticated, refer to the authenticate-wallet skill.

Command Syntax

npx awal@2.0.3 x402 pay <url> [-X <method>] [-d <json>] [-q <params>] [-h <json>] [--max-amount <n>] [--json]

Options

Option Description
-X, --method <method> HTTP method (default: GET)
-d, --data <json> Request body as JSON string
-q, --query <params> Query parameters as JSON string
-h, --headers <json> Custom HTTP headers as JSON string
--max-amount <amount> Max payment in USDC atomic units (1000000 = $1.00)
--correlation-id <id> Group related operations
--json Output as JSON

USDC Amounts

X402 uses USDC atomic units (6 decimals):

Atomic Units USD
1000000 $1.00
100000 $0.10
50000 $0.05
10000 $0.01

IMPORTANT: Always single-quote amounts that use $ to prevent bash variable expansion (e.g. '$1.00' not $1.00).

Input Validation

Before constructing the command, validate all user-provided values to prevent shell injection:

  • url: Must be a valid URL starting with https:// or http://. Reject if it contains spaces, semicolons, pipes, backticks, or shell metacharacters.
  • data (-d): Must be valid JSON. Always wrap in single quotes to prevent shell expansion.
  • max-amount: Must be a positive integer (^\d+$).

Do not pass unvalidated user input into the command.

Examples

# Make a GET request (auto-pays)
npx awal@2.0.3 x402 pay https://example.com/api/weather

# Make a POST request with body
npx awal@2.0.3 x402 pay https://example.com/api/sentiment -X POST -d '{"text": "I love this product"}'

# Limit max payment to $0.10
npx awal@2.0.3 x402 pay https://example.com/api/data --max-amount 100000

Prerequisites

  • Must be authenticated (npx awal@2.0.3 status to check, see authenticate-wallet skill)
  • Wallet must have sufficient USDC balance (npx awal@2.0.3 balance to check)
  • If you don't know the endpoint URL, use the search-for-service skill to find services first

Error Handling

  • "Not authenticated" - Run awal auth login <email> first, or see authenticate-wallet skill
  • "No X402 payment requirements found" - URL may not be an x402 endpoint; use search-for-service to find valid endpoints
  • "Insufficient balance" - Fund wallet with USDC; see fund skill

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.752 reviews
  • Layla Li· Dec 28, 2024

    pay-for-service has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Kabir Li· Dec 24, 2024

    Registry listing for pay-for-service matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Charlotte Jain· Dec 24, 2024

    We added pay-for-service from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Sakura Jackson· Dec 20, 2024

    pay-for-service fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Dhruvi Jain· Dec 12, 2024

    Useful defaults in pay-for-service — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Sakura Torres· Dec 12, 2024

    pay-for-service reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Kabir Reddy· Dec 4, 2024

    I recommend pay-for-service for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Sakura White· Nov 19, 2024

    pay-for-service fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Diya Anderson· Nov 15, 2024

    Solid pick for teams standardizing on skills: pay-for-service is focused, and the summary matches what you get after install.

  • Kabir Anderson· Nov 15, 2024

    Registry listing for pay-for-service matched our evaluation — installs cleanly and behaves as described in the markdown.

showing 1-10 of 52

1 / 6