# AgentShelf Profile Rel-Next Link Extractor

> AgentShelf Profile Rel-Next Link Extractor is a paid API for AI agents from agentshelf.syntexa.ch, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-02).

Extracts `link rel=next` href values from a public web page URL or raw HTML, with SSRF protection.

## Facts

- Endpoint: POST https://agentshelf.syntexa.ch/v1/profile-rel-next?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentshelf-profile-rel-next-link-extractor-d382e666
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hOv_FenpiEz5QXbts6lcG

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 agentshelf-profile-rel-next-link-extractor-d382e666 -d '<json body>'
```

Example prompt: Can you extract the rel=next link from this paginated page — https://example.com/results?page=1 — so I know what URL to fetch next?

## When to prefer this

Use this endpoint when you need to reliably extract `link rel=next` pagination hrefs from a live public URL or from raw HTML you already hold, and you want SSRF-safe fetching built in. Prefer the free sandbox endpoint (`POST /v1/sandbox/profile-rel-next`) for testing. Use this paid endpoint when you need production reliability or are processing content at scale via agentic workflows.

## Known failure modes

- URL is not publicly accessible or returns a non-200 status — extraction fails
- HTML exceeds 200,000 character limit — request rejected
- URL string is fewer than 8 characters or malformed — validation error
- Page has no rel=next link — returns empty/null result
- SSRF-blocked URL (private IP range, localhost, etc.) — rejected by safety filter
- Neither url nor html provided — missing required input error

## How this service works

Call when an agent needs link rel=next hrefs extracted from a public page or HTML (SSRF-safe). Exact $0.003 USDC. Prefer unpaid POST /v1/sandbox/profile-rel-next first.

## Output

Returns the href value(s) of any `link rel=next` elements found on the page or in the provided HTML. If no rel=next link is present, returns an empty or null result indicating the end of pagination. The response is SSRF-safe when using the URL input mode.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "maxLength": 2048,
   "minLength": 8,
   "description": "Public page to fetch. The selector or profile is fixed by the SKU. Provide url or html."
  },
  "html": {
   "type": "string",
   "examples": [
    "<!doctype html><html lang=\"en\"><head><title>Hello</title>\n<meta name=\"description\" content=\"Desc\"><meta property=\"og:title\" content=\"OG\">\n<link rel=\"canonical\" href=\"https://example.com/\"><link rel=\"icon\" href=\"/favicon.ico\">\n</head><body><h1>Hello</h1><a href=\"https://example.com/a\">A</a></body></html>"
   ],
   "maxLength": 200000,
   "minLength": 1,
   "description": "HTML to extract from locally. Provide html or url. When both are set, html is used."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentshelf-profile-rel-next-link-extractor-d382e666/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentshelf.syntexa.ch](https://www.zero.xyz/host/agentshelf.syntexa.ch/llms.txt)