# HTTP Redirect Chain Tracer

> HTTP Redirect Chain Tracer is a paid API for AI agents from api.strale.io, paid per call via x402, $0.054001/call, status unknown (last checked 2026-10-12).

Traces the full HTTP redirect chain for a given URL, returning each hop's status code, Location header, server, and latency.

## Facts

- Endpoint: GET https://api.strale.io/x402/redirect-trace?utm_source=zero.xyz
- Price: $0.054001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-strale-io-f3626185
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Bn-hmOVDWhTE9YJA6ZNuO

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 api-strale-io-f3626185
```

Example prompt: Trace the full redirect chain for https://bit.ly/3xYzAbc using a GET request so I can see every hop, its status code, server, and how long each step takes.

## When to prefer this

Use this endpoint when you need to inspect the full HTTP redirect path of a URL, debug redirect chains, identify tracking or intermediary hops, verify where a shortened or obfuscated URL ultimately resolves, or audit redirect latency across each hop.

## Known failure modes

- URL is unreachable or DNS resolution fails — network error returned
- Redirect loop detected — may return error or truncated chain at max_redirects limit
- Invalid or malformed URL input — validation error
- Max redirects exceeded — partial chain returned up to limit
- Target server times out — timeout error with partial results

## How this service works

Trace the full HTTP redirect chain for a URL. Shows each hop with status code, location header, server, and latency.

## Output

An ordered list of redirect hops, each containing the HTTP status code, Location header value, server identifier, and latency in milliseconds, ending at the final resolved URL.

## Example request

```json
{
 "url": "https://example.com"
}
```

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "url"
 ],
 "properties": {
  "url": {
   "type": "string"
  },
  "max_redirects": {
   "type": "integer"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "chain": {
  "type": "array"
 },
 "issues": {
  "type": "array"
 },
 "final_url": {
  "type": "string"
 },
 "original_url": {
  "type": "string"
 },
 "redirect_count": {
  "type": "integer"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/api-strale-io-f3626185/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.strale.io](https://www.zero.xyz/host/api.strale.io/llms.txt)