# TLS Certificate Expiry Check (14-Day Threshold)

> TLS Certificate Expiry Check (14-Day Threshold) is a paid API for AI agents from agentshelf.syntexa.ch, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-02).

Checks whether a host's port-443 TLS certificate remains valid for at least 14 days and returns an ok_check boolean indicating pass/fail.

## Facts

- Endpoint: POST https://agentshelf.syntexa.ch/v1/tls-expiry-14?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tls-certificate-expiry-check-14-day-threshold-8fc2e983
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_WiUWQTeAXeLFiLPXk-KTg

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 tls-certificate-expiry-check-14-day-threshold-8fc2e983 -d '<json body>'
```

Example prompt: Can you check whether the TLS certificate for api.example.com is still valid for at least 14 more days — I need to know if it's about to expire before our deployment tomorrow.

## When to prefer this

Use this endpoint when an agent needs a quick, deterministic pass/fail check on whether a specific host's TLS certificate will remain valid for at least 14 days. Ideal for pre-deployment checks, automated certificate monitoring pipelines, and third-party dependency health verification where the 14-day threshold is the relevant boundary.

## Known failure modes

- Host unreachable or DNS resolution failure — endpoint cannot connect to inspect the certificate
- Invalid hostname or URL format — request rejected before network call
- Certificate already expired — ok_check returns false
- Self-signed or untrusted certificate chain — may fail validation checks
- Payment not processed — x402 payment required error blocks response

## How this service works

Call when an agent needs whether the port-443 certificate stays valid for at least 14 days. The threshold changes the ok_check bit. Exact $0.005 USDC. Prefer unpaid POST /v1/sandbox/tls-expiry-14 first.

## Output

Returns an ok_check boolean (true if the certificate is valid for at least 14 days, false otherwise), along with relevant expiry metadata for the queried host's port-443 TLS certificate.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "maxLength": 2048,
   "minLength": 8,
   "description": "Public URL whose hostname is inspected. Provide url or host. Private targets are rejected."
  },
  "host": {
   "type": "string",
   "examples": [
    "example.com"
   ],
   "maxLength": 253,
   "minLength": 1,
   "description": "Public hostname such as example.com. The port and check are fixed by the SKU. Provide host or url."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tls-certificate-expiry-check-14-day-threshold-8fc2e983/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)
