# X402 Data API – TLS Report

> X402 Data API – TLS Report is a paid API for AI agents from api.x402dataapi.com, paid per call via x402, $1/call, status unknown (last checked 2026-09-15).

Inspects a public hostname's TLS/SSL certificate and returns issuer, expiry, and error details

## Facts

- Endpoint: POST https://api.x402dataapi.com/v1/tls-report
- Price: $1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-data-api-tls-report-fc631ca1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_3XMPz3ybqmTyHXCAUoVex

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 x402-data-api-tls-report-fc631ca1 -d '<json body>'
```

Example prompt: Can you check the TLS certificate on api.example.com port 443 — I want to know if it's valid, who issued it, and how many days until it expires?

## When to prefer this

Use this endpoint when you need a pay-per-request, programmatic TLS/SSL certificate inspection for any public hostname without managing your own TLS scanning infrastructure. Ideal for AI agents monitoring certificate health, alerting on impending expiry, or validating HTTPS configuration before deploying or trusting a service.

## Known failure modes

- Host unreachable or DNS resolution failure — errors array will be populated, tls_enabled may be false
- Port not open or connection refused — errors array returned with connection details
- Invalid hostname format — 400-level error or validation failure
- TLS handshake failure — errors populated, certificate fields may be null or absent
- Expired certificate — days_remaining will be 0 or negative, errors may list expiry

## How this service works

Paid x402 API for AI agents that checks TLS certificate health, SSL report data, HTTPS certificate expiration, issuer, validity, SAN coverage, chain health, HTTPS readiness and certificate risk for a public hostname.

## Output

A JSON object with the hostname, port, TLS enabled flag, certificate issuer name, number of days remaining until expiry, and a list of any TLS errors encountered during the inspection.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "host": {
   "type": "string",
   "description": "Public hostname to inspect"
  },
  "port": {
   "type": "number",
   "description": "TLS port, usually 443"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "host": "example.com",
  "port": 443,
  "errors": [],
  "issuer": "Example CA",
  "tls_enabled": true,
  "days_remaining": 60
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-data-api-tls-report-fc631ca1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.x402dataapi.com](https://www.zero.xyz/host/api.x402dataapi.com/llms.txt)