# PennyRail Batch Utility Runner

> PennyRail Batch Utility Runner is a paid API for AI agents from pennyrail.vercel.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-22).

Executes multiple utilities in a single batch call via a machine-readable settlement endpoint, accepting a generic input object and returning combined results.

## Facts

- Endpoint: POST https://pennyrail.vercel.app/api/p/standard/batch.utility--run-multiple-utilities?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pennyrail-batch-utility-runner-355f9547
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_iIj9ezNqSSEb6jQ6zUxyB

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-batch-utility-runner-355f9547 -d '<json body>'
```

Example prompt: Run a batch of utility operations in one go using PennyRail — pass in the combined input object for all utilities I need executed, and give me back the full set of results.

## When to prefer this

Choose this endpoint when you need to execute multiple utility operations in a single network round-trip, minimizing latency and paying only one $0.01 USDC fee for the batch rather than making separate calls. It is best suited for automation workflows where several lightweight utility tasks can be parallelized or pipelined, and where the caller can construct a combined input object upfront.

## Known failure modes

- Missing or malformed 'input' object returns a 400-level validation error
- One failing utility may cause the entire batch to fail or return partial results
- Payment not settled (402) if x402 micropayment header is absent or invalid
- Ambiguous or undocumented utility identifiers may produce empty or unexpected output
- Rate limiting or cold-start latency on Vercel deployment may cause timeouts

## How this service works

Machine-readable settlement service

## Output

A generic JSON object containing the combined outputs of all utilities executed in the batch. The schema is open-ended (additionalProperties: true), so the structure depends on which utilities were invoked and their individual return shapes.

## 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-batch-utility-runner-355f9547/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)