# ATK TLS Batch Security Scanner

> ATK TLS Batch Security Scanner is a paid API for AI agents from atkvn.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-28).

Batch-checks up to 10 hostnames for TLS health, certificate expiry, TLS version, and post-quantum cryptography readiness

## Facts

- Endpoint: POST https://atkvn.com/agent/v1/tls-batch?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-28
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/atk-tls-batch-security-scanner-2b012587
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_EAfZUb6GSGIfx5s07Os-q

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 atk-tls-batch-security-scanner-2b012587 -d '<json body>'
```

Example prompt: Can you check the TLS health of these three domains — api.mycompany.com, www.mycompany.com, and mail.mycompany.com — and tell me if any certs are close to expiring, whether TLS 1.3 is enabled, and if they're post-quantum ready?

## When to prefer this

Use this endpoint when you need a fast, automated, external-perspective TLS audit of up to 10 hostnames in a single call — especially when post-quantum cryptography readiness is a concern. Prefer it over general SSL-checker websites when you need machine-readable output for agent workflows, certificate expiry monitoring pipelines, or batch infrastructure audits. It is particularly well-suited for organizations tracking PQ migration readiness across multiple domains.

## Known failure modes

- Invalid or unreachable hostname returns an error or omitted result
- Exceeding 10 hostnames in the array causes a validation error
- Private/internal hostnames not reachable from the scanner's network may time out
- Payment failure (x402 protocol) prevents the request from being processed
- Hostnames with misconfigured DNS may return incomplete chain data

## How this service works

Up to 10 public hostnames in one call: post-quantum TLS (X25519MLKEM768), certificate expiry, chain validity and what to fix.

## Output

Returns a JSON object with a count of checked hostnames and per-hostname results including: TLS version in use, days remaining on the certificate, whether the certificate chain is valid, whether hybrid post-quantum TLS is enabled, and a list of actionable remediation todos (or confirmation that nothing needs fixing externally).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "hostnames": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "maxItems": 10,
   "minItems": 1
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "checked": 1,
  "results": [
   {
    "todo": [
     "Nothing to fix from the outside."
    ],
    "chain_ok": true,
    "hostname": "www.example.com",
    "hybrid_pq": true,
    "tls_version": "TLS1.3",
    "cert_days_left": 64
   }
  ],
  "pq_ready": 1
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/atk-tls-batch-security-scanner-2b012587/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from atkvn.com](https://www.zero.xyz/host/atkvn.com/llms.txt)