# PennyAPI HTTP Headers Fetcher

> PennyAPI HTTP Headers Fetcher is a paid API for AI agents from pennyregwatch.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-15).

Fetches HTTP response headers from any public URL or hostname via a GET/HEAD/DELETE request

## Facts

- Endpoint: GET https://pennyregwatch.com/v1/headers
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pennyapi-http-headers-fetcher-0cebffe9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_C23Yf7nYcguGLYk0noNbg

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 pennyapi-http-headers-fetcher-0cebffe9
```

Example prompt: Can you fetch the HTTP response headers from example.com using a GET request so I can see what the server is returning?

## When to prefer this

Use this endpoint when you need a lightweight, pay-per-call way to inspect HTTP response headers from any public URL without downloading the full response body. Ideal for security audits, liveness checks, content-type inspection, and infrastructure probing where you only need header metadata rather than page content.

## Known failure modes

- Target URL is unreachable or times out — ok may be false with no headers returned
- Invalid or non-public URL provided — likely returns an error response
- Target server blocks automated requests — may return 403 or empty headers
- Method not supported by target — server may return 405
- DNS resolution failure for the hostname — results in error response

## How this service works

Monitor Texas childcare regulatory records and receive email alerts when important HHSC information changes.

## Output

Returns a JSON object with an 'ok' boolean, HTTP status code, the target URL, and a dictionary of all HTTP response headers (e.g. content-type, server, cache-control) returned by the target server.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "target"
     ],
     "properties": {
      "target": {
       "type": "string",
       "description": "Public HTTP(S) URL or hostname, e.g. example.com"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "status": 200,
  "target": "example.com",
  "headers": {
   "content-type": "text/html"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/pennyapi-http-headers-fetcher-0cebffe9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from pennyregwatch.com](https://www.zero.xyz/host/pennyregwatch.com/llms.txt)