# spipe Deep Web Search

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

Performs a deep web search with optional recency filtering and result count control, returning structured search results for AI agent research workflows.

## Facts

- Endpoint: GET https://spip3.vercel.app/search/deep
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/spipe-deep-web-search-f525f9ba
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_XCTe5-7kEmOLzrsbtQE1Q

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-deep-web-search-f525f9ba
```

Example prompt: Search the web for the latest news about OpenAI's GPT-5 release from the past week and give me 10 results.

## When to prefer this

Choose this endpoint when an AI agent needs fresh, broad web search results with recency control — especially useful for news monitoring, competitive research, or any task requiring information beyond a training cutoff. The 'freshness' filter makes it superior to generic search APIs when temporal relevance matters. Best for agents that need multiple results (configurable via 'count') rather than a single URL extraction. Prefer over scraping endpoints when the agent needs discovery (finding relevant URLs) rather than deep extraction from a known URL.

## Known failure modes

- Missing required 'q' parameter returns a 400 or validation error
- Invalid 'freshness' enum value (not day/week/month/year) causes a schema validation error
- Query returns no results for very niche or obscure topics
- Payment failure or insufficient USDC balance blocks the request via x402 protocol
- Rate limiting or quota exhaustion if called too frequently
- Network timeout for complex or broad queries

## How this service works

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

## Output

A JSON object containing web search results relevant to the query, likely including page titles, URLs, snippets or summaries, and relevance signals. The number of results is controlled by the 'count' parameter and can be filtered by recency using the 'freshness' parameter (day, week, month, year).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "q"
 ],
 "properties": {
  "q": {
   "type": "string",
   "description": "Search query"
  },
  "count": {
   "type": "integer",
   "description": "Number of results"
  },
  "freshness": {
   "enum": [
    "day",
    "week",
    "month",
    "year"
   ],
   "type": "string",
   "description": "Filter by recency"
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

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