Skill: Site status snapshot

Bundled execution of the Site status snapshot workflow - The 'is this site healthy, addressable, and crawlable - right now?' workflow. DNS resolution → HTTP reachability → security headers → TLS certificate expiry → robots policy. Five tools, one structured status payload an operator (or an uptime bot, or a pre-flight check before an extract/crawl) can act on. One x402 payment runs 5 underlying tools (dns-lookup, http-check, http-headers, tls-cert, robots-check); partial-success per step.

Input

Example output

{
  "pack": "status-snapshot",
  "args": {
    "url": "https://example.com"
  },
  "steps": [
    {
      "slug": "dns-lookup",
      "ok": true,
      "result": {}
    },
    {
      "slug": "http-check",
      "ok": true,
      "result": {}
    },
    {
      "slug": "http-headers",
      "ok": true,
      "result": {}
    },
    {
      "slug": "tls-cert",
      "ok": true,
      "result": {}
    },
    {
      "slug": "robots-check",
      "ok": true,
      "result": {}
    }
  ],
  "summary": "5/5 steps succeeded"
}

Try it - see the 402 challenge (free)

curl -i -X POST https://agent402.tools/api/skill/status-snapshot \
  -H "Content-Type: application/json" \
  -d '{"url":"https://example.com"}'

The response is HTTP 402 Payment Required with exact payment requirements. Any x402 v2 client pays automatically and retries:

Paid call (JavaScript agent)

import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/core/client";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

const client = new x402Client();
registerExactEvmScheme(client, { signer: privateKeyToAccount(KEY) });
const payFetch = wrapFetchWithPayment(fetch, client);

const res = await payFetch("https://agent402.tools/api/skill/status-snapshot", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
    "url": "https://example.com"
  }),
});

Related tools