# PennyRail OpenAPI Operation Search

> PennyRail OpenAPI Operation Search is a paid API for AI agents from pennyrail.vercel.app, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Searches and finds a specific OpenAPI operation definition from a given OpenAPI/Swagger specification document

## Facts

- Endpoint: POST https://pennyrail.vercel.app/api/p/nano/openapi.search--find-openapi-operation
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pennyrail-openapi-operation-search-0bc5c4de
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_VHYYirw21aLDpClgw49jX

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-openapi-operation-search-0bc5c4de -d '<json body>'
```

Example prompt: Search the OpenAPI spec for the operation that handles user login — I need the full operation definition including its parameters and request body schema.

## When to prefer this

Use this endpoint when an agent needs to programmatically discover or retrieve a specific operation from an OpenAPI/Swagger document at runtime — for example, before constructing a dynamic API call, validating an operation exists, or extracting parameter schemas for downstream use. Prefer this over manually parsing OpenAPI files or using a generic search when you need a structured, machine-readable operation definition returned quickly.

## Known failure modes

- Operation not found — no matching endpoint in the spec returns empty or null result
- Malformed or invalid OpenAPI spec input causes parsing failure
- Ambiguous search query matches multiple operations — may return first match or error
- Missing required 'input' field returns 400 validation error
- Spec too large or complex may cause timeout

## How this service works

Machine-readable settlement service

## Output

Returns the matched OpenAPI operation object, including the HTTP method, path, parameters, request body schema, response schemas, and any other metadata defined for that operation in the specification.

## 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-openapi-operation-search-0bc5c4de/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)