# PennyRail URL Parse

> PennyRail URL Parse 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).

Parses a URL string into its structured components via a paid micropayment API endpoint

## Facts

- Endpoint: POST https://pennyrail.vercel.app/api/f/url.parse
- 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-url-parse-2fa0c255
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_C4mtjFZ3qEQcyr0gcPSTL

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-url-parse-2fa0c255 -d '<json body>'
```

Example prompt: Can you parse this URL for me and break it down into its parts — protocol, hostname, path, and query string: https://example.com:8080/search?q=hello&lang=en#results

## When to prefer this

Choose this endpoint when your agent needs a quick, reliable, machine-readable URL decomposition via a micropayment-gated API — especially in x402-compatible payment workflows where you want to pay per call in USDC rather than manage API keys or subscriptions. It is well-suited for agents that process URLs at low frequency and want cost-proportional billing.

## Known failure modes

- Malformed or non-URL string input may return an error or empty result fields
- Missing 'input' field in request body returns validation error
- Payment failure or insufficient USDC balance blocks the request via x402 payment required response
- Very long or unusual URL strings may produce partial parse results
- Non-HTTP URLs (e.g. mailto:, ftp:) may not be fully decomposed

## How this service works

Machine-readable settlement service

## Output

Returns a structured object containing the parsed components of the input URL, such as protocol, hostname, port, pathname, search/query string, and hash fragment, alongside an operation identifier string confirming what was performed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "string",
   "description": "string URL"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "operation",
  "result"
 ],
 "properties": {
  "result": {},
  "operation": {
   "type": "string"
  }
 },
 "additionalProperties": true
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/pennyrail-url-parse-2fa0c255/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)