search-for-service▌
coinbase/agentic-wallet-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Search and discover paid API services available on the x402 bazaar marketplace.
- ›Query the marketplace using BM25 relevance search, list all available resources, or inspect specific endpoints to see pricing and payment requirements without paying
- ›Supports filtering by network (base, base-sepolia) and output formats (human-readable or JSON)
- ›Results are cached locally and auto-refresh every 12 hours; no authentication required for any search or discovery operation
- ›Use as a fallback w
Searching the x402 Bazaar
Use the npx [email protected] x402 commands to discover and inspect paid API endpoints available on the x402 bazaar marketplace. No authentication or balance is required for searching.
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:
npx [email protected] 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:
npx [email protected] 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.
Examples
# Search for weather-related paid APIs
npx [email protected] x402 bazaar search "weather"
# Search with more results
npx [email protected] x402 bazaar search "sentiment analysis" -k 10
# Browse all bazaar resources with full details
npx [email protected] x402 bazaar list --full
# Check what an endpoint costs
npx [email protected] x402 details https://example.com/api/weather
Prerequisites
- No authentication needed for search, list, or details commands
Next Steps
Once you've found a service you want to use, use the pay-for-service skill to make a paid request to the endpoint.
Error Handling
- "CDP API returned 429" - Rate limited; cached data will be used if available
- "No X402 payment requirements found" - URL may not be an x402 endpoint
How to use search-for-service on Cursor
AI-first code editor with Composer
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 search-for-service
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches search-for-service from GitHub repository coinbase/agentic-wallet-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate search-for-service. Access the skill through slash commands (e.g., /search-for-service) 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.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
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.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 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▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★26 reviews- ★★★★★Ganesh Mohane· Dec 24, 2024
search-for-service fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Liam Singh· Dec 16, 2024
I recommend search-for-service for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Sakshi Patil· Nov 15, 2024
Registry listing for search-for-service matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Olivia Reddy· Nov 7, 2024
Keeps context tight: search-for-service is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Ira Khanna· Nov 7, 2024
Registry listing for search-for-service matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Henry Thomas· Oct 26, 2024
search-for-service is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Diya Gupta· Oct 26, 2024
search-for-service reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Chaitanya Patil· Oct 6, 2024
search-for-service reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Piyush G· Sep 25, 2024
I recommend search-for-service for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Aditi Tandon· Sep 17, 2024
search-for-service fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 26