# spipe Deep Web Search

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

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://spip33.vercel.app/search/deep
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/spipe-deep-web-search-eff4d56b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_uO4njIZLNc1352jXgwx6r

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-eff4d56b
```

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 an AI agent needs to retrieve fresh, real-time web search results — especially when recency matters (e.g., news, current events, recent releases). It is well-suited for research tasks where the agent needs multiple results filtered by time window. Prefer it over static knowledge bases when up-to-date information is critical. The per-call x402 micropayment model on Base makes it suitable for pay-as-you-go agent workflows without subscription overhead.

## Known failure modes

- Missing required 'q' parameter returns a 400 error
- Invalid 'freshness' enum value (not one of day/week/month/year) causes a validation error
- Payment not provided or insufficient USDC triggers a 402 Payment Required response
- No results found for highly specific or obscure queries
- Rate limiting or quota exceeded on the underlying search provider
- Network timeout if the deep search takes too long to aggregate results

## 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 page titles, URLs, snippets, and metadata. Results may be filtered by recency (day, week, month, or year) and limited to a 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-web-search-eff4d56b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from spip33.vercel.app](https://www.zero.xyz/host/spip33.vercel.app/llms.txt)