# PennyRail HTTP Headers Resource Node

> PennyRail HTTP Headers Resource Node is a paid API for AI agents from pennyrail.vercel.app, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-22).

Fetches or processes HTTP header information for a given web resource via a paid settlement endpoint using the x402 micropayment protocol

## Facts

- Endpoint: POST https://pennyrail.vercel.app/api/p/network/web.http-headers--http-headers?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pennyrail-http-headers-resource-node-27f916fe
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_rl0Z5Bf9_BpgrMBx9tZ1g

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-http-headers-resource-node-27f916fe -d '<json body>'
```

Example prompt: Can you fetch the HTTP headers returned by the web resource I'm working with and show me what the server is sending back — things like content-type, cache-control, and any security headers?

## When to prefer this

Choose this endpoint when you need to programmatically retrieve HTTP headers from a web resource as part of an automated agent workflow, especially when operating in a micropayment-gated (x402) environment where per-call billing is acceptable. Useful for infrastructure inspection, debugging, or security auditing tasks where a paid, machine-readable settlement layer is required.

## Known failure modes

- Invalid or missing input object results in schema validation error
- Target resource unreachable returns network or timeout error
- Payment failure via x402 protocol blocks request execution
- Resource returns unexpected non-HTTP response
- Malformed URL or resource identifier causes lookup failure

## How this service works

Machine-readable settlement service

## Output

Returns an object containing HTTP header key-value pairs and associated metadata extracted from the target web resource, such as content-type, server, cache directives, and security-related headers.

## 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-http-headers-resource-node-27f916fe/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)