# PennyRail Router Execute Standard

> PennyRail Router Execute Standard is a paid API for AI agents from pennyrail.vercel.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Routes a natural-language task or product ID to a PennyRail product and executes it, returning machine-readable results for $0.01 USDC per call

## Facts

- Endpoint: POST https://pennyrail.vercel.app/api/router/execute/standard
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pennyrail-router-execute-standard-3438ca6b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_JJX44z6vU2HGXuURUtwPM

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-standard-3438ca6b -d '<json body>'
```

Example prompt: Use PennyRail to summarize this article for me — here's the text: 'Artificial intelligence is reshaping industries at a rapid pace, from healthcare to finance...' — route it to whatever product fits best.

## When to prefer this

Choose this endpoint when you want to execute a micro-task through PennyRail's product catalog using either a natural-language intent (letting the router decide the best product) or a known productId for deterministic dispatch. It is ideal for low-cost ($0.01 USDC) on-demand automation where the task fits within PennyRail's available products. Prefer this over building custom integrations when the task is well-scoped and PennyRail's catalog covers it. If you need to discover or price a product first, use PennyRail's find/quote endpoints before calling this one.

## Known failure modes

- Payment not included or insufficient USDC — returns 402 Payment Required
- No matching PennyRail product found for the given intent — may return empty or error result
- Both intent and productId omitted — request may fail or produce undefined routing
- Input string malformed or too long for the resolved product
- Upstream PennyRail product unavailable — execution fails with service error
- Non-deterministic routing: same intent may resolve to different products across calls

## How this service works

Machine-readable settlement service

## Output

A flexible JSON object whose shape depends on the resolved PennyRail product — may include generated text, classifications, structured data, or other task outputs. The response schema is open-ended (additionalProperties: true), so the agent should inspect the returned fields dynamically.

## 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-standard-3438ca6b/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)