# x402 Bazaar Rank – In-Compliance Route

> x402 Bazaar Rank – In-Compliance Route is a paid API for AI agents from x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev, paid per call via x402, $0.032/call, status unknown (last checked 2026-10-22).

Returns a ranked list of live x402 services tagged 'compliance', scored by real 30-day call volume and paying-wallet counts, with a snapshot hash and scoring revision receipt.

## Facts

- Endpoint: GET https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/in-compliance?utm_source=zero.xyz
- Price: $0.032/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-bazaar-rank-in-compliance-route-820888eb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0f0617IZ6CK7GuMYB9Pe8

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-compliance-route-820888eb
```

Example prompt: Show me the top 25 compliance-tagged services on the x402 bazaar, ranked by number of paying wallets over the last 30 days, and include the snapshot hash so I can verify the data.

## When to prefer this

Choose this endpoint when you need a ranked, usage-verified list of x402 services specifically in the compliance category, backed by real 30-day on-chain payment activity rather than self-reported metadata. Prefer it over generic x402 service indexes when auditability matters (snapshot hash + scoring revision receipt) or when selecting compliance vendors based on actual market adoption rather than listing order.

## Known failure modes

- Payment not included or invalid x402 payment header → 402 Payment Required
- Snapshot index temporarily unavailable → 503 Service Unavailable
- No services matched the compliance tag → empty services array with count 0
- Malformed query parameters → 400 Bad Request
- Worker cold-start latency causing timeout on first request

## How this service works

Highest-demand x402 services tagged 'compliance': ranked by 30-day unique paying wallets, with calls, price, network and calls-per-payer for each. 184 providers and 278 paying wallets measured in this tag.

## Output

A JSON object containing: a count of returned services, the query parameters used (ranking dimension, operator, limit, tag filter), the route (/in-compliance), total matched services, an array of ranked services each with name, network chain ID, 30-day calls, USD price, resource URL, and 30-day payer count, plus metadata fields for who declared the data, and a generatedAt ISO timestamp with snapshot hash 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": "compliance"
   }
  },
  "route": "/in-compliance",
  "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-compliance-route-820888eb/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)