# DNS SRV Record Lookup for Jabber (_jabber._tcp)

> DNS SRV Record Lookup for Jabber (_jabber._tcp) is a paid API for AI agents from agentshelf.syntexa.ch, paid per call via x402, $0.004/call, status unknown (last checked 2026-10-19).

Resolves SRV records at _jabber._tcp.{hostname} for a given registrable domain, returning Jabber/XMPP service discovery data.

## Facts

- Endpoint: POST https://agentshelf.syntexa.ch/v1/dns-srv-jabber?utm_source=zero.xyz
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/dns-srv-record-lookup-for-jabber-jabber-tcp-6cc51fa4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vovuAO8Tgfg248Xzi6PZs

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 dns-srv-record-lookup-for-jabber-jabber-tcp-6cc51fa4 -d '<json body>'
```

Example prompt: What are the Jabber SRV records for example.com? I need the _jabber._tcp DNS SRV entries to figure out which server and port handle XMPP connections for that domain.

## When to prefer this

Use this endpoint when you need to programmatically discover the Jabber/XMPP service endpoint (host, port, priority, weight) for a given domain via DNS SRV lookup at _jabber._tcp. Prefer the unpaid sandbox variant (POST /v1/sandbox/dns-srv-jabber) for testing. Choose this over generic DNS lookup tools when you specifically need structured SRV record resolution scoped to the Jabber service type.

## Known failure modes

- Domain does not have _jabber._tcp SRV records configured — empty or not-found response
- Invalid or malformed hostname input — validation error
- DNS resolution timeout or upstream DNS failure — network error
- Hostname exceeds 253 character limit — input validation failure
- Payment not included or insufficient — HTTP 402 response

## How this service works

Call when an agent needs SRV records at _jabber._tcp.{hostname} for Jabber. The caller sends the registrable domain, not the underscored name. Exact $0.004 USDC. Prefer unpaid POST /v1/sandbox/dns-srv-jabber first.

## Output

Returns the SRV record data found at _jabber._tcp.{hostname}, including priority, weight, port, and target hostname for the Jabber/XMPP service. If no SRV records are found or the domain does not exist, an error or empty result is returned.

## 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/dns-srv-record-lookup-for-jabber-jabber-tcp-6cc51fa4/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)