# x402serps Batch Web Search API

> x402serps Batch Web Search API is a paid API for AI agents from x402serps.com, paid per call via x402, $0.08/call, status unknown (last checked 2026-11-16).

Executes up to 25 Google web search queries in a single batch call, returning ranked results with URLs, titles, and snippets, paid per call in USDC via x402

## Facts

- Endpoint: POST https://x402serps.com/api/v1/batch?utm_source=zero.xyz
- Price: $0.08/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402serps-batch-web-search-api-39882f23
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wouZSfBvomMRfV1NDz8vw

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 x402serps-batch-web-search-api-39882f23 -d '<json body>'
```

Example prompt: Search the web for these three topics and give me the top 5 results each: 'best open-source LLMs 2025', 'x402 payment protocol overview', and 'Base blockchain developer tools'.

## When to prefer this

Choose this endpoint when an AI agent needs to run multiple web searches in a single round-trip without managing API keys or subscriptions. It is ideal for agents that perform research across several topics simultaneously, want pay-as-you-go pricing via USDC micropayments on Base, or need to avoid OAuth/account setup overhead. Prefer it over single-query endpoints when batching 2–25 queries to reduce latency and cost per lookup.

## Known failure modes

- Payment failure — insufficient USDC balance or x402 payment not accepted returns a 402 error
- Invalid queries array — empty array or more than 25 queries returns a validation error
- num out of range — values below 1 or above 20 may be rejected or clamped
- Individual query errors — a specific query within the batch may return an error field while others succeed
- Network/provider downtime — upstream Google search outage may cause partial or full batch failure
- Rate limiting — excessive concurrent requests may result in throttling

## How this service works

x402serps: up to 25 Web search queries in one paid call

## Output

A JSON object containing a count of queries processed and an array of per-query result objects, each including the original query string, the provider used, any error message, and an array of up to 20 results with URL, page title, snippet text, and 1-based position ranking.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "num": {
   "type": "number",
   "description": "Results per query 1-20, default 10"
  },
  "queries": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "description": "1-25 queries"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "count": 2,
  "results": [
   {
    "query": "x402 protocol",
    "results": [
     {
      "url": "https://www.x402.org/",
      "title": "x402 payments protocol",
      "snippet": "An open standard for internet-native payments over HTTP 402.",
      "position": 1
     }
    ],
    "provider": "primary"
   }
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402serps-batch-web-search-api-39882f23/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402serps.com](https://www.zero.xyz/host/x402serps.com/llms.txt)
