The example uses category tags and a player-only roster scope. Read category_contributors, metadata.unaccounted_constraints, and flip_conditions together.
Knowledge Base
Developer guides
Separate a current trade evaluation from a later projection revision.
A proposed discussion example for comparing a trade-day forecast with a later forecast.
This fictional H2H 9-category trade keeps the roster and player rates fixed. The received center's projected minutes are the only basketball input that changes.
Net gain over the outgoing player, across four games
Snapshot
Minutes/game
Rebounds
Blocks
Trade day
30
+25.99
+7.18
One week later
22
+14.26
+4.83
The values are synthetic. They are not hiiivelocity's trade, Basketball Monster data, a Basketball Monster win probability, or evidence that a model was wrong.
{
"scenario": "synthetic_center_minutes",
"as_of": "2026-11-21T00:00:00Z",
"league": {
"format": "H2H 9-cat",
"remaining_games_per_player": 4
},
"trade": {
"send": {
"name": "Synthetic wing sent",
"minutes_per_game": 32,
"per_game_at_30_minutes": {
"REB": 4.22,
"BLK": 0.38
}
},
"receive": {
"name": "Synthetic center received",
"minutes_per_game": 30,
"per_game_at_30_minutes": {
"REB": 11.0,
"BLK": 2.2
}
}
},
"assumption": "All inputs are synthetic. The received center's minutes are the only changing value between snapshots."
}
Trade-day response
{
"example_type": "synthetic_center_minutes",
"as_of": "2026-11-21T00:00:00Z",
"units": "projected category totals across the supplied remaining_games_per_player",
"center_minutes_per_game": 30,
"projected_trade_delta": {
"REB": 25.99,
"BLK": 7.18
},
"notices": [
"Synthetic example only. It is not a Basketball Monster output.",
"No win odds or real player projections are calculated."
]
}
Updated-projection request
{
"scenario": "synthetic_center_minutes",
"as_of": "2026-11-28T00:00:00Z",
"league": {
"format": "H2H 9-cat",
"remaining_games_per_player": 4
},
"trade": {
"send": {
"name": "Synthetic wing sent",
"minutes_per_game": 32,
"per_game_at_30_minutes": {
"REB": 4.22,
"BLK": 0.38
}
},
"receive": {
"name": "Synthetic center received",
"minutes_per_game": 22,
"per_game_at_30_minutes": {
"REB": 11.0,
"BLK": 2.2
}
}
},
"assumption": "All inputs are synthetic. The received center's minutes are the only changing value between snapshots."
}
Updated-projection response
{
"example_type": "synthetic_center_minutes",
"as_of": "2026-11-28T00:00:00Z",
"units": "projected category totals across the supplied remaining_games_per_player",
"center_minutes_per_game": 22,
"projected_trade_delta": {
"REB": 14.26,
"BLK": 4.83
},
"notices": [
"Synthetic example only. It is not a Basketball Monster output.",
"No win odds or real player projections are calculated."
]
}
Knowledge Base
Scope and limits
Keep observed source material and invented example values separate.
Use this for
Checking whether structured inputs distinguish a projection, roster context, and missing information in a trade explanation.
Do not use this for
Live trade advice, player forecasts, partner API claims, historical Basketball Monster comparisons, or evidence of user outcomes.
API Reference
API reference
The local server exposes a trade evaluation and a synthetic minutes scenario.
Base URL
http://127.0.0.1:8788
Endpoints
POST /v0/frame/trade-evaluations
Contextual evaluation for synthetic player proposals.
POST /v0/frame/minutes-scenarios
One synthetic center-minutes snapshot.
API Reference
Trade evaluations
Send player proposals with league rules, category context, and roster scope.
POST/v0/frame/trade-evaluations
Try a local request
Open this page locally to run the request.
Request body
The local implementation accepts one or more proposals. A player-only scope causes the response to record the roster context it cannot account for.