# Signal Engine Tavily Web Search Gateway

> Signal Engine Tavily Web Search Gateway is a paid API for AI agents from signal-engine-production-d88d.up.railway.app, paid per call via x402, $0.012/call, status unknown (last checked 2026-09-15).

Performs AI-powered web searches via Tavily, returning ranked results with titles, URLs, and content snippets

## Facts

- Endpoint: POST https://signal-engine-production-d88d.up.railway.app/v1/gateway/search/tavily
- Price: $0.012/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/signal-engine-tavily-web-search-gateway-2ec3ca81
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_nrJFjDv4x5JgJylt59ooy

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 signal-engine-tavily-web-search-gateway-2ec3ca81 -d '<json body>'
```

Example prompt: Search the web for the latest news on Bitcoin ETF approval and give me the top results with their titles and summaries.

## When to prefer this

Use this endpoint when you need real-time web search results with AI-powered relevance ranking via Tavily, especially within a micropayment (x402) workflow where per-call billing is acceptable. Prefer over generic search APIs when Tavily's scored, content-rich results are specifically needed.

## Known failure modes

- Invalid or missing query string returns an error
- Tavily API downstream outage causes search failure
- Rate limiting or quota exceeded on Tavily side
- Payment not processed via x402 protocol results in 402 response
- Malformed request body returns 400 error

## How this service works

AI-powered web search via Tavily

## Output

A JSON object containing the original query, an array of ranked results (each with URL, title, content snippet, and relevance score), and total response time in seconds.

## Example request

```json
{
 "query": "artificial intelligence trends 2024",
 "topic": "general",
 "exclude_domains": [],
 "include_domains": []
}
```

## Request schema (JSON Schema)

```json
{
 "output": {
  "required": [
   "query",
   "results"
  ],
  "properties": {
   "query": {
    "type": "string"
   },
   "results": {
    "type": "array",
    "items": {
     "type": "object",
     "properties": {
      "url": {
       "type": "string",
       "format": "uri"
      },
      "score": {
       "type": "number"
      },
      "title": {
       "type": "string"
      },
      "content": {
       "type": "string"
      }
     }
    }
   },
   "response_time": {
    "type": "number"
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/signal-engine-tavily-web-search-gateway-2ec3ca81/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from signal-engine-production-d88d.up.railway.app](https://www.zero.xyz/host/signal-engine-production-d88d.up.railway.app/llms.txt)