# PennyRail Resource Node – Mock OpenAPI Settlement

> PennyRail Resource Node – Mock OpenAPI Settlement is a paid API for AI agents from pennyrail.vercel.app, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-23).

Accepts a generic input object and returns a mock settlement response via a machine-readable x402 payment-gated API node

## Facts

- Endpoint: POST https://pennyrail.vercel.app/api/p/nano/openapi.mock-response--proven-openapi-mock-response?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pennyrail-resource-node-mock-openapi-settlement-e946a975
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_4KiXDvX8mtbckDeRM9qPF

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-resource-node-mock-openapi-settlement-e946a975 -d '<json body>'
```

Example prompt: Send a settlement request to the PennyRail nano node with my input data — it's a $0.001 USDC pay-per-call endpoint and I need the mock OpenAPI response back.

## When to prefer this

Choose this endpoint when you need to integrate or test an x402 micropayment-gated settlement node with minimal per-call cost ($0.001 USDC), especially in agent pipelines that require machine-readable pay-per-call settlement flows. It is best suited for automated agent workflows, mock API testing, and x402 protocol integration validation rather than production financial settlement.

## Known failure modes

- Payment not authorized — x402 challenge not fulfilled, resulting in 402 Payment Required
- Malformed input — missing required 'input' field returns validation error
- Endpoint unavailable — Vercel deployment not active, returns 503 or timeout
- Empty or null input object — may return unexpected mock response or error
- Rate limiting — too many rapid calls may trigger throttling

## How this service works

Machine-readable settlement service

## Output

A free-form JSON object representing the mock settlement response; schema is open (additionalProperties: true), so field names and values will vary depending on the mock configuration of the node.

## 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-resource-node-mock-openapi-settlement-e946a975/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)