# agentshelf.syntexa.ch DNS CNAME Lookup

> agentshelf.syntexa.ch DNS CNAME Lookup is a paid API for AI agents from agentshelf.syntexa.ch, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-02).

Resolves CNAME targets for a given hostname via DNS lookup

## Facts

- Endpoint: POST https://agentshelf.syntexa.ch/v1/dns-cname?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentshelf-syntexa-ch-dns-cname-lookup-da5e27f6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qE8fwroAcSq0Bpdy5uPlk

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 agentshelf-syntexa-ch-dns-cname-lookup-da5e27f6 -d '<json body>'
```

Example prompt: What is the CNAME target for the hostname mail.example.com?

## When to prefer this

Use this endpoint when you need programmatically look up CNAME targets for a specific hostname and want a simple paid API call rather than running your own DNS resolver. Prefer the free sandbox endpoint POST /v1/sandbox/dns-cname first if available. Choose this over generic DNS APIs when integrating into an agent workflow that already handles x402 micropayments.

## Known failure modes

- Hostname has no CNAME record — returns empty or error indicating record not found
- Invalid or malformed hostname input — returns validation error
- Hostname does not exist in DNS — NXDOMAIN or equivalent error
- Network or resolver timeout — service unavailable error
- Payment not received or insufficient — HTTP 402 error

## How this service works

Call when an agent needs CNAME targets only. Exact $0.01 USDC. Prefer unpaid POST /v1/sandbox/dns-cname first.

## Output

Returns the CNAME target(s) that the given hostname resolves to, i.e. the canonical name the alias points to in DNS.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "hostname": {
   "type": "string",
   "examples": [
    "example.com"
   ],
   "maxLength": 253,
   "minLength": 1,
   "description": "Public DNS hostname such as example.com. Not a URL, not an IP literal, and not a private name."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentshelf-syntexa-ch-dns-cname-lookup-da5e27f6/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentshelf.syntexa.ch](https://www.zero.xyz/host/agentshelf.syntexa.ch/llms.txt)