# PennyRail Web Search (proven-search)

> PennyRail Web Search (proven-search) is a paid API for AI agents from pennyrail.vercel.app, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-15).

Performs a web search query and returns results, accessible via a pay-per-call x402 micropayment settlement endpoint.

## Facts

- Endpoint: POST https://pennyrail.vercel.app/api/p/premium/web.search--proven-search
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pennyrail-web-search-proven-search-d59e5e0b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_P9vkubRQbGk5GeKst1hmu

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 pennyrail-web-search-proven-search-d59e5e0b -d '<json body>'
```

Example prompt: Search the web for the latest news on quantum computing breakthroughs and give me the top results.

## When to prefer this

Choose this endpoint when you need programmatic web search with micropayment-based access via the x402 protocol, particularly in agentic or automated pipelines where per-call USDC billing ($0.02) is acceptable. Prefer this over free-tier alternatives when you need reliable, pay-gated access without API key management overhead. Best suited for agents running on x402-compatible infrastructure that can handle HTTP 402 payment flows natively.

## Known failure modes

- Payment not settled or x402 authorization missing — request rejected before execution
- Malformed or missing 'input' object in request body — 400 validation error
- Search query too vague or empty — may return empty results or an error
- Rate limiting or quota exceeded on the underlying search provider — 429 or 503 response
- Network timeout if underlying search provider is slow — 504 or timeout error
- Unparseable response if the upstream search API changes schema — may return raw or null output

## How this service works

Machine-readable settlement service

## Output

Returns an object containing web search results, typically including page titles, URLs, snippets or descriptions of matching web pages, and potentially ranking or relevance metadata. The exact shape is open-ended (additionalProperties: true) but expected to mirror standard search result structure.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "additionalProperties": true
}
```

## More

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