# Query Gap Radar

> Query Gap Radar is a paid API for AI agents from query-gap-radar-mainnet-production.up.railway.app, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-20).

Ranks aggregate agent-demand gaps using bounded, privacy-safe evidence events to surface unmet query categories.

## Facts

- Endpoint: POST https://query-gap-radar-mainnet-production.up.railway.app/v1/gaps?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/query-gap-radar-67d3dabe
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Nj-BduCjmXAVt8EK6kzAW

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 query-gap-radar-67d3dabe -d '<json body>'
```

Example prompt: Look at these 200 aggregate demand events from the past 14 days and rank the top 10 unmet query gaps where agents are struggling — only include gaps backed by at least 5 events, and keep everything privacy-safe with no raw prompts.

## When to prefer this

Choose this endpoint when you need to identify and prioritize unmet demand across a fleet of AI agents using aggregated, privacy-safe signals — not individual query logs. It is especially useful for product roadmap decisions, API marketplace gap analysis, or capacity planning where raw prompts cannot be shared. Prefer it over general analytics tools when privacy-bounded aggregate evidence is a hard requirement and ranked prioritization of gaps (not raw counts) is the desired output.

## Known failure modes

- Fewer than minEvidence events for a gap causes that gap to be filtered out entirely, potentially returning an empty list
- events array below minItems (1) or above maxItems (500) triggers a validation error
- windowDays outside 1–365 range returns a schema validation error
- limit outside 1–100 range rejected with validation error
- Submitting raw user prompts or PII in the events array may cause rejection or sanitization
- Stale or low-diversity events may yield uninformative or redundant gap rankings

## How this service works

Rank aggregate agent-demand gaps with bounded, privacy-safe evidence.

## Output

A ranked list of agent-demand gaps, each backed by bounded aggregate evidence counts, indicating which query categories are most underserved. Results include gap labels or categories, evidence volume, and ranking scores — no raw prompts or user identities are exposed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "now": {
   "type": "string"
  },
  "limit": {
   "type": "integer",
   "maximum": 100,
   "minimum": 1
  },
  "events": {
   "type": "array",
   "maxItems": 500,
   "minItems": 1,
   "description": "Privacy-safe aggregate demand events; raw prompts and identities are not accepted."
  },
  "windowDays": {
   "type": "integer",
   "maximum": 365,
   "minimum": 1
  },
  "minEvidence": {
   "type": "integer",
   "maximum": 500,
   "minimum": 1
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/query-gap-radar-67d3dabe/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from query-gap-radar-mainnet-production.up.railway.app](https://www.zero.xyz/host/query-gap-radar-mainnet-production.up.railway.app/llms.txt)