GET /api/v1/demand-intent/games/{id}/conditions: that endpoint reports per-condition demand, while this one recommends — blending where watch demand concentrates with each condition’s relative price into a 0–100 strategy_score, then naming a single recommended condition. It requires the intelligence.read scope and a valid Authorization: Bearer <token> header.
This page covers the per-game condition recommendation. To rank or score whole titles by liquidity — or to score a lot/inventory in bulk — see Intelligence: Games.
How the recommendation is built
For each of the three sellable conditions — loose (cartridge/disc only), CIB (complete in box), and new (sealed) — the endpoint combines two normalised signals:- Demand concentration — how much of the game’s watch demand is attached to that condition, drawn from saved notification alerts where a buyer selected the condition they want.
- Relative value — that condition’s catalog price, normalised against the highest of the title’s three condition prices.
strategy_score, and the highest-scoring condition becomes the recommended pick.
demand_share
Each condition’s share of the game’s watch demand, expressed between 0.0 and 1.0. A high demand_share on cib means buyers who alert on this title overwhelmingly want the complete-in-box version.
value_index
Each condition’s catalog price normalised against the highest of the title’s three condition prices (0.0–1.0). The priciest condition scores 1.0; the others are scored relative to it. This is the value component that the strategy_score weighs against demand.
strategy_score
A 0–100 blend of demand concentration and relative value, normalised across the game’s three conditions:
w_demand and w_value) are set in the API’s serving configuration. The condition with the highest strategy_score is the one returned in recommended.
premiums
Price step-ups between conditions, expressed as ratios. complete_over_loose of 1.6786 means CIB sells for 168% of the loose price. Each ratio is null when its base price is 0.
GET /api/v1/intelligence//conditions
Returns the full condition breakdown for one game, scored and ranked, with a single recommended condition to list in.Path parameters
integer
required
The numeric ID of the game. You can resolve IDs from the Games catalog endpoints.
Query parameters
string
default:"7d"
The time window to aggregate over. One of
day, 7d, or 30d.string
Override the target window-end date. Defaults to the latest computed date. Format:
YYYY-MM-DD.Response
object
object
object
array
One row per sellable condition —
loose, cib, and new — sorted by strategy_score descending.string
The condition:
loose, cib, or new.string
The catalog price for this condition (decimal string).
integer
Active watchlist alerts for this game in this condition.
This condition’s share of the game’s watch demand (
0.0–1.0).float
This condition’s price normalised against the highest of the three condition prices (
0.0–1.0); the priciest condition is 1.0.integer
A
0–100 blend of demand concentration and relative value, normalised across the game’s three conditions.object
The single suggested condition to list in.
string
The highest-scoring condition (ties break to the higher price).
string
A short rationale reconciling the pick against the pure-demand and pure-value winners — e.g.
"where buyer demand concentrates", "best price with viable demand", "highest demand and best price", or "best demand/value balance".object
reason — "where buyer demand concentrates" — reconciles the recommendation against the pure-value winner (new).
Returns
404 not_found only when the id is not a real, enabled game.