Strategy Profiles v2
This documentation presents strategy profile data derived from self-play simulations against GTO (Game Theory Optimal) baseline strategies.
Understanding the Metrics
Preflop Metrics
- Target VPIP: Target percentage of hands Voluntarily Put money In Pot
- Target PFR: Target percentage of hands with Pre-Flop Raise
- Empirical VPIP: Actual VPIP achieved in self-play simulations
- Empirical PFR: Actual PFR achieved in self-play simulations
- BB/100: Big blinds won per 100 hands (relative to GTO baseline)
Postflop Metrics
- Target WTSD: Target percentage of hands that Went To ShowDown
- Target AF: Target Aggression Factor (ratio of aggressive to passive actions)
- Empirical WTSD: Actual WTSD achieved in self-play simulations
- Empirical AF: Actual AF achieved in self-play simulations
- BB/100: Big blinds won per 100 hands (relative to GTO baseline)
Game Format Notation
Game format notation X-Y:
- First number (X): Number of blinds (2 = SB+BB, 3 = SB+BB+Straddle)
- Second number (Y): Ante as percentage of big blind (0 = no ante, 50 = half BB, 100 = equal to BB)
Examples:
2-0: 2 blinds, no ante2-50: 2 blinds, 50% BB ante3-50: 3 blinds, 50% BB ante
Available Game Formats
Click on a game format below to view detailed strategy profile data:
Game Format 2-0
2 blinds, no ante
Game Format 2-50
2 blinds, 50% BB ante
Game Format 2-100
2 blinds, 100% BB ante
Game Format 3-0
3 blinds, no ante
Game Format 3-50
3 blinds, 50% BB ante
Special Profile: Splash
Special splash pot profile
Integration Notes
Release Information
Postflop strategy profiles V2 will be available to B2B clients on January 07, 2026.
Request Format
Strategy Profiles V2 uses the same request structure as V1. Include the strategy profile object in your request:
{
"request_id": "unique-request-id",
"hand": {...},
"strategy_profile": {
"target_profile_name": "wtsd51-af1.2"
}
}Important: Match profile types to game types:
- Preflop profiles → Preflop games
- Postflop profiles → Postflop games
Verifying Profile Application
Check solution_information.strategy_profile_config in the response to confirm profile application.
When profile is not applied:
{
"request": {},
"strategy": {<default results>},
"solution_information": {
(...),
"strategy_profile_config": {
"game_format": "no_profile_applied",
"matched_profile_name": "no_profile_applied",
"strategy_after_adjust": "no_profile_applied",
"strategy_before_adjust": "no_profile_applied"
}
}
}When fallback occurs:
The game_format field will show the fallback format that was actually used:
{
"solution_information": {
(...),
"strategy_profile_config": {
"game_format": "3-50",
"matched_profile_name": "vpip21-pfr13",
...
}
}
}Game Format Fallback Behavior
Strategy Profiles V2 includes automatic fallback functionality for cash games:
Default Fallback Format
- Fallback format:
3-50(3 blinds, 50% BB ante) - This is the default fallback used when the requested game format is not available
When Fallback Occurs
Fallback automatically activates in the following scenarios:
-
Requested game format not found
- If your game format (e.g.,
2-75) doesn't exist in the strategy profiles - System automatically falls back to
3-50format - Request succeeds with the fallback profile
- If your game format (e.g.,
-
Requested game format exists but is empty/invalid
- If the game format exists but has no valid profiles
- System automatically falls back to
3-50format - Request succeeds with the fallback profile
Fallback Limitations
- MTT tournaments: Fallback is disabled for MTT games
- MTT games use
2-15format and will fail if not found (no fallback) - This ensures MTT games don't accidentally use cash game profiles
- MTT games use
Verifying Fallback Usage
Check the game_format field in solution_information.strategy_profile_config:
- If it shows
3-50but you requested a different format, fallback was used - The
matched_profile_namewill show which profile was actually applied
Example:
- Request: Game format
2-75with profilevpip21-pfr13(preflop) orwtsd51-af1.2(postflop) - If
2-75doesn't exist, response shows:{ "solution_information": { "strategy_profile_config": { "game_format": "3-50", // Fallback format used "matched_profile_name": "vpip21-pfr13" // or "wtsd51-af1.2" for postflop } } }
Error Handling Behavior
Non-existent Profile Names
- Request succeeds with default GTO strategy
- Response includes
no_profile_appliedstatus - No service disruption
Profile Type Mismatch
Using preflop profiles for postflop games or vice versa:
- Request succeeds with default GTO strategy
- Response includes
no_profile_appliedstatus - Profile is ignored
MTT Tournament Requests
Warning: Strategy Profiles V2 are for cash games only.
- MTT requests with V2 profiles will fail
- Use Strategy Profiles V1 for MTT tournaments (supports
2-15game format)
Quick Reference
| Scenario | Request Result | Response Status | Strategy Applied |
|---|---|---|---|
| Valid profile + correct game type | Success | Profile name shown | Adjusted strategy |
| Invalid profile name | Success | no_profile_applied | Default GTO |
| Preflop profile → Postflop game | Success | no_profile_applied | Default GTO |
| Postflop profile → Preflop game | Success | no_profile_applied | Default GTO |
| Unavailable game format (cash) | Success | Falls back to 3-50 | Adjusted strategy (from fallback) |
| V2 Profile → MTT tournament | Failure | Error response | N/A |
| Unavailable game format (MTT) | Failure | Error response | N/A |