Bet Size Profiles

Bet size profiles allow you to map the model's bet and raise amounts to predefined, human-like bet sizes. This makes the betting behavior more consistent and natural-looking while preserving the strategic decisions from the model.

When a bet size profile is applied, the system:

1. Selects a profile based on the current_user_id (ensuring consistency for the same user)
2. Maps each RL bet/raise amount to the closest valid bet size from the profile
3. Returns information about which profile was used and how amounts were mapped

Note: Bet size profiles are only applied to MTT (Multi-Table Tournament) requests. They have no effect on cash games or other formats.

How to request it:

Bet profiles are optional. To enable them, include the bet_profile field at the top-level of the request.

Example request:

{
    "request_id": "request-123",
    "hand": {...},
    "bet_profile": {
        "current_user_id": "user-123"
    }
}

Bet Profile current_user_id possible values:

The current_user_id accepts any string value, but it is recommended to use a simple numeric string (for example, "23", "45", "43").

Important: The same current_user_id will always map to the same bet size profile, ensuring consistent bet sizing behavior for that user. Different user IDs will map to different profiles from the available configuration.

Understanding the Response:

The response will contain information about the applied bet size profile. The information is contained in the solution_information field. The request below is an example of the response when a bet size profile is applied:

{
    "request": {...},
    "strategy": {...},
    "suggested_action": {...},
    "solution_information":{
        "bet_profile_config": {
            "bet_profile": {
                "open_raise": {
                    "B1": 1,
                    "P1": 0.67
                },
                "other_raise": {
                    "P1": 0.75,
                    "P2": 0.5,
                    "P3": 0.34,
                    "P4": 0.25
                }
            },
            "bet_profile_config_id": 4,
            "bet_size_mapping_result": [
                {
                    "from": 3625,
                    "key": "P1",
                    "to": 2138
                }
            ],
            "betsize_threshold": 0.75,
            "called_pot": 2250,
            "is_open_raise": false,
            "pot": 1800
        },
        (...)
    }
}

Response fields

• bet_profile: The bet size profile configuration that was selected and applied. Contains:

  • open_raise: Bet sizes available for the first voluntary raise in a pot where no one has entered the pot yet (keys like B1, P1, P2). Once someone limps (calls the big blind pre-flop instead of folding) or raises, the pot is already opened, so subsequent raises use other_raise instead.
  • other_raise: Bet sizes available for all other raises/bets (keys like P1, P2, P3, P4)

  Key meanings:

  • B1, B2, etc.: Big blind multipliers (e.g., B1 = 1 big blind)
  • P1, P2, P3, P4, etc.: Pot size multipliers (e.g., P1 = 0.67 means 67% of the pot)

• bet_profile_config_id: The index (0-based) of the profile selected from the configuration array. This is determined by hashing the current_user_id.

• bet_size_mapping_result: An array showing how RL model bet amounts were mapped to profile amounts. Each entry contains:

  • from: The original bet amount from the RL model
  • to: The mapped bet amount from the profile
  • key: The profile key used (e.g., "P1", "B1")

• betsize_threshold: The probability threshold (0.0 to 1.0) that determines whether bet size mapping is applied. Default is 0.75 (75% chance).

• is_open_raise: true if this decision point is the first voluntary raise in a pot where no one has entered the pot yet, false otherwise. Once someone limps (calls the big blind pre-flop instead of folding) or raises, the pot is already opened, so this will be false. Determines which profile section (open_raise vs other_raise) is used.

• pot: The current pot size (in chips) at the time of the decision.

• called_pot: The pot size if the current bet/raise were called (pot + call amount).

No profile applied

A bet size profile may not be applied in the following cases:

• The bet_profile field is missing or doesn't contain current_user_id
• The request is not for an MTT (Multi-Table Tournament) format

Important to note: even when the bet size profile is not applied, the solution_information field will still contain the bet_profile_config field with the following values:

{
    "request": {...},
    "strategy": {...},
    "suggested_action": {...},
    "solution_information":{
        "bet_profile_config": {
            "bet_profile": "no_profile_applied",
            "bet_profile_config_id": -1,
            "bet_size_mapping_result": "no_profile_applied",
            "betsize_threshold": 0.75,
            "called_pot": -1,
            "is_open_raise": false,
            "pot": -1
        },
        (...)
    }
}