# x402 Bazaar Rank – In-Search Discovery

> x402 Bazaar Rank – In-Search Discovery is a paid API for AI agents from x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev, paid per call via x402, $0.008/call, status unknown (last checked 2026-09-18).

Returns ranked x402 services tagged 'search', scored by real 30-day call volumes and paying-wallet counts, with a snapshot receipt for auditability.

## Facts

- Endpoint: GET https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/in-search
- Price: $0.008/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-bazaar-rank-in-search-discovery-115cf4c8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ubIl7pZ3uroZpl0uGt2t6

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability x402-bazaar-rank-in-search-discovery-115cf4c8
```

Example prompt: Show me the top 25 search-tagged services on the x402 bazaar, ranked by number of paying wallets over the last 30 days, so I can find the most actively used paid search APIs.

## When to prefer this

Choose this endpoint when you need ranked, usage-verified discovery of x402 search-category services backed by real on-chain payment data rather than self-reported metadata. It is ideal for agents that must select a downstream search microservice based on demonstrated adoption (calls30d, payers30d) rather than static listings. Prefer it over generic API directories when you need an auditable receipt (snapshot hash + scoring revision) for reproducibility.

## Known failure modes

- Payment not attached or invalid x402 payment header → 402 Payment Required
- No services currently indexed under the 'search' tag → empty services array with count:0
- Snapshot index temporarily unavailable → 503 or timeout
- Invalid query parameters (e.g. unknown op or by field) → 400 Bad Request
- Rate limit exceeded → 429 Too Many Requests

## How this service works

Ranked discovery over the live x402 service market: every indexed service scored by real 30-day calls and paying-wallet bounds, with a receipt naming the snapshot hash and scoring revision.

## Output

A JSON object containing a ranked array of x402 services in the 'search' tag, each entry including service name, network chain ID, 30-day call count, 30-day unique paying wallets, price in USD, and resource URL. The envelope includes total matched count, the query parameters echoed back, the route, a generatedAt timestamp, and a snapshot hash plus scoring revision for auditability.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "count": 25,
  "query": {
   "by": "payers",
   "op": "top",
   "limit": 25,
   "where": {
    "tag": "search"
   }
  },
  "route": "/in-search",
  "matched": 359,
  "services": [
   {
    "name": "forecast api",
    "network": "eip155:8453",
    "calls30d": 310,
    "priceUsd": 0.01,
    "resource": "https://api.example.com/forecast",
    "payers30d": 42
   }
  ],
  "declaredBy": "agent",
  "generatedAt": "2026-09-17T12:00:00.000Z"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-bazaar-rank-in-search-discovery-115cf4c8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev](https://www.zero.xyz/host/x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/llms.txt)