# Agent Search Result Judge

> Agent Search Result Judge is a paid API for AI agents from agent-product-normalizer.vercel.app, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-18).

Ranks search results for a given task/query and flags duplicate, stale, and spam-like entries

## Facts

- Endpoint: GET https://agent-product-normalizer.vercel.app/api/v1/rank-results
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-search-result-judge-3f40b96f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Z6qVX2I2Gj0dg5o2kmSbO

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 agent-search-result-judge-3f40b96f
```

Example prompt: I have 15 search results from a web search about 'best electric vehicles under $40,000' — can you rank them by relevance, and flag any duplicates, spam sites, or outdated pages?

## When to prefer this

Choose this endpoint when an agent has already retrieved a set of search results and needs to prioritize, deduplicate, or clean them before downstream processing — especially useful in research, shopping, or news aggregation pipelines where result quality is mixed and manual review isn't practical.

## Known failure modes

- Malformed JSON in the results parameter causes a parsing error
- Query string exceeds 4000 character limit
- Results JSON array exceeds 20000 character limit
- Empty results array returns empty ranked output
- Ambiguous or very short query reduces ranking accuracy
- Results with no metadata (dates, domains) limit staleness detection

## How this service works

Rank search results for a task and flag duplicate, stale and spam-like results

## Output

A ranked and annotated list of the input search results, with each result scored for relevance to the query and flagged where applicable as duplicate, stale, or spam-like, helping the agent prioritize which results to act on.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "query",
      "results"
     ],
     "properties": {
      "query": {
       "type": "string",
       "maxLength": 4000,
       "description": "Search task/query"
      },
      "results": {
       "type": "string",
       "maxLength": 20000,
       "description": "JSON array of search results"
      }
     },
     "additionalProperties": false
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-search-result-judge-3f40b96f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent-product-normalizer.vercel.app](https://www.zero.xyz/host/agent-product-normalizer.vercel.app/llms.txt)