# Boring API – Product Schema Normalize

> Boring API – Product Schema Normalize is a paid API for AI agents from api.relaex-engineers.de, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-10).

Normalizes a product data file (Shopify CSV, Google Merchant feed, WooCommerce CSV, or JSON schema) into a canonical structured format with confidence scoring

## Facts

- Endpoint: POST https://api.relaex-engineers.de/v1/schema/normalize?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/boring-api-product-schema-normalize-46718b4c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_LNZQPc9Nf4-dH4nusj05D

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 boring-api-product-schema-normalize-46718b4c -d '<json body>'
```

Example prompt: I just exported my products from Shopify as a CSV — can you normalize it against the shopify_products_csv schema? Here's the public file URL: https://mystore.com/exports/products.csv

## When to prefer this

Choose this endpoint when you need deterministic, rule-based normalization of e-commerce product data across known formats (Shopify, Google Merchant, WooCommerce, JSON schema). Ideal for catalog migration pipelines, feed unification, and cross-platform product data standardization where reproducibility and confidence scoring matter more than AI-generated mappings.

## Known failure modes

- File URL is not publicly accessible — returns an error or failed status
- Unsupported or mismatched target schema for the input file format — low confidence or error result
- Malformed file content that cannot be parsed — returns failed status
- Invalid options JSON string — options are ignored or cause a validation error
- Network timeout fetching the remote file URL

## How this service works

Deterministic analysis APIs and MCP tools: supplier
price list comparison, PDF table extraction, product feed validation, product data mapping.

## Output

A JSON object containing a 'result' field with the normalized product data, a 'status' field indicating success or failure, and a 'confidence' object with a level (e.g. 'high') indicating how reliably the normalization was performed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "target": {
   "type": "string",
   "description": "shopify_products_csv, google_merchant, woocommerce_products_csv or json_schema"
  },
  "options": {
   "type": "string",
   "description": "Optional options as a JSON string; schema under /v1/schemas/"
  },
  "file_url": {
   "type": "string",
   "description": "Public URL of the input file"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {},
  "status": "success",
  "confidence": {
   "level": "high"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/boring-api-product-schema-normalize-46718b4c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.relaex-engineers.de](https://www.zero.xyz/host/api.relaex-engineers.de/llms.txt)