Validate product variants API

Group products by the supplied parent sku and flag repeated color and size pairs, price disagreements, and parents that are not in the request. Missing options are not invented.

The Validate product variants operation is part of the E-commerce Catalog Intelligence API on BRAINIAC.software. Group products by the supplied parent sku and flag repeated color and size pairs, price disagreements, and parents that are not in the request. Missing options are not invented. It is exposed as POST /api/v1/ecommerce-catalog/product-variant-validate and priced at $0.04 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: Product records, CSV, and JSON supplied in the request. Limitations: No sales channel is contacted and no product is published. Specifications, dimensions, materials, and certifications are not invented. A category is marked inferred only when one caller-supplied keyword matches the title. Feed checks cover brainiac-catalog-v1 and a documented Google Merchant subset. They are not a channel approval. Image files are not downloaded. Only supplied URLs and metadata are checked. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include Normalize product records, Extract product attributes, Check product description quality, Classify product categories. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.04 USDC
/api/v1/ecommerce-catalog/product-variant-validate

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/ecommerce-catalog/product-variant-validate" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "products": [
    {
      "sku": "mug-blue",
      "parentSku": "mug",
      "title": "Blue Mug",
      "color": "Blue",
      "size": "M",
      "price": 12,
      "currency": "USD"
    },
    {
      "sku": "mug-blue-2",
      "parentSku": "mug",
      "title": "Blue Mug",
      "color": "Blue",
      "size": "M",
      "price": 14,
      "currency": "EUR"
    },
    {
      "sku": "orphan",
      "parentSku": "missing-parent",
      "title": "Red Mug",
      "color": "Red",
      "size": "S",
      "price": 10,
      "currency": "USD"
    }
  ]
}
JSON

An unpaid probe returns HTTP 402 with x402 payment requirements. After paying the exact USDC amount on Base, retry the identical request with a payment-signature header.

FAQ

  • Do I need an API key? No. Pay the listed USDC amount with x402.
  • What network? Base (eip155:8453), USDC.
  • Is this an official determination? No. Results are for human review against the cited sources.

Related APIs

E-commerce Catalog Intelligence APIFull docsHow it works