explainx.ainewsletter3.4k
Productivity

x402▌

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

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

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

Discover and call paid APIs using the X402 payment protocol with automatic USDC payments on Base.

  • ›Search a bazaar of paid services by keyword, list all available resources, or inspect an endpoint's price and requirements without paying
  • ›Make authenticated requests to X402 endpoints with automatic USDC payment in atomic units, supporting GET, POST, PUT, DELETE, and PATCH methods
  • ›Includes query parameters, custom headers, request body support, and max-amount spending limits to control p
skill.md

x402 Payment Protocol

Use the npx [email protected] x402 commands to discover, inspect, and call paid API endpoints using the X402 payment protocol. Payments are made in USDC on Base.

Workflow

The typical x402 workflow is:

  1. Find a service - Search the bazaar or get details for a known endpoint
  2. Check requirements - Inspect price, method, and input schema
  3. Make the request - Call the endpoint with automatic USDC payment

Commands

Search the Bazaar

Find paid services by keyword using BM25 relevance search:

npx [email protected] x402 bazaar search <query> [-k <n>] [--force-refresh] [--json]
Option Description
-k, --top <n> Number of results (default: 5)
--force-refresh Re-fetch resource index from CDP API
--json Output as JSON

Results are cached locally at ~/.config/awal/bazaar/ and auto-refresh after 12 hours.

List Bazaar Resources

Browse all available resources:

awal x402 bazaar list [--network <network>] [--full] [--json]
Option Description
--network <name> Filter by network (base, base-sepolia)
--full Show complete details including schemas
--json Output as JSON

Discover Payment Requirements

Inspect an endpoint's x402 payment requirements without paying:

awal x402 details <url> [--json]

Auto-detects the correct HTTP method (GET, POST, PUT, DELETE, PATCH) by trying each until it gets a 402 response, then displays price, accepted payment schemes, network, and input/output schemas.

Make a Paid Request

Call an x402 endpoint with automatic USDC payment:

awal x402 pay <url> [-X <method>] [-d <json>] [-q <params>] [-h <json>] [--max-amount <n>] [--json]
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

Examples

# Search for weather-related paid APIs
awal x402 bazaar search "weather"

# Search with more results
awal x402 bazaar search "sentiment analysis" -k 10

# Check what an endpoint costs
awal x402 details https://example.com/api/weather

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

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

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

# Browse all bazaar resources with full details
awal x402 bazaar list --full

USDC Amounts

X402 uses USDC atomic units (6 decimals):

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

Prerequisites

  • Search/Details: No authentication needed
  • Pay: Must be authenticated (awal auth login <email>) with sufficient USDC balance (awal balance)

Error Handling

  • "Not authenticated" - Run awal auth login <email> first
  • "No X402 payment requirements found" - URL may not be an x402 endpoint
  • "CDP API returned 429" - Rate limited; cached data will be used if available
  • "Insufficient balance" - Fund wallet with USDC (awal balance to check)
how to use x402

How to use x402 on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • ›Cursor installed and configured on your development machine
  • ›Node.js version 16.0+ with npm package manager (verify with node --version)
  • ›Active project directory or workspace where you want to add x402
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/coinbase/agentic-wallet-skills --skill x402

The skills CLI fetches x402 from GitHub repository coinbase/agentic-wallet-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/x402

Reload or restart Cursor to activate x402. Access the skill through slash commands (e.g., /x402) or your agent's skill management interface.

⚠

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

Additional Resources

›View source code on GitHub›Skills CLI documentation›Learn more about Cursor›What are agent skills?

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases▌

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

✓

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

✓

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

✓

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

✓

Save 3-5 hours/week on communication overhead

Implementation Guide▌

Prerequisites

  • ›Claude Desktop or compatible AI client
  • ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • ›Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • ⚠Not validating competitive research—verify facts before sharing
  • ⚠Accepting user stories without involving engineering team
  • ⚠Over-relying on frameworks without qualitative judgment
  • ⚠Not customizing outputs to company culture and communication style
  • ⚠Skipping stakeholder validation of generated requirements

Best Practices▌

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • −Don't publish competitive analysis without fact-checking
  • −Don't finalize user stories without engineering review
  • −Don't make prioritization decisions solely on AI scoring
  • −Don't skip customer validation of generated requirements
  • −Don't ignore company-specific context and culture

💡 Pro Tips

  • ★Provide context: company goals, constraints, customer feedback
  • ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • ★Use skill for 70% generation + 30% customization to company needs

When to Use This▌

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path▌

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

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

Ratings

4.4★★★★★63 reviews
  • ★★★★★James Johnson· Dec 28, 2024

    We added x402 from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • ★★★★★Valentina Thomas· Dec 28, 2024

    x402 is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • ★★★★★James Perez· Dec 24, 2024

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

  • ★★★★★James Gill· Dec 24, 2024

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

  • ★★★★★Hiroshi Martin· Dec 24, 2024

    x402 reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • ★★★★★Li Thomas· Dec 20, 2024

    x402 reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • ★★★★★Diya Haddad· Dec 20, 2024

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

  • ★★★★★Diya Ghosh· Nov 19, 2024

    x402 fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • ★★★★★Chen Mehta· Nov 15, 2024

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

  • ★★★★★Nikhil Ramirez· Nov 15, 2024

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

showing 1-10 of 63

1 / 7