Compare two listing records API

Compare supplied titles, brands, sellers, prices, and decoded images field by field. Different currencies are not converted, and a difference is not a finding that either listing is counterfeit.

The Compare two listing records operation is part of the Brand Protection API on BRAINIAC.software. Compare supplied titles, brands, sellers, prices, and decoded images field by field. Different currencies are not converted, and a difference is not a finding that either listing is counterfeit. It is exposed as POST /api/v1/brand-protection/marketplace-listing-compare and priced at $0.05 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: Listings and images supplied in the request. One public page when the caller provides its URL. Limitations: Records come from the request or from one public page named in the request. Login pages and CAPTCHAs are not bypassed. A visual match is not proof of counterfeiting. A brand name in a listing is not a trademark determination. No seller account is accessed and no listing is removed. 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 Match a listing to a supplied brand, Detect listing signals against a reference, Compare product images, Extract seller evidence. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.05 USDC
/api/v1/brand-protection/marketplace-listing-compare

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/brand-protection/marketplace-listing-compare" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "listings": [
    {
      "id": "L-1",
      "title": "Example kettle",
      "brand": "Example",
      "seller": "Shop A",
      "price": 80,
      "currency": "USD",
      "sku": "SKU-1"
    },
    {
      "id": "L-2",
      "title": "Example kettle",
      "brand": "Other",
      "seller": "Shop B",
      "price": 20,
      "currency": "USD",
      "sku": "SKU-9"
    }
  ]
}
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

Brand Protection APIFull docsHow it works