# Forest Commerce – Canonical Product URL Resolver

> Forest Commerce – Canonical Product URL Resolver is a paid API for AI agents from http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-02).

Resolves a public product URL to its redirect chain, canonical URL, and stable provider identifiers using bounded HTTP and structured data extraction (no JavaScript execution).

## Facts

- Endpoint: POST https://http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run/commerce/canonical-product?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/forest-commerce-canonical-product-url-resolver-86debb12
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_w_Rv7wTcvFq48deY9_ZlR

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 forest-commerce-canonical-product-url-resolver-86debb12 -d '<json body>'
```

Example prompt: Can you resolve this product URL to its canonical form and get me the stable provider identifiers — I want the real, final URL without any redirects or affiliate wrappers: https://amzn.to/3xyz123

## When to prefer this

Choose this endpoint when you need the final canonical URL and stable provider identifiers for a product URL that may be behind redirects, affiliate wrappers, or short links — and when you do not need JavaScript rendering. Prefer this over general scraping endpoints when the specific goal is URL canonicalization and identifier extraction for product deduplication, tracking, or reference normalization.

## Known failure modes

- URL is not publicly accessible or requires authentication (returns error or empty result)
- Product page uses JavaScript rendering to expose canonical URL (not supported, returns static-only result)
- URL does not resolve to a product page (result may lack provider identifiers)
- Redirect chain exceeds bounded HTTP fetch limits (resolution may be incomplete)
- Provider identifiers not available in static HTML (fields returned as missing/null)

## How this service works

Resolve a public product redirect, canonical URL and stable provider identifiers using bounded HTTP and structured data. It does not execute JavaScript or assert unavailable facts. Base mainnet USDC

## Output

Returns the canonical URL of the product after following redirects, along with stable provider identifiers extracted from the resolved page using bounded HTTP requests and structured data — without executing JavaScript or asserting facts not available in the static response.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "pattern": "^https?://",
   "maxLength": 2048,
   "description": "Public HTTP(S) URL to inspect, resolve, or compare."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/forest-commerce-canonical-product-url-resolver-86debb12/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run](https://www.zero.xyz/host/http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run/llms.txt)