# OpenVerbs Redirect Chain Follower

> OpenVerbs Redirect Chain Follower is a paid API for AI agents from web.openverbs.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-29).

Follows a URL's full redirect chain (301/302/303/307/308) and returns every hop with its HTTP status code and Location header, revealing the final destination of shortened or cloaked links.

## Facts

- Endpoint: POST https://web.openverbs.com/v1/redirects?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/openverbs-redirect-chain-follower-4c21c1ad
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_LYDTtVtZ5SKPp0nJnKqb6

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 openverbs-redirect-chain-follower-4c21c1ad -d '<json body>'
```

Example prompt: Can you trace where this link actually goes — follow the full redirect chain for https://bit.ly/3xAmPle and show me every hop it takes before landing on the final page?

## When to prefer this

Choose this endpoint when you need to safely inspect a URL's redirect path before following it — especially for link shorteners (bit.ly, tinyurl), affiliate/tracking links, or any cloaked URL where the true destination is hidden. It is the right choice when you need the full chain of hops rather than just the final destination, and when SSRF safety validation is required. Prefer it over a generic HTTP fetch when redirect transparency and per-hop status codes are the primary concern.

## Known failure modes

- Private or loopback IP addresses in the redirect chain trigger SSRF rejection
- Redirect chain exceeds the maximum hop cap and returns a chain-too-long error
- Non-HTTP/HTTPS URLs (e.g. ftp://) are rejected as invalid input
- The target server is unreachable or times out
- Malformed URL input fails schema validation
- Redirect loop detected (URL revisited) causes early termination

## How this service works

Follow a URL's redirect chain (301/302/303/307/308) to its final destination and return every hop with its status and Location. Unwraps link shorteners and cloaked/tracking links so an agent can see where a link really goes before following it. Each hop is SSRF-validated and the chain is capped.

## Output

An ordered list of every redirect hop, each containing the hop number, the URL at that step, the HTTP status code (e.g. 301, 302, 307), and the Location header value pointing to the next URL. The final entry shows the terminal destination URL after all redirects are exhausted. The chain is capped at a maximum number of hops, and any private/loopback/link-local addresses encountered are rejected with an SSRF error.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "format": "uri",
   "maxLength": 2048,
   "description": "Public http(s) URL to fetch. Private/loopback/link-local addresses are rejected."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/openverbs-redirect-chain-follower-4c21c1ad/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from web.openverbs.com](https://www.zero.xyz/host/web.openverbs.com/llms.txt)