# Toll402 URL Status Checker

> Toll402 URL Status Checker is a paid API for AI agents from toll402.dev, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Returns HTTP status code, final content-type, and response size for any public URL using HEAD then GET fallback

## Facts

- Endpoint: POST https://toll402.dev/v1/t/url_status
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/toll402-url-status-checker-a2bd7867
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0wji2xUQduI5hMoTjeZ9l

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 toll402-url-status-checker-a2bd7867 -d '<json body>'
```

Example prompt: Can you check if https://example.com/report.pdf is reachable and tell me its content-type and file size?

## When to prefer this

Use this endpoint when you need a lightweight, low-cost probe of a URL's availability and metadata without fetching full content. Ideal for link validation, pre-download checks, API health spot-checks, or determining content-type before deciding how to process a resource. Prefer this over a full page-fetch endpoint when you only need status and headers, not content.

## Known failure modes

- URL is unreachable or DNS fails — returns a network error or timeout
- URL requires authentication — returns 401 or 403 status
- URL is malformed or missing scheme — schema validation error on input
- HEAD and GET both fail — may return an error indicating no response received
- Very slow servers may cause timeouts before a response is available

## How this service works

HTTP status, final content-type and response size for a URL (HEAD then GET fallback)

## Output

Returns the HTTP status code (e.g. 200, 301, 404), the final content-type header (e.g. text/html, application/pdf), and the response size in bytes for the given URL, after attempting HEAD first and falling back to GET if needed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object",
     "required": [
      "url"
     ],
     "properties": {
      "url": {
       "type": "string"
      }
     }
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/toll402-url-status-checker-a2bd7867/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from toll402.dev](https://www.zero.xyz/host/toll402.dev/llms.txt)