Call paid APIs on Base with automatic USDC payment via x402 protocol.
Works with
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
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionpay-for-serviceExecute the skills CLI command in your project's root directory to begin installation:
Fetches pay-for-service from coinbase/agentic-wallet-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate pay-for-service. Access via /pay-for-service in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
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
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
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
90
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
90
stars
Use the npx [email protected] x402 pay command to call paid API endpoints with automatic USDC payment on Base.
npx [email protected] status
If the wallet is not authenticated, refer to the authenticate-wallet skill.
npx [email protected] 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 |
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).
Before constructing the command, validate all user-provided values to prevent shell injection:
https:// or http://. Reject if it contains spaces, semicolons, pipes, backticks, or shell metacharacters.^\d+$).Do not pass unvalidated user input into the command.
# Make a GET request (auto-pays)
npx [email protected] x402 pay https://example.com/api/weather
# Make a POST request with body
npx [email protected] x402 pay https://example.com/api/sentiment -X POST -d '{"text": "I love this product"}'
# Limit max payment to $0.10
npx [email protected] x402 pay https://example.com/api/data --max-amount 100000
npx [email protected] status to check, see authenticate-wallet skill)npx [email protected] balance to check)search-for-service skill to find services firstawal auth login <email> first, or see authenticate-wallet skillsearch-for-service to find valid endpointsfund skillMake data-driven prioritization decisions faster
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
pay-for-service has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for pay-for-service matched our evaluation — installs cleanly and behaves as described in the markdown.
We added pay-for-service from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
pay-for-service fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in pay-for-service — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
pay-for-service reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend pay-for-service for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
pay-for-service fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Solid pick for teams standardizing on skills: pay-for-service is focused, and the summary matches what you get after install.
Registry listing for pay-for-service matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 52