# PennyRail Execute Intel

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

Routes a natural-language task or product ID to a PennyRail product and executes it, returning a machine-readable result

## Facts

- Endpoint: POST https://pennyrail.vercel.app/api/router/execute/intel
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pennyrail-execute-intel-6e6c5956
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_en3h8PoN1dgvG6chzCD4b

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-execute-intel-6e6c5956 -d '<json body>'
```

Example prompt: Use PennyRail to execute the following task: summarize the key points from this text — 'Artificial intelligence is transforming industries by automating complex tasks, improving decision-making, and enabling new products.' Route it by intent since I don't have a specific product ID.

## When to prefer this

Choose this endpoint when you want to dynamically route a natural-language task to the appropriate PennyRail product without knowing the exact product ID upfront, or when you already have a PennyRail product ID and want to execute it directly. It is especially useful for AI agents that need to delegate micro-tasks to a settlement-backed execution layer with micropayment support via x402. Prefer this over manual product lookup when low-latency, one-shot task dispatch is needed.

## Known failure modes

- Payment failure: insufficient USDC balance or x402 payment not accepted, resulting in a 402 error
- Invalid productId: if the specified productId does not exist or is inactive, the request may fail or route incorrectly
- Ambiguous intent: if the intent field is too vague, the router may resolve an unexpected product
- Missing required fields: omitting both intent and productId may result in a routing error
- Service unavailability: Vercel hosting may experience cold-start delays or downtime
- Malformed input: non-string or oversized input values may cause validation errors

## How this service works

Machine-readable settlement service

## Output

An open-ended JSON object containing the execution output from the resolved PennyRail product. The structure varies depending on which product was dispatched; the response is machine-readable and may include text, structured data, scores, or other task-specific fields.

## 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-execute-intel-6e6c5956/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)