Rust Steam Market automation

Rust is the first SteamMarketRunner acquisition focus: high-volume commodity skins, frequent repricing, and broad item sets make it a natural fit for scheduled Steam Community Market automation.

SteamMarketRunner supports Rust and CS2 as first-class Steam games. The same runner, pricing algorithms, exposure controls, audit log, and safety limits apply across games; Rust is the recommended starting point for the MVP because item metadata is simpler than CS2 sticker/float workflows.

Use conservative Rust settings

SteamMarketRunner is an independent automation tool for your own Steam accounts. Automation is not officially endorsed by Valve and can carry account, market, and financial risk. Start with small item scopes, low exposure, BUY and SELL disabled, and manual review of candidate data, statuses, and audit output before scaling live buy or sell actions.

Where Rust fits in the product

Workflow	Why it matters for Rust	SteamMarketRunner support
Broad item tracking	Rust traders often manage many commodity skins and containers	Catalog sync, item groups, per-group strategy overrides
Buy orders	Small pricing errors can repeat across many items	Exposure caps, balance fail-closed behavior, liquidity and trend guards
Sell listings	Inventory can accumulate across accounts	Scheduled listing jobs, confirmation handling, and old-listing removal
Repricing	Commodity listings can drift from the active market	Reprice tolerance, competitor removal, and stale order cancellation
Multi-account operations	Operators may split inventory and wallet capacity	Per-account runner state, proxies, audit log, alerts, and dashboard views

For the cross-game overview, read Steam Market automation overview. For game-specific CS2 metadata concerns, see CS2 Steam Market automation.

Recommended Rust rollout

1. Connect one Steam account and wait for account health, wallet, inventory, and market state sync.
2. Import or add Rust catalog items, then keep BUY and SELL disabled while reviewing candidate data.
3. Create a small Rust item group with conservative trading settings: low exposure, modest order sizing, and cautious repricing.
4. Review skip reasons, item statuses, and audit output in the dashboard while BUY and SELL remain disabled.
5. Enable SELL or BUY for a limited Rust group before expanding to more items or accounts.

Small scopes are especially important when bulk Rust item lists share the same strategy. A single bad setting can otherwise repeat across many buy orders or listings.

Rust buy-order guardrails

Rust buy automation should be treated as exposure management, not as a promise of returns. Use the same controls described in buy order automation and exposure guards:

• maxOrderExposure to cap total open buy-order exposure for the account;
• liquidity and sales-count gates to avoid thin or stale markets;
• order-book depth checks for configured order position;
• balance checks that fail closed when wallet state is unknown;
• per-account job throttling when you intentionally scale candidate count.

The runner uses current wallet and order state from Steam sync jobs. If wallet data is missing, buy planning treats available balance as zero instead of assuming unlimited funds.

Rust sell and repricing workflow

Rust sell-side automation is usually simpler than CS2 because there are no sticker or float guards. The main risks are stale prices, held inventory, aggressive repricing, and too many actions on one account.

Use these docs together:

• Steam market repricing and listing automation for listing and maintenance behavior;
• Inventory holds troubleshooting for marketable versus held inventory;
• Steam Market pricing algorithms explained for MS, HG, HSG, AVG, LG, BG, and OG pricing;
• Steam Market automation safety and risk for account-risk and legal framing.

Rust is supported, not the only focus

SteamMarketRunner is a multi-game Steam Market runner. Rust is the current MVP positioning and landing-page focus, while CS2 remains a supported game with extra metadata-sensitive safeguards.

If you operate both games, keep separate item groups and review strategy overrides independently. Rust commodity settings should not be copied blindly to CS2 skins with stickers, souvenir status, or float-sensitive prices.

Next step

Configure a small Rust group from Trading settings, then review How trading works before enabling live runner actions.