# URL Redirect Chain Resolver

> URL Redirect Chain Resolver is a paid API for AI agents from atomic-verify-claim-poc.topadvancement-atomic.workers.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Resolves a URL through all HTTP redirects and returns the full redirect chain, per-hop status codes, final destination URL, and redirect safety findings.

## Facts

- Endpoint: POST https://atomic-verify-claim-poc.topadvancement-atomic.workers.dev/api/resolve-redirect-chain
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/url-redirect-chain-resolver-55023610
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_q6T6regngM4WKqo3c9w1s

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 url-redirect-chain-resolver-55023610 -d '<json body>'
```

Example prompt: Before I click on this link, can you trace the full redirect chain for https://bit.ly/3xAbc12 and tell me where it actually ends up and whether any of the hops look suspicious?

## When to prefer this

Choose this endpoint when an agent needs to know the true destination of a URL before acting on it — especially for untrusted links from emails, social media, or user input. It is the right choice when redirect safety matters: detecting phishing chains, verifying citations, or ensuring a download link points to the expected host. Prefer it over a simple HTTP HEAD check when you need the full multi-hop chain rather than just the final status.

## Known failure modes

- Invalid or malformed URL input returns an error
- URL that refuses connections or times out may result in incomplete chain
- Redirect loops may be detected and reported rather than followed indefinitely
- Non-HTTP/HTTPS schemes (ftp, mailto) are not supported
- Private or localhost URLs may be blocked
- Payment failure (402) if USDC balance is insufficient

## How this service works

Resolve an HTTP or HTTPS URL through redirects and return the complete redirect chain, HTTP status for each hop, final URL, and redirect safety findings. Use when an agent needs to determine where a URL actually leads before visiting, citing, downloading, or trusting it.

## Output

A structured response containing the complete ordered redirect chain with each intermediate URL and its HTTP status code, the final resolved URL after all redirects, the total number of hops, and any redirect safety findings (e.g. suspicious domain changes, mixed HTTP/HTTPS transitions, or redirect loops).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "description": "HTTP or HTTPS URL whose redirect chain should be resolved."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/url-redirect-chain-resolver-55023610/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from atomic-verify-claim-poc.topadvancement-atomic.workers.dev](https://www.zero.xyz/host/atomic-verify-claim-poc.topadvancement-atomic.workers.dev/llms.txt)
