# spipe Deep Search

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

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

## Facts

- Endpoint: GET https://spip32.vercel.app/search/deep?utm_source=zero.xyz
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-31
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/spipe-deep-search-15c46e36
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_8Tn9GD77dUCZlmkx7q45r

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-search-15c46e36
```

Example prompt: Search the web for the latest developments in quantum computing from the past week and give me the top 5 results.

## When to prefer this

Choose this endpoint when you need fresh, filtered web search results with control over recency (day/week/month/year) and result count. It is well-suited for AI agent research workflows requiring up-to-date information rather than static knowledge. Prefer it over general knowledge retrieval when you need live web data with a specific time window.

## 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
- No results found for obscure or overly specific queries
- Payment failure or insufficient funds returns a 402 response
- Rate limiting or service unavailability returns 429 or 503

## 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, potentially including titles, URLs, snippets, and metadata for each result, filtered by the requested recency window and limited to the specified count.

## 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-search-15c46e36/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from spip32.vercel.app](https://www.zero.xyz/host/spip32.vercel.app/llms.txt)