# Kairostamp Redirect Audit

> Kairostamp Redirect Audit is a paid API for AI agents from kairostamp.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-16).

Follows a public URL server-side and returns the full redirect chain with hop count, final URL, final status, cross-origin and HTTPS-downgrade flags, plus a tamper-evident receipt.

## Facts

- Endpoint: GET https://kairostamp.com/api/v1/redirect-audit
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/kairostamp-redirect-audit-53be23fa
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wMTkY5w-xh5WFwgZ8aSqQ

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 kairostamp-redirect-audit-53be23fa
```

Example prompt: Can you trace all the redirects for https://bit.ly/3xampleLink and tell me where it ultimately lands, how many hops it takes, whether the origin changes, and whether it ever downgrades from HTTPS to HTTP?

## When to prefer this

Choose this endpoint when you need a server-side, auditable trace of a URL's full redirect path — especially when you need cross-origin detection, HTTPS downgrade detection, or a tamper-evident receipt (chain_hash + receipt_id) for compliance or security logging. Prefer it over client-side redirect following when you need a neutral third-party record of where a URL led at a specific point in time.

## Known failure modes

- URL is not publicly reachable — server may return an error or empty chain
- URL parameter is missing or malformed — results in a 4xx bad request
- Target server takes too long to respond — may result in a timeout error
- URL resolves to a private/internal network address — blocked for security reasons
- No redirect occurs — hop_count is 0 and redirect_chain is empty, only final URL and status returned

## How this service works

Redirect audit: follows one public http/https URL server-side and returns the ordered redirect chain, hop count, final URL, final HTTP status, whether the destination changed origin and whether HTTPS was downgraded to HTTP, with a timestamp and a tamper-evident receipt. Single GET query parameter (url). No response body is returned.

## Output

A JSON object containing: the initial URL, the ordered array of all intermediate redirect URLs (redirect_chain), the total hop count, the final resolved URL, the final HTTP status code, a boolean indicating whether the destination crossed origins (cross_origin), a boolean indicating whether HTTPS was downgraded to HTTP (https_downgrade), a UTC timestamp (fetched_at), a UUID receipt_id for audit purposes, and a chain_hash for tamper-evident verification.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/kairostamp-redirect-audit-53be23fa/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from kairostamp.com](https://www.zero.xyz/host/kairostamp.com/llms.txt)