Search For Service
Discover paid x402 bazaar APIs your agent can call when a task needs an external capability or no other skill fits.
Overview
search-for-service is an agent skill most often used in Build (also Ship integrations, Operate iterate) that searches the x402 bazaar for paid API services via Awal CLI—usable whenever you need to discover an external en
Install
npx skills add https://github.com/coinbase/agentic-wallet-skills --skill search-for-serviceWhat is this skill?
- Vector search across the x402 bazaar with keyword queries and up to 20 ranked results
- Filters for chain network, payment scheme, and max price before you commit spend
- Inspect service metadata with `x402 details` without wallet balance or auth to search
- Documented Awal CLI: `npx awal@2.10.0 x402 bazaar search` and `details` via allowed Bash tools
- Explicit fallback: when no skill clearly matches, search the bazaar for a paid service
- Top-k search supports 1–20 results (default 20)
- Awal CLI pinned at npx awal@2.10.0 for bazaar search and details
Adoption & trust: 2.8k installs on skills.sh; 110 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need a concrete paid API for a task but do not know what exists on the x402 marketplace or how to filter by chain, scheme, and price.
Who is it for?
Solo builders wiring agentic wallets who want marketplace discovery before spending USDC on x402 endpoints.
Skip if: Teams that already have fixed API contracts, cannot run `npx` Bash in the agent, or need free-only integrations with no paid bazaar.
When should I use this skill?
You or the user want to find available services, see what's available, discover APIs, need an external service for a task, or as a fallback when no other skill clearly matches.
What do I get? / Deliverables
You get a shortlist of bazaar services with inspectable details so you can choose an endpoint and hand off to wallet or invocation skills for paid calls.
- Ranked bazaar search results with optional JSON output
- Service detail inspection from `x402 details` for chosen listings
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Build → integrations because the skill’s core job is wiring the agent to marketplace APIs via Awal CLI search and detail commands. Subphase integrations matches browsing and selecting third-party paid endpoints rather than implementing your own backend from scratch.
Where it fits
Search the bazaar for image or data APIs before scaffolding an agent tool that pays per request.
Confirm a paid third-party endpoint exists before launch-day automation that cannot be self-hosted in time.
When production workflow hits a missing capability, search the bazaar as a fallback instead of forking a new integration from scratch.
How it compares
Marketplace discovery via Awal CLI—not a generic web search skill or an MCP catalog browser.
Common Questions / FAQ
Who is search-for-service for?
Solo and indie builders using agentic wallet stacks who need to find x402 bazaar APIs for agent tasks without manually browsing docs.
When should I use search-for-service?
During Build integrations when picking paid APIs; during Ship when a workflow lacks a tool; during Operate iterate when you need a new external capability—especially for “find me an API for…”, “what services are available?”, or when no other skill matches.
Is search-for-service safe to install?
Review the Security Audits panel on this Prism page and restrict agent Bash to the documented `npx awal@2.10.0 x402` commands; searching alone does not require wallet keys.
SKILL.md
READMESKILL.md - Search For Service
# Searching the x402 Bazaar Use the `npx awal@2.10.0 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 CDP's vector search: ```bash npx awal@2.10.0 x402 bazaar search <query> [-k <n>] [--network <network>] [--scheme <scheme>] [--max-price <price>] [--json] ``` | Option | Description | | ----------------------- | ------------------------------------------------------------------------ | | `-k, --top <n>` | Number of results, 1–20 (default: 20) | | `--network <name>` | Filter by chain (base, base-sepolia, polygon, solana, solana-devnet) | | `--scheme <scheme>` | Filter by payment scheme: `exact` or `upto` | | `--max-price <price>` | Maximum price in USD (e.g. `0.01`) | | `--asset <address>` | Filter by payment asset address | | `--pay-to <address>` | Filter by recipient wallet address | | `--extensions <type>` | Filter by extension type (e.g. `outputSchema`, `bazaar`) | | `--json` | Output as JSON | ### List Bazaar Resources Browse all available resources: ```bash npx awal@2.10.0 x402 bazaar list [--network <network>] [--full] [--refresh] [--json] ``` | Option | Description | | ------------------ | -------------------------------------------------------------------- | | `--network <name>` | Filter by chain (base, base-sepolia, polygon, solana, solana-devnet) | | `--full` | Show complete details including schemas | | `--refresh` | Re-fetch resource index from CDP API | | `--json` | Output as JSON | ### Discover Payment Requirements Inspect an endpoint's x402 payment requirements without paying: ```bash npx awal@2.10.0 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 ```bash # Search for weather-related paid APIs npx awal@2.10.0 x402 bazaar search "weather" # Search with more results npx awal@2.10.0 x402 bazaar search "sentiment analysis" -k 10 # Browse all bazaar resources with full details npx awal@2.10.0 x402 bazaar list --full # Check what an endpoint costs npx awal@2.10.0 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