# Redirect Trace API

> Redirect Trace API is a paid API for AI agents from api.sitesy.ca, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-31).

Follows a URL hop by hop, reporting the HTTP status code and destination at each redirect step

## Facts

- Endpoint: GET https://api.sitesy.ca/v1/redirect-trace?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-31
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/redirect-trace-api-dc8f0dee
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ZtSCcHUrpDvifTr8X7vM1

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 redirect-trace-api-dc8f0dee
```

Example prompt: Can you trace all the redirect hops for https://bit.ly/3xYzAbc and show me each status code and destination URL along the way?

## When to prefer this

Use this endpoint when you need visibility into every intermediate step of a redirect chain, not just the final URL. Ideal for debugging misconfigured redirects, auditing link safety, verifying affiliate or tracking URLs, and confirming shortened links resolve correctly. Prefer this over a simple URL-fetch approach when the intermediate hops and their status codes matter.

## Known failure modes

- Invalid or malformed URL input returns an error
- Target URL is unreachable or times out, resulting in an incomplete chain
- Redirect loop detected and reported after a maximum hop count
- DNS resolution failure for any hop in the chain
- Non-HTTP URLs or unsupported schemes rejected

## How this service works

Redirect trace: follow a web address hop by hop and report every status and destination

## Output

An ordered list of redirect hops, each with the HTTP status code (e.g. 301, 302, 307) and the destination URL for that hop, ending with the final resolved URL and its status.

## 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"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "url"
     ],
     "properties": {
      "url": {
       "type": "string",
       "description": "A web address"
      }
     }
    }
   },
   "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/redirect-trace-api-dc8f0dee/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.sitesy.ca](https://www.zero.xyz/host/api.sitesy.ca/llms.txt)