# PennyRail DNS A Record Lookup

> PennyRail DNS A Record Lookup is a paid API for AI agents from pennyrail.vercel.app, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-15).

Resolves a hostname to its DNS A record (IPv4 address) via a paid API endpoint

## Facts

- Endpoint: POST https://pennyrail.vercel.app/api/p/network/dns.a--dns-lookup
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pennyrail-dns-a-record-lookup-0ac3d184
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Rc14-A92M8Q90tfT8HA--

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-dns-a-record-lookup-0ac3d184 -d '<json body>'
```

Example prompt: Look up the DNS A record for api.example.com and tell me what IPv4 address it resolves to.

## When to prefer this

Use this endpoint when you need a quick, programmatic DNS A record lookup within an agent workflow that already handles x402 micropayments. It is well-suited for lightweight infrastructure checks, pre-deployment validations, or enriching data pipelines with IP resolution, especially when you want a pay-per-call model rather than managing a DNS SDK or credentials.

## Known failure modes

- Invalid or malformed hostname input returns an error
- Non-existent domain (NXDOMAIN) results in resolution failure
- Network timeout if DNS upstream is unreachable
- Missing required 'input' field returns a validation error
- Payment failure (insufficient USDC) blocks the request via x402 protocol

## How this service works

Machine-readable settlement service

## Output

A JSON object containing the DNS A record resolution result for the provided hostname, including the resolved IPv4 address(es). The response schema is open-ended (additionalProperties: true), so additional DNS metadata may be included.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "additionalProperties": true
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/pennyrail-dns-a-record-lookup-0ac3d184/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)