# PennyRail Router Execute (Nano)

> PennyRail Router Execute (Nano) 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-13).

Routes a natural-language intent or explicit product ID to a PennyRail micro-service and executes it, returning the service's result for $0.001 USDC per call.

## Facts

- Endpoint: POST https://pennyrail.vercel.app/api/router/execute/nano
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pennyrail-router-execute-nano-999a4ff9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zHxZwcelSSFz68KCLoCzG

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-router-execute-nano-999a4ff9 -d '<json body>'
```

Example prompt: Use PennyRail's nano router to summarize this text — 'Quarterly earnings exceeded expectations by 12%, driven by software revenue' — and route it as the intent 'summarize this text for an executive briefing'.

## When to prefer this

Choose this endpoint when you need to dynamically route a natural-language intent to a low-cost ($0.001 USDC) micro-service without knowing the exact product upfront, or when you already have a PennyRail product ID and want the cheapest execution path. It is ideal for agent workflows that need pay-per-call compute without managing multiple API integrations. Prefer this over direct product endpoints when intent-based routing is desirable or when building cost-sensitive pipelines that leverage PennyRail's settlement layer.

## Known failure modes

- Intent is too ambiguous for PennyRail to resolve a product — returns an error or empty result
- Invalid or unknown productId supplied — service cannot find the product
- Input string is malformed or too long for the resolved product
- Payment of $0.001 USDC fails due to insufficient wallet balance or x402 protocol error
- Network or cold-start latency on Vercel causes timeout
- Product execution itself fails and returns a pass-through error from the underlying service

## How this service works

Machine-readable settlement service

## Output

A flexible JSON object whose shape depends on which PennyRail product was resolved and executed; may include processed text, transformed data, classification results, or any other product-specific output. The schema is open-ended (additionalProperties: true).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "string",
   "description": "Input passed to the resolved PennyRail product."
  },
  "intent": {
   "type": "string",
   "description": "Natural-language task. Omit when productId is supplied."
  },
  "productId": {
   "type": "string",
   "description": "Optional exact PennyRail product id returned by find/quote."
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/pennyrail-router-execute-nano-999a4ff9/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)