# Forest Commerce – Variant Resolver

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

Resolves requested product options (size, color, etc.) to a canonical public variant identifier, explicitly reporting ambiguous or missing options without modifying any cart or checkout state.

## Facts

- Endpoint: POST https://http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run/commerce/variant-resolve?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/forest-commerce-variant-resolver-285718a8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_iOtIqub0HVvcIo8ToT3eL

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-variant-resolver-285718a8 -d '<json body>'
```

Example prompt: Can you resolve which exact product variant this URL maps to when I select size Large and color Blue? https://example-store.com/products/t-shirt

## When to prefer this

Use this endpoint when you need to programmatically resolve a set of human-selected product options (size, color, etc.) to a canonical variant identifier before proceeding with price lookup, availability checking, or order automation — without touching cart or checkout state. Prefer it over full product normalization endpoints when variant resolution is the specific bottleneck, and over checkout-check endpoints when you do not yet need to validate cart reachability.

## Known failure modes

- Ambiguous options that match multiple variants are reported with details rather than resolved
- Missing required options are flagged explicitly in the response
- Product URL is unreachable or returns a non-200 status
- Provider does not expose public variant data for the given URL
- Supplied options do not match any known variant, returning an error or empty result
- URL pattern validation fails for malformed or non-HTTP(S) URLs

## How this service works

Resolve requested product options to a canonical public variant when the provider exposes them. Ambiguous or missing options are reported explicitly; no checkout or cart mutation occurs. Base mainnet USDC

## Output

Returns the canonical public variant identifier matching the supplied product URL and option values. If options are ambiguous or missing, those are reported explicitly. No cart is created or modified and no checkout flow is triggered.

## 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."
  },
  "options": {
   "type": "object",
   "description": "Public identifiers value used to scope this lookup.",
   "additionalProperties": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/forest-commerce-variant-resolver-285718a8/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)