# Prysm — Tavily Web Search via x402

> Prysm — Tavily Web Search via x402 is a paid API for AI agents from prysm-kappa.vercel.app, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-15).

Executes a Tavily web search query through Prysm's x402-gated API, returning search results paid per-call in USDC on Base mainnet.

## Facts

- Endpoint: POST https://prysm-kappa.vercel.app/api/v1/providers/tavily
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/prysm-tavily-web-search-via-x402-2d6e53a5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wifzh7p2dWzcAP5t7djB0

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 prysm-tavily-web-search-via-x402-2d6e53a5 -d '<json body>'
```

Example prompt: Search the web for the latest news on Ethereum Layer 2 scaling solutions and give me a summary of what you find — use the Tavily search operation.

## When to prefer this

Choose this endpoint when your agent needs live, real-time web search results and you want to pay per-call in USDC via x402 on Base mainnet without managing a Tavily API key directly. Ideal for AI agents operating in crypto-native environments where x402 micropayments are already supported.

## Known failure modes

- Payment failure if insufficient USDC balance on Base mainnet — returns 402 Payment Required
- Invalid or unsupported operation string — returns error indicating operation not allowlisted
- Malformed input parameters — returns validation error
- Tavily upstream timeout or rate limit — may return 502 or 503
- Empty search results if query is too obscure or Tavily index lacks coverage

## How this service works

Prysm sells paid, agent-ready provider capabilities over x402 on Base mainnet using USDC.

## Output

Returns a JSON object with a 'data' field containing Tavily search results (URLs, titles, snippets, and content), a 'provider' field set to 'tavily', and an 'operation' field set to 'search'.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "object",
   "description": "Provider-specific operation parameters.",
   "additionalProperties": true
  },
  "operation": {
   "type": "string",
   "description": "Allowlisted operation for the selected provider."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {},
  "provider": "tavily",
  "operation": "search"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/prysm-tavily-web-search-via-x402-2d6e53a5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from prysm-kappa.vercel.app](https://www.zero.xyz/host/prysm-kappa.vercel.app/llms.txt)