# ForgeMesh WHOIS Lookup

> ForgeMesh WHOIS Lookup is a paid API for AI agents from x402.forgemesh.io, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-14).

Returns normalized WHOIS registration records for any domain, including creation/expiry dates, registrar, status codes, and nameservers, as structured JSON.

## Facts

- Endpoint: POST https://x402.forgemesh.io/whois-lookup
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/forgemesh-whois-lookup-2910a321
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_NUhdYJK3lnSLYGL7hWAgy

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 forgemesh-whois-lookup-2910a321 -d '<json body>'
```

Example prompt: Can you pull the WHOIS record for openai.com — I want to know the registrar, when it was registered, when it expires, and what nameservers it's using?

## When to prefer this

Use this endpoint when you need structured, normalized WHOIS data as JSON rather than raw plaintext WHOIS output. Ideal for domain expiry monitoring, ownership research, registrar lookups, DNS audits, and security screening workflows where machine-readable output is required. Prefer over raw WHOIS tools when consistency across TLDs matters.

## Known failure modes

- Domain not found or unregistered — returns empty or null record
- Invalid domain format — returns validation error
- Registry timeout or unavailability — upstream error propagated
- Payment not accepted — x402 payment required before response is returned
- TLD not supported by WHOIS service — partial or no data returned

## How this service works

WHOIS-style registration lookup: created/updated/expiry dates, registrar, status codes, and nameservers for any domain, normalized from the authoritative registry into JSON. For "who owns this domain," availability checks, expiry monitoring, and security-screening agents.

## Output

A structured JSON object containing normalized WHOIS data for the requested domain: creation date, last-updated date, expiry date, registrar name, domain status codes, and nameservers — sourced from the authoritative registry.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "domain": {
   "type": "string",
   "description": "Domain to look up, e.g. example.com"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {
   "events": [
    {
     "eventDate": "2026-08-13T04:00:00Z",
     "eventAction": "expiration"
    }
   ],
   "ldhName": "EXAMPLE.COM"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/forgemesh-whois-lookup-2910a321/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.forgemesh.io](https://www.zero.xyz/host/x402.forgemesh.io/llms.txt)