Skip to content

Chrome Extension

The CutX Companion is a Chrome extension (Manifest V3) that adds functionality directly on whatnot.com for sellers using the CutX platform.

  1. Download the extension from the CutX dashboard
  2. Open chrome://extensions in Chrome
  3. Enable Developer mode (top right)
  4. Click Load unpacked and select the extension/ folder
  5. The CutX icon appears in your browser toolbar

While streaming on Whatnot, the extension captures sale data in real-time and syncs it to your CutX inventory:

  • Item name and sale price
  • Buyer username
  • Whatnot order ID

Sales are sent to the CutX API via:

POST /api/extension/sales
Authorization: Bearer <token>
Content-Type: application/json
{
"items": [
{
"item_name": "Pokemon Booster",
"sale_price": 45.00,
"buyer_username": "buyer123",
"order_id": "WN-123"
}
]
}

Track competitor sellers’ live stream performance:

  • Viewer count
  • Items sold and total sales
  • Top-selling items with prices

Data is stored for trend analysis:

POST /api/extension/competitor
Authorization: Bearer <token>
Content-Type: application/json
{
"seller_name": "CompetitorSeller",
"category": "trading_cards",
"viewer_count": 150,
"items_sold": 23,
"total_sales": 890.50
}

The extension popup provides quick access to:

  • Current inventory count and value
  • Upcoming shows
  • Recent sales summary
extension/
├── manifest.json # Manifest V3 config
├── background.js # Service worker (API sync)
├── content.js # Whatnot page integration
├── content.css # UI overlay styles
└── popup/
├── popup.html # Toolbar popup UI
└── popup.js # Popup logic
ComponentRole
Service workerHandles API calls to CutX, manages auth token
Content scriptInjects UI overlays on whatnot.com, captures DOM events
PopupQuick-access dashboard in the browser toolbar

The extension requests minimal permissions:

PermissionPurpose
storageStore auth token and settings
activeTabAccess the current Whatnot tab
  • https://www.whatnot.com/*
  • https://whatnot.com/*

The extension authenticates with CutX using a Bearer token stored in chrome.storage.local. Users log in through the extension popup, which calls the standard CutX auth endpoints.