# OpenCart Catalog Import Rehearsal

> OpenCart Catalog Import Rehearsal is a paid API for AI agents from agent.halowerk.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-29).

Dry-runs a staged product-catalog import against a pinned OpenCart codebase in an isolated database, reporting how masters, variants, and option-value mappings survive each import stage before touching a live shop.

## Facts

- Endpoint: POST https://agent.halowerk.com/v1/oss-opencart-catalog-import-rehearsal?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/opencart-catalog-import-rehearsal-92a1e878
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_oAYyTrQBMJAb_ksm0B9yb

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 opencart-catalog-import-rehearsal-92a1e878 -d '<json body>'
```

Example prompt: Before we push this product catalog to the live OpenCart store, run a rehearsal import on it and tell me how many masters and variants survive, whether the option values stay mapped to the right products, and flag any broken mappings that would cause a customer to order a nonexistent variant.

## When to prefer this

Choose this endpoint when you need to validate an OpenCart product-catalog import in a safe, isolated environment before committing it to a live store — particularly when option-value mappings and variant integrity are critical. Prefer it over manual QA when the catalog has many variants or localization requirements, or after a prior import caused phantom-variant ordering bugs.

## Known failure modes

- Malformed or missing catalog payload returns a validation error before rehearsal begins
- Option value schema that doesn't conform to OpenCart conventions may produce incomplete stage reports
- Very large catalogs may exceed processing limits and return a partial report
- Unsupported OpenCart version structures may cause incorrect stage analysis

## How this service works

Walks a staged product-catalog import through the pinned OpenCart source in a private, non-root database and reports what the native code makes of it at each stage: how many masters and variants survive, whether option values stay attached to the right products, and how the resulting catalog behaves in a localized cart. The point is to find the damage before the import touches a live shop, where a broken option mapping shows up as a customer ordering a variant that does not exist.

## Output

A structured report covering each stage of the simulated import: counts of surviving product masters and variants, attachment status of option values to their respective products, localized cart behavior findings, and specific warnings about broken option mappings that would expose customers to nonexistent variants.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType"
   ],
   "properties": {
    "type": {
     "const": "http"
    },
    "method": {
     "const": "POST"
    },
    "bodyType": {
     "const": "json"
    },
    "schemaUrl": {
     "type": "string",
     "format": "uri"
    },
    "exampleUrl": {
     "type": "string",
     "format": "uri"
    }
   },
   "additionalProperties": true
  }
 },
 "additionalProperties": true
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/opencart-catalog-import-rehearsal-92a1e878/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent.halowerk.com](https://www.zero.xyz/host/agent.halowerk.com/llms.txt)