Date: 2026-03-07 Scope: create a strong public OSS starting point for a Node.js / TypeScript SDK around the CSFloat API, with honest room for future CS2 market adapters.
This repository should start as:
- an unofficial Node.js / TypeScript SDK for the CSFloat API
- a public OSS project that is actually useful on its own
- a clean foundation for future automation tools and adapters
This repository should not start as:
- a vague “all CS2 markets” wrapper without real implementation
- a thin copy of another unofficial wrapper
- a giant product surface with unclear ownership
Deliver a public repository that can credibly say:
- here is a well-designed CSFloat Node.js SDK
- here are the tested API workflows it supports
- here is the roadmap toward a broader market-adapter architecture
Current implementation scope:
- CSFloat API only
- Node.js / TypeScript only
- explicit support for authenticated account flows
- focus on listings, stall, inventory, account profile, and listing mutation
Current non-goals:
- browser automation
- pricing engine logic
- Telegram bot workflows
- multi-market support in v0
Future direction can expand toward a broader CS2 market tooling ecosystem, but only in stages.
Recommended wording:
- current:
CSFloat-first SDK - next:
market-adapter-ready architecture - future:
additional CS2 market adapters
That keeps the repository honest while still showing active growth potential.
The first strong public version should include:
- typed API client
- auth handling via API key
- methods for:
getMegetInventorygetStallgetListingsgetListingByIdcreateListingupdateListingdeleteListing
- pagination helpers
- normalized error model
- usage examples
- endpoint support matrix in docs
- basic smoke-test guidance
Suggested high-level modules:
src/client/- low-level HTTP client
- auth injection
- retry / timeout handling
src/resources/accountinventorystalllistingshistory
src/types/- API response types
- shared entities
src/errors/- typed errors
src/utils/- query helpers
- pagination helpers
examples/- real usage scripts
The public repository should include:
README.md- quick start
- install instructions
- auth usage
- endpoint examples
- supported / partially-supported endpoint table
- roadmap section
- contribution guidelines later
Before public release, the repo should have:
- clean naming
- consistent TypeScript types
- no hardcoded secrets
- simple examples that actually run
- smoke-tested mutation examples clearly labeled
- clear disclaimer that this is unofficial
If the repository later grows beyond CSFloat, it should do so by adapters, not by scope drift.
Good future shape:
- keep
csfloat-node-sdkstrong as the first adapter - later introduce adapter interfaces or sibling packages
- only claim broad market coverage after real implementations exist
Possible future branches:
market-adaptersabstraction layer- normalized listing model across providers
- additional CS2 market connectors
- comparison / research utilities
The best next execution step after this planning repo exists:
- initialize the actual package skeleton
- choose
TypeScript + tsupor equivalent minimal build tooling - implement authenticated client bootstrap
- implement
getMe,getInventory,getStall, andgetListings - document real tested behavior as the source of truth