CSBoard price alerts: find underpriced skins scored against CSFloat

The value of a market to a sniping tool is not its inventory size — it is which fields it publishes per listing, because a rule can only fire on a number the marketplace actually states. CSBoard publishes an unusually complete set: float value, paint seed, Doppler phase, fade percentage, blue percentage, and an inspect link on every listing.

That set makes CSBoard the strongest pattern-hunting surface outside CSFloat itself, and it is the only market in CSWatcher's roster that publishes fade % and blue % per listing.

Here is what that translates to in practice, rule type by rule type.

• Float rules fire natively. A "Factory New under 0.02" or "Field-Tested between 0.15 and 0.18" condition is evaluated against CSBoard's own published float. No estimation, no inference from wear name.
• Paint seed rules fire natively. Seed is published per listing, so a whitelist of specific seeds — the blue-gem patterns, the Fire Serpent placements, whatever list you keep — filters correctly at scan time rather than after you have already clicked through.
• Doppler phase rules fire natively. Phase 2, Ruby, Sapphire and Black Pearl are distinguished by CSBoard's own phase field, which is the difference between a usable Doppler alert and a stream of undifferentiated Gamma noise.
• Fade percentage rules fire on the marketplace's published number. This is the distinctive one. A rule like "Karambit Fade above 95%" runs against the figure CSBoard states for that exact listing. Elsewhere in the roster, fade is either absent or something you would have to derive yourself from the seed.
• Blue percentage rules fire the same way. "Case Hardened, blue side above 60%" is a rule that normally cannot exist on a marketplace scan at all, because almost no market publishes a blue figure. On CSBoard it is a first-class condition evaluated on the published value.
• Sticker, nametag and StatTrak conditions are weaker here. Where a field is not published in the listing data, CSWatcher will not guess at it. It does not silently substitute an estimate to make a rule look like it worked. If a condition cannot be evaluated from what the market states, that listing is simply not matched.

The inspect link matters for a different reason: it is your verification step. CSWatcher's alert tells you what CSBoard published; the inspect link lets you confirm the item in-game before committing money. CSWatcher never buys here on its own — so that verification step stays available to you — there is no automated path that skips it.

One consequence worth internalising: a CSBoard price check is only as good as CSBoard's own field accuracy. CSWatcher reads and reports; it does not audit the marketplace's numbers. If a published fade % is wrong, the alert built on it will be wrong in the same direction.

There is nothing for you to tune here, and that is deliberate. CSWatcher ships one behaviour for this lane and does not expose a "go faster" toggle, because such a toggle only ever does one thing in practice: it lets an impatient user trade the market's tolerance for a few seconds of apparent throughput, and then the lane stops working for everybody. A read-only lane that gets throttled or blocked is worth nothing, and a market you can still read next year beats a market you squeezed today. CSWatcher behaves like a guest on CSBoard because staying welcome is the feature.

What you do control is what you point at it, and on this market that choice matters more than usual. CSBoard's distinguishing fields — fade %, blue %, phase, seed — are precisely the ones that reward a narrow rule and punish a broad one. "Any Case Hardened under $400" will fill your feed with items you do not want. "Case Hardened, blue side above 60%, under $400" will stay quiet for days and then hand you the listing you actually came for. The whole value of this lane is that the second rule is possible here and is not possible on most of the roster, so write the second one.

Link precision on CSBoard is narrowed. When CSWatcher opens a listing for you it does not dump you on a generic search page for the skin — it constructs a link filtered to a tight float band around the exact listing that triggered the alert. On a popular item where hundreds of copies are on sale, that is the difference between arriving at the item and hunting for it while the price advantage evaporates. CSWatcher deliberately does not document how those links are assembled, and its own signed-in API redacts that construction. The sentences ship; the recipe does not.

CSBoard works with zero setup. No API key, no login, no account linking — enable the market and the lane starts reading. That is unusual and it is worth stating plainly, because most market integrations in this space demand credentials before they show you anything.

Adding a free read-only API key upgrades the lane to CSBoard's official feed. The rules and fields are the same; what you gain is that listings arrive timestamped. That single addition changes what "new" means, which is covered below.

Surface support: this lane is read through the free CSWatcher Bridge extension, so the request leaves from your own browser rather than from one address shared by every customer — the same posture CSWatcher takes on every market it can. Nothing about the rule set changes because of that: the fade % and blue % conditions that make CSBoard worth watching behave exactly as they do anywhere else, and your rules are written once and run wherever the engine runs.

CSWatcher uses one yardstick across the entire roster. Every listing on every market — CSBoard included — is scored against CSFloat's Final price for that item. A deal percentage therefore means the same thing regardless of where the listing lives, so a 14% figure on CSBoard and a 14% figure elsewhere are directly comparable and sortable in one list. You are never mentally converting between per-market baselines.

Where the gaps sit, how liquidity and fees change the picture market by market, and how CSFloat's own listings compare, are covered properly on the dedicated CSFloat comparison page. Read that one if pricing mechanics are what you came for.

Two limitations, stated straight.

The keyless lane carries no listing timestamp. Without an API key, CSBoard's data does not tell CSWatcher when a listing appeared. CSWatcher therefore recognises a new listing by its identifier — the first time an id is seen, it is treated as new. In practice this works, but the distinction is real: "not seen before by this scan" is not identical to "just posted". After a restart, or on the first scan of a newly enabled item, the tool has no history to compare against and behaves accordingly. If listing age matters to your strategy, add the free read-only key and use the official feed, which timestamps listings.

Desktop only. There is no browser-app path to CSBoard today. If you use CSWatcher through the browser, this market is not available to you regardless of plan.

Beyond those: CSWatcher's alerts are the beginning of your decision, not the end of it. The tool tells you a listing is priced below CSFloat's Final by some margin. It does not tell you the item will sell, what it will sell for, or when. CSWatcher makes no claims about returns and does not model them.

CSBoard scans and alerts on Spectator, the free plan, like every marketplace CSWatcher reads — you get the listing link and buy it yourself. What a Sniper pass adds is the buying: hands-off Auto-Buy on the seven marketplaces that support it, Turbo pace and unlimited armed filters. Run the roster for free first and decide whether a pass is worth $7 for a week.

Markets ship switched off. A fresh install makes zero requests to CSBoard, or to any other market, until you explicitly enable it. There is no default-on lane, no background scanning you did not ask for, and no "we enabled some sensible defaults for you". You turn CSBoard on, and only then does the lane start reading. Turning it off stops it entirely.

Every non-CSFloat market in CSWatcher, CSBoard included, is alert-only. CSWatcher scans, scores and links. The purchase is yours to make, on CSBoard, in your own session.

CSWatcher is not affiliated with or endorsed by CSBoard. CSWatcher reads CSBoard's publicly published listing data as a client and has no commercial, technical or contractual relationship with the marketplace. Marketplace names are used descriptively to identify the services CSWatcher reads.