# spipe Web Search

> spipe Web Search is a paid API for AI agents from spip36.vercel.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Performs a web search query and returns ranked results, optionally filtered by recency, country, language, and safe search level

## Facts

- Endpoint: GET https://spip36.vercel.app/search
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/spipe-web-search-21a0998d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tE1NUkxwGtriiB7G5wmtU

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 spipe-web-search-21a0998d
```

Example prompt: Search the web for the latest news on AI regulation in the EU — give me 10 results from the past week, using US results.

## When to prefer this

Prefer this endpoint when an AI agent needs to retrieve live web search results with fine-grained control over recency, country, language, and safe search — especially in x402/Base payment-enabled pipelines where per-call micropayments are acceptable. It is well-suited for research, news monitoring, and information retrieval tasks requiring up-to-date web content.

## Known failure modes

- Missing required 'q' parameter returns an error
- Invalid country or language code may return no results or an error
- Count outside 1-20 range may be clamped or rejected
- Payment failure (x402) if USDC balance is insufficient
- Freshness filter with no matching results returns empty result set
- Network timeout if upstream search provider is slow

## How this service works

Web search, content extraction, and research APIs for AI agents. x402 on Base.

## Output

Returns a JSON object containing ranked web search results, likely including page titles, URLs, snippets/descriptions, and metadata such as publication date, sourced from a web search index filtered by the provided query parameters.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "q"
 ],
 "properties": {
  "q": {
   "type": "string",
   "description": "Search query"
  },
  "count": {
   "type": "integer",
   "description": "Number of results (1-20)"
  },
  "country": {
   "type": "string",
   "description": "Country code (US, GB, etc.)"
  },
  "language": {
   "type": "string",
   "description": "Language code"
  },
  "freshness": {
   "enum": [
    "day",
    "week",
    "month",
    "year"
   ],
   "type": "string",
   "description": "Filter by recency"
  },
  "safesearch": {
   "enum": [
    "off",
    "moderate",
    "strict"
   ],
   "type": "string",
   "description": "Safe search level"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/spipe-web-search-21a0998d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from spip36.vercel.app](https://www.zero.xyz/host/spip36.vercel.app/llms.txt)