PioSOLVER

https://piosolver.com/docs
Admin
PioSOLVER is a postflop equilibrium solver for Texas Hold'em poker that calculates optimal...
Tokens:42,536
Snippets:270
Trust Score:9.1
Update:9 months ago
Show doc for...
Tokens:
Raw
### Tree Building Commands

Source: https://piosolver.com/docs/upi/commands

Commands related to building postflop and preflop game trees.

```APIDOC
## Commands related to building the tree

Building a postflop tree consists of:
* Setting global state first (range, stacks, board)
* Adding betting lines
* Executing `build_tree` command

Building a preflop tree consists of:
* Setting global state first (ranges, stacks)
* Adding preflop betting lines
* Building pure preflop tree
* Setting postflop trees and adding them to postflop exits
* Specifying flops subset
* Building full preflop tree by executing `add_all_flops` command

*Note: Specific API endpoints for `build_tree`, `add_all_flops`, and associated commands for setting ranges, stacks, board, and betting lines are not detailed in the provided text. Please refer to Piosolver's full documentation for these.*
```

--------------------------------

### Additional Commands

Source: https://piosolver.com/docs/upi/commands

Utility commands for managing output, inspecting the game tree, and system information.

```APIDOC
## stdoutredi

### Description
Redirects the standard output stream to a specified file.

### Method
POST

### Endpoint
/websites/piosolver/stdoutredi

### Parameters
#### Path Parameters
N/A

#### Query Parameters
- **filename** (string) - Required - The name of the file to redirect stdout to.

#### Request Body
N/A

### Request Example
(No request body)

### Response
#### Success Response (200)
- **message** (string) - Indicates success (usually empty or a confirmation).

#### Response Example
```json
{
  "message": "stdout redirected to filename.txt"
}
```

## stdoutredi_append

### Description
Redirects the standard output stream to a specified file, appending to it instead of overwriting.

### Method
POST

### Endpoint
/websites/piosolver/stdoutredi_append

### Parameters
#### Path Parameters
N/A

#### Query Parameters
- **filename** (string) - Required - The name of the file to append stdout to.

#### Request Body
N/A

### Request Example
(No request body)

### Response
#### Success Response (200)
- **message** (string) - Indicates success (usually empty or a confirmation).

#### Response Example
```json
{
  "message": "stdout appended to filename.txt"
}
```

## stdoutback

### Description
Restores the standard output stream back to the console. This is useful when working with text interfaces.

### Method
POST

### Endpoint
/websites/piosolver/stdoutback

### Parameters
#### Path Parameters
N/A

#### Query Parameters
N/A

#### Request Body
N/A

### Request Example
(No request body)

### Response
#### Success Response (200)
- **message** (string) - stdoutback ok!

#### Response Example
```json
{
  "message": "stdoutback ok!"
}
```

## print_all_strats

### Description
Prints the nodeID for all nodes in the game tree. For decision nodes, it also prints their associated strategies.

### Method
GET

### Endpoint
/websites/piosolver/print_all_strats

### Parameters
#### Path Parameters
N/A

#### Query Parameters
N/A

#### Request Body
N/A

### Request Example
(No request body)

### Response
#### Success Response (200)
- **output** (string) - A multi-line string containing nodeIDs and strategies.

#### Response Example
```text
12345
67890 nodeID: 12345 strategy: [0.5, 0.5]
...
```

## node_count

### Description
Counts and prints the number of nodes for each type (H_DEC, FLOP, TURN, RIVER, etc.) in the game tree.

### Method
GET

### Endpoint
/websites/piosolver/node_count

### Parameters
#### Path Parameters
N/A

#### Query Parameters
N/A

#### Request Body
N/A

### Request Example
(No request body)

### Response
#### Success Response (200)
- **counts** (string) - A multi-line string detailing the count for each node type (e.g., "H_DEC: 339\nFLOP: 0").

#### Response Example
```text
H_DEC: 339
FLOP: 0
TURN: 3
RIVER: 336
```

## clear_cache

### Description
Clears any cached results stored within the game tree.

### Method
POST

### Endpoint
/websites/piosolver/clear_cache

### Parameters
#### Path Parameters
N/A

#### Query Parameters
N/A

#### Request Body
N/A

### Request Example
(No request body)

### Response
#### Success Response (200)
- **message** (string) - clear_cache ok!

#### Response Example
```json
{
  "message": "clear_cache ok!"
}
```

## show_cpu_info

### Description
Displays information about the system's CPU, including the number of CPUs, maximum threads, and thread affinity policy.

### Method
GET

### Endpoint
/websites/piosolver/show_cpu_info

### Parameters
#### Path Parameters
N/A

#### Query Parameters
N/A

#### Request Body
N/A

### Request Example
(No request body)

### Response
#### Success Response (200)
- **cpu_info** (string) - Detailed CPU information (e.g., "number of CPUs: 16\nmax threads: 16").

#### Response Example
```text
number of CPUs: 16
max threads: 16
thread limit is: 2147483647
affinity policy is: 0
```

## show_nuts

### Description
Shows the number of combos in the villain's range that are winning against a given hand. A value of 0 indicates the nuts.

### Method
GET

### Endpoint
/websites/piosolver/show_nuts

### Parameters
#### Path Parameters
N/A

#### Query Parameters
- **hand** (string) - Required - The hand to evaluate against.
- **opponent_position** (string) - Required - The opponent's position (e.g., "OOP", "IP").

#### Request Body
N/A

### Request Example
(No request body)

### Response
#### Success Response (200)
- **nuts_info** (string) - Information about winning combos per live hand (e.g., "hand - number").

#### Response Example
```text
AsKs - 50
AhKh - 75
```
```

--------------------------------

### Preflop Tree Building API

Source: https://piosolver.com/docs/upi/commands

Endpoints for setting up and building preflop poker trees, including subset management.

```APIDOC
## POST /websites/piosolver/add_preflop_line

### Description
Adds a betting sequence for a pure preflop tree. This is similar to `add_line` but specifically for the preflop street.

### Method
POST

### Endpoint
/websites/piosolver/add_preflop_line

### Parameters
#### Query Parameters
- **line** (string) - Required - A series of numbers representing cumulative bet sizes for the preflop action.

### Request Example
```json
{
  "line": "0 50 150"
}
```

### Response
#### Success Response (200)
- **message** (string) - Confirmation message, e.g., "Add_preflop_line ok!"

#### Response Example
```json
{
  "message": "Add_preflop_line ok!"
}
```
```

```APIDOC
## POST /websites/piosolver/remove_preflop_line

### Description
Removes a preflop betting sequence that was previously added. This allows modification of the preflop tree structure.

### Method
POST

### Endpoint
/websites/piosolver/remove_preflop_line

### Parameters
#### Query Parameters
- **line** (string) - Required - A series of numbers representing the preflop line to remove.

### Request Example
```json
{
  "line": "0 50"
}
```

### Response
#### Success Response (200)
- **message** (string) - Confirmation message, e.g., "remove_preflop_line ok!"

#### Response Example
```json
{
  "message": "remove_preflop_line ok!"
}
```
```

```APIDOC
## POST /websites/piosolver/clear_preflop_lines

### Description
Clears the preflop tree structure created by `add_preflop_line` commands, resetting it to an empty state.

### Method
POST

### Endpoint
/websites/piosolver/clear_preflop_lines

### Parameters
*No parameters required.*

### Request Example
```json
{}
```

### Response
#### Success Response (200)
- **message** (string) - Confirmation message, e.g., "Clear_preflop_lines ok!"

#### Response Example
```json
{
  "message": "Clear_preflop_lines ok!"
}
```
```

```APIDOC
## POST /websites/piosolver/build_preflop_tree

### Description
Builds a pure preflop tree based on the sequences defined by `add_preflop_line` commands.

### Method
POST

### Endpoint
/websites/piosolver/build_preflop_tree

### Parameters
*No parameters required.*

### Request Example
```json
{}
```

### Response
#### Success Response (200)
- **message** (string) - Confirmation message, e.g., "Build_preflop_tree ok!"

#### Response Example
```json
{
  "message": "Build_preflop_tree ok!"
}
```
```

```APIDOC
## POST /websites/piosolver/add_to_subset

### Description
Adds a specified board with a given weight to a flop subset. This subset can later be used to build a preflop tree with selected flops.

### Method
POST

### Endpoint
/websites/piosolver/add_to_subset

### Parameters
#### Query Parameters
- **weight** (float) - Required - The weight of the board in the subset.
- **card1** (string) - Required - The first card of the board (e.g., "Ac").
- **card2** (string) - Required - The second card of the board (e.g., "Kd").
- **card3** (string) - Required - The third card of the board (e.g., "Jc").

### Request Example
```json
{
  "weight": 1.0,
  "card1": "Ac",
  "card2": "Kd",
  "card3": "Jc"
}
```

### Response
#### Success Response (200)
- **message** (string) - Confirmation message, e.g., "Add_to_subset ok!"

#### Response Example
```json
{
  "message": "Add_to_subset ok!"
}
```
```

```APIDOC
## POST /websites/piosolver/reset_subset

### Description
Clears the current flop subset, removing all previously added boards and weights.

### Method
POST

### Endpoint
/websites/piosolver/reset_subset

### Parameters
*No parameters required.*

### Request Example
```json
{}
```

### Response
#### Success Response (200)
- **message** (string) - Confirmation message, e.g., "Reset_subset ok!"

#### Response Example
```json
{
  "message": "Reset_subset ok!"
}
```
```

```APIDOC
## GET /websites/piosolver/show_subset

### Description
Prints the current flops with their associated weights from the flop subset.

### Method
GET

### Endpoint
/websites/piosolver/show_subset

### Parameters
*No parameters required.*

### Request Example
```json
{}
```

### Response
#### Success Response (200)
- **subset_data** (string) - Multiline string, where each line is 'weight board', e.g., "1.0 Ac Kd Jc".

#### Response Example
```json
{
  "subset_data": "1.0 Ac Kd Jc\n0.5 Ah Kh Qh"
}
```
```

```APIDOC
## POST /websites/piosolver/recover_subset

### Description
If a preflop tree is loaded, this command replaces the current flop subset with the subset stored within that loaded tree.

### Method
POST

### Endpoint
/websites/piosolver/recover_subset

### Parameters
*No parameters required.*

### Request Example
```json
{}
```

### Response
#### Success Response (200)
- **message** (string) - Confirmation message, e.g., "recover_subset ok!"

#### Response Example
```json
{
  "message": "recover_subset ok!"
}
```
```

```APIDOC
## POST /websites/piosolver/add_schematic_tree

### Description
Attaches a postflop abstraction (a tree built with `add_line` commands) to a chosen preflop exit node.

### Method
POST

### Endpoint
/websites/piosolver/add_schematic_tree

### Parameters
#### Query Parameters
- **nodeID** (string) - Required - The identifier of the preflop exit node (must be a SPLIT_NODE).

### Request Example
```json
{
  "nodeID": "preflop_exit_1"
}
```

### Response
#### Success Response (200)
- **message** (string) - Confirmation message, e.g., "add_schematic_tree ok!"

#### Response Example
```json
{
  "message": "add_schematic_tree ok!"
}
```
```

```APIDOC
## POST /websites/piosolver/add_all_flops

### Description
Uses the flops currently defined in the flop subset to build a full preflop tree.

### Method
POST

### Endpoint
/websites/piosolver/add_all_flops

### Parameters
*No parameters required.*

### Request Example
```json
{}
```

### Response
#### Success Response (200)
- **message** (string) - Confirmation message, e.g., "add_all_flops ok!"

#### Response Example
```json
{
  "message": "add_all_flops ok!"
}
```
```

--------------------------------

### Postflop Tree Building API

Source: https://piosolver.com/docs/upi/commands

Endpoints for setting up and building postflop poker trees.

```APIDOC
## POST /websites/piosolver/set_range

### Description
Sets the range for the OOP (Out Of Position) or IP (In Position) player in the global state. This is a fundamental step before building a tree.

### Method
POST

### Endpoint
/websites/piosolver/set_range

### Parameters
#### Query Parameters
- **OOP** (string) - Optional - The range for the OOP player.
- **IP** (string) - Optional - The range for the IP player.

### Request Example
```json
{
  "OOP": "IP 1326 floats"
}
```

### Response
#### Success Response (200)
- **message** (string) - Confirmation message, e.g., "set_range ok!"

#### Response Example
```json
{
  "message": "set_range ok!"
}
```
```

```APIDOC
## POST /websites/piosolver/set_eff_stack

### Description
Sets the effective stack size in the global state. This is crucial for identifying all-in nodes during tree construction.

### Method
POST

### Endpoint
/websites/piosolver/set_eff_stack

### Parameters
#### Query Parameters
- **stack_size** (integer) - Required - The effective stack size.

### Request Example
```json
{
  "stack_size": 100
}
```

### Response
#### Success Response (200)
- **message** (string) - Confirmation message, e.g., "Set_eff_stack ok!"

#### Response Example
```json
{
  "message": "Set_eff_stack ok!"
}
```
```

```APIDOC
## POST /websites/piosolver/set_board

### Description
Sets the current board cards in the global state. This defines the community cards for the hand.

### Method
POST

### Endpoint
/websites/piosolver/set_board

### Parameters
#### Query Parameters
- **cards** (string) - Required - A string representing the cards, e.g., "AcKdJc".

### Request Example
```json
{
  "cards": "AcKdJc"
}
```

### Response
#### Success Response (200)
- **message** (string) - Confirmation message, e.g., "set_board ok!"

#### Response Example
```json
{
  "message": "set_board ok!"
}
```
```

```APIDOC
## POST /websites/piosolver/set_pot

### Description
Sets the initial pot size in the global state, specifying amounts for OOP, IP, and dead cards.

### Method
POST

### Endpoint
/websites/piosolver/set_pot

### Parameters
#### Query Parameters
- **oop_pot** (integer) - Required - The pot size for the OOP player.
- **ip_pot** (integer) - Required - The pot size for the IP player.
- **dead_cards_pot** (integer) - Required - The pot size from dead cards.

### Request Example
```json
{
  "oop_pot": 10,
  "ip_pot": 10,
  "dead_cards_pot": 0
}
```

### Response
#### Success Response (200)
- **message** (string) - Confirmation message, e.g., "set_pot ok!"

#### Response Example
```json
{
  "message": "set_pot ok!"
}
```
```

```APIDOC
## POST /websites/piosolver/add_line

### Description
Adds a betting sequence (line) to the current tree structure. This defines a specific path of actions (checks, bets, calls, folds) for a street.

### Method
POST

### Endpoint
/websites/piosolver/add_line

### Parameters
#### Query Parameters
- **line** (string) - Required - A series of numbers representing cumulative bet sizes. Example: "0 30 30 30 90" represents check OOP, bet IP, call, check turn, bet 60.

### Request Example
```json
{
  "line": "0 30 30 30 90"
}
```

### Response
#### Success Response (200)
- **message** (string) - Confirmation message, e.g., "add_line ok!"

#### Response Example
```json
{
  "message": "add_line ok!"
}
```
```

```APIDOC
## POST /websites/piosolver/remove_line

### Description
Removes a previously added betting sequence (line) from the tree structure. This allows for modifying the tree by excluding specific action paths.

### Method
POST

### Endpoint
/websites/piosolver/remove_line

### Parameters
#### Query Parameters
- **line** (string) - Required - A series of numbers representing the line to remove, using the same syntax as `add_line`. Example: "0 30 0" removes a fold for OOP player.

### Request Example
```json
{
  "line": "0 30 0"
}
```

### Response
#### Success Response (200)
- **message** (string) - Confirmation message, e.g., "remove_line ok!"

#### Response Example
```json
{
  "message": "remove_line ok!"
}
```
```

```APIDOC
## POST /websites/piosolver/force_line

### Description
Forces a specific betting sequence by removing all other lines that do not have the specified line as a prefix. This is used to isolate a particular line of play.

### Method
POST

### Endpoint
/websites/piosolver/force_line

### Parameters
#### Query Parameters
- **line** (string) - Required - A series of numbers representing the bet sizes for the line to be forced.

### Request Example
```json
{
  "line": "0 30 30 60"
}
```

### Response
#### Success Response (200)
- **message** (string) - Confirmation message, e.g., "force_line ok!"

#### Response Example
```json
{
  "message": "force_line ok!"
}
```
```

```APIDOC
## POST /websites/piosolver/clear_lines

### Description
Resets the state created by `add_line`, `remove_line`, and `force_line` commands, effectively clearing the current postflop tree structure.

### Method
POST

### Endpoint
/websites/piosolver/clear_lines

### Parameters
*No parameters required.*

### Request Example
```json
{}
```

### Response
#### Success Response (200)
- **message** (string) - Confirmation message, e.g., "clear_lines ok!"

#### Response Example
```json
{
  "message": "clear_lines ok!"
}
```
```

```APIDOC
## POST /websites/piosolver/build_tree

### Description
Builds the postflop tree based on the configured global state and lines added. It can take an optional argument to control memory checking behavior.

### Method
POST

### Endpoint
/websites/piosolver/build_tree

### Parameters
#### Query Parameters
- **memory_option** (string) - Optional - Specifies memory handling: `mem_ignore` (no memory check), `mem_pessimistic` (pessimistic memory check), or `default` (builds only if enough memory).

### Request Example
```json
{
  "memory_option": "mem_ignore"
}
```

### Response
#### Success Response (200)
- **message** (string) - Confirmation message, e.g., "build_tree ok!"

#### Response Example
```json
{
  "message": "build_tree ok!"
}
```
```

--------------------------------

### Additional Tree Building Settings API

Source: https://piosolver.com/docs/upi/commands

Endpoints for configuring algorithms, memory checks, and strategy precision.

```APIDOC
## GET /websites/piosolver/list_algorithms

### Description
Lists the available algorithms that can be used for tree building, along with their codes and descriptions.

### Method
GET

### Endpoint
/websites/piosolver/list_algorithms

### Parameters
*No parameters required.*

### Request Example
```json
{}
```

### Response
#### Success Response (200)
- **algorithms** (array) - An array of algorithm objects, each containing 'code', 'name', and 'description'.

#### Response Example
```json
{
  "algorithms": [
    {"code": "original_pio", "name": "Original PioSolver", "description": "Original PioSolver algorithm that uses less memory"},
    {"code": "pio_cfr", "name": "Pio CFR", "description": "Pio CFR algorithm"}
  ]
}
```
```

```APIDOC
## POST /websites/piosolver/set_algorithm

### Description
Sets the algorithm to be used for building a tree. This setting is applied at the time of tree building and cannot be changed afterwards.

### Method
POST

### Endpoint
/websites/piosolver/set_algorithm

### Parameters
#### Query Parameters
- **algorithm_code** (string) - Required - The code of the algorithm to set. Possible values: `auto`, `pio_cfr`, `original_pio`.

### Request Example
```json
{
  "algorithm_code": "pio_cfr"
}
```

### Response
#### Success Response (200)
- **message** (string) - Confirmation message, e.g., "set_algorithm ok!"

#### Response Example
```json
{
  "message": "set_algorithm ok!"
}
```
```

```APIDOC
## POST /websites/piosolver/ignore_mem_check

### Description
Controls whether the memory check is performed before building a tree. Setting it to 'on' disables the check.

### Method
POST

### Endpoint
/websites/piosolver/ignore_mem_check

### Parameters
#### Query Parameters
- **setting** (string) - Required - The setting for memory check: `on` or `off`.

### Request Example
```json
{
  "setting": "on"
}
```

### Response
#### Success Response (200)
- **message** (string) - Confirmation message, e.g., "ignore_mem_check ok!"

#### Response Example
```json
{
  "message": "ignore_mem_check ok!"
}
```
```

```APIDOC
## POST /websites/piosolver/small_strats

### Description
Configures the precision used to store strategies. 'on' uses float16, 'off' uses float32, and 'auto' uses float16 for preflop and float32 for others.

### Method
POST

### Endpoint
/websites/piosolver/small_strats

### Parameters
#### Query Parameters
- **setting** (string) - Required - The setting for strategy precision: `on`, `off`, or `auto`.

### Request Example
```json
{
  "setting": "on"
}
```

### Response
#### Success Response (200)
- **message** (string) - Confirmation message, e.g., "small_strats ok!"

#### Response Example
```json
{
  "message": "small_strats ok!"
}
```
```

```APIDOC
## GET /websites/piosolver/estimate_tree

### Description
Estimates the size and memory requirements for the preflop tree based on the current subset configuration.

### Method
GET

### Endpoint
/websites/piosolver/estimate_tree

### Parameters
*No parameters required.*

### Request Example
```json
{}
```

### Response
#### Success Response (200)
- **estimate** (string) - A human-readable estimate of the preflop tree.

#### Response Example
```json
{
  "estimate": "Estimated size: 100MB, Nodes: 1,000,000"
}
```
```

```APIDOC
## GET /websites/piosolver/estimate_schematic_tree

### Description
Estimates the size and memory requirements for a postflop tree using different algorithms. This is useful for evaluating performance before building.

### Method
GET

### Endpoint
/websites/piosolver/estimate_schematic_tree

### Parameters
*No parameters required.*

### Request Example
```json
{}
```

### Response
#### Success Response (200)
- **estimate** (string) - A human-readable estimate of the postflop tree with different algorithms.

#### Response Example
```json
{
  "estimate": "Algorithm A: 50MB, Algorithm B: 75MB"
}
```
```

```APIDOC
## GET /websites/piosolver/show_memory

### Description
Displays information about the system's available physical memory.

### Method
GET

### Endpoint
/websites/piosolver/show_memory

### Parameters
*No parameters required.*

### Request Example
```json
{}
```

### Response
#### Success Response (200)
- **memory_info** (string) - A string containing details about total and available memory.

#### Response Example
```json
{
  "memory_info": "Total Physical Memory: 65214 MB\nAvailable Phys Memory: 45093 MB"
}
```
```

--------------------------------

### Player Profile Modeling via Incentives

Source: https://piosolver.com/docs/upi/commands

Commands for setting and managing EV incentives for player actions.

```APIDOC
## Player profile modeling via incentives

### set_incentives_node

**Description:** Sets EV incentives for N child actions in a specified node.

**Method:** N/A (Command-line execution)

**Arguments:**
- `nodeID`: The identifier of the node.
- `N floats`: N floating-point numbers representing incentives for child actions.

**Response Format:** `set_incentives_node ok!`

### set_incentives_line

**Description:** Sets EV incentives for N child actions in a specified line.

**Method:** N/A (Command-line execution)

**Arguments:**
- `lineID`: The identifier of the line.
- `N floats`: N floating-point numbers representing incentives for child actions.

**Response Format:** `set_incentives_line ok!`

### show_incentives

**Description:** Shows the incentives set for a specified node.

**Method:** N/A (Command-line execution)

**Arguments:**
- `nodeID`: The identifier of the node.

**Response Format:** `N floats` (The incentives set for the node)

### clear_incentives

**Description:** Clears all incentives set for a specified node.

**Method:** N/A (Command-line execution)

**Arguments:**
- `nodeID`: The identifier of the node.

**Response Format:** `clear_incentives ok!`
```

--------------------------------

### General UPI Commands

Source: https://piosolver.com/docs/upi/commands

This section details general UPI commands for managing solver settings and status.

```APIDOC
## General UPI Commands

### Description
Provides general commands for the UPI solver, including initialization checks, configuration, and version information.

### Commands

#### `is_ready`

- **Description**: Checks if the solver is initialized and ready to receive commands.
- **Request**: `is_ready`
- **Response**: `is_ready ok!`

#### `exit`

- **Description**: Terminates the solver's process.
- **Request**: `exit`
- **Response**: None (process terminates)

#### `set_end_string`

- **Description**: Sets a custom string that will terminate every solver response.
- **Request**: `set_end_string <string>`
- **Response**: `set_end_string ok!`

#### `reset_end_string`

- **Description**: Clears the custom end string setting, reverting to the default termination behavior.
- **Request**: `reset_end_string`
- **Response**: `reset_end_string ok!`

#### `show_version`

- **Description**: Retrieves a human-readable version of the program.
- **Request**: `show_version`
- **Response**: `number or text` (program version)

#### `show_build_version`

- **Description**: Retrieves the build version of the program.
- **Request**: `show_build_version`
- **Response**: `number or text` (build version)

#### `show_settings`

- **Description**: Displays the current global solver settings.
- **Request**: `show_settings`
- **Response**: `many lines with 'name: value' pairs` (solver settings)

#### `bench`

- **Description**: Runs a performance benchmark by building a large tree, performing iterations, and returning the execution time.
- **Request**: `bench`
- **Response**: `Time taken: float` (running time in seconds)

#### `load_script`

- **Description**: Reads and executes commands from a specified file line by line. After EOF, it returns to receiving input from stdin. **Warning**: Not recommended for use from other programs. Use `load_script_silent` or execute commands manually.
- **Request**: `load_script <filename>`
- **Response**: `load_script ok!`

#### `load_script_silent`

- **Description**: A silent version of `load_script` that executes commands from a file and returns only one END string at the very end.
- **Request**: `load_script_silent <filename>`
- **Response**: `load_script_silent ok!`

```

--------------------------------

### File Operations

Source: https://piosolver.com/docs/upi/commands

Commands for loading, saving, and managing PioSolver tree files.

```APIDOC
## Save / load / read files

### load_tree

**Description:** Loads a tree from a save file into memory. `State.root` will point to this tree.

**Method:** N/A (Command-line execution)

**Arguments:**
- `filename`: The name of the save file.
- `[full | fast | auto (default)]`: Optional argument to control the loading mode.
  - `full`: Loads all data.
  - `fast`: Loads essential data, other data can be loaded later with `load_all_nodes`.
  - `auto`: PioSolver decides the best mode.

**Response Format:** `load_tree ok!`

**Possible Errors:** I/O errors, file format error, out of memory.

### dump_tree

**Description:** Saves the current tree to disk.

**Method:** N/A (Command-line execution)

**Arguments:**
- `Filename`: The name of the file to save to.
- `[full | no_turns | no_rivers]`: Optional arguments to control the save detail.
  - `full`: Saves the entire tree.
  - `no_turns`: Saves without turn data.
  - `no_rivers`: Saves without river data.

**Response Format:** `dump_tree ok!`

**Note:** If `no_turns` or `no_rivers` is provided, a smaller save is made while the whole tree is preserved in memory.

### free_tree

**Description:** Deletes the current tree from memory and frees associated memory.

**Method:** N/A (Command-line execution)

**Arguments:** n/a

**Response Format:** `free_tree ok!`

### show_metadata

**Description:** Shows metadata about a specified save file without loading the entire tree.

**Method:** N/A (Command-line execution)

**Arguments:**
- `filename`: The name of the save file.

**Response Format:** Multiline string containing metadata.

**Note:** This command can provide information similar to `show_node r`, `show_effective_stack`, `show_range OOP r`, `show_range IP r`, and `show_tree_info`.

### show_save_version

**Description:** Checks if a file is a PioSolver tree file and displays its internal version number.

**Method:** N/A (Command-line execution)

**Arguments:**
- `filename`: The name of the save file.

**Response Format:** One line string indicating if it's a PioSolver file and its version.

### load_all_nodes

**Description:** Loads all remaining data for a tree that was initially loaded with the `fast` option.

**Method:** N/A (Command-line execution)

**Arguments:** n/a

**Response Format:** `load_all_nodes ok!`
```

--------------------------------

### Solver Control Commands

Source: https://piosolver.com/docs/upi/commands

Commands to control the execution and behavior of the Piosolver.

```APIDOC
## POST go

### Description
Starts or resumes the Piosolver. It can run indefinitely or for a specified duration (in seconds) or number of steps.

### Method
POST

### Endpoint
/websites/piosolver/go

### Parameters
#### Request Body
- **duration** (integer) - Optional - The number of seconds to run the solver.
- **steps** (integer) - Optional - The number of steps to run the solver.
  *If neither `duration` nor `steps` is provided, the solver will run indefinitely until manually stopped or accuracy is reached.*

### Request Example
```json
{
  "steps": 10000
}
```

### Response
#### Success Response (200)
- **status** (string) - "go ok!"
- **message** (string) - "SOLVER: started" (emitted once running)

#### Response Example
```json
{
  "status": "go ok!",
  "message": "SOLVER: started"
}
```

## POST stop

### Description
Stops the Piosolver and waits for it to gracefully shut down.

### Method
POST

### Endpoint
/websites/piosolver/stop

### Parameters
None

### Response
#### Success Response (200)
- **status** (string) - "go ok!"
- **message** (string) - "SOLVER: stopped"

#### Response Example
```json
{
  "status": "go ok!",
  "message": "SOLVER: stopped"
}
```

## POST wait_for_solver

### Description
Waits until the Piosolver finishes its current task before proceeding with further commands. Useful for scripting sequential operations.

### Method
POST

### Endpoint
/websites/piosolver/wait_for_solver

### Parameters
None

### Response
#### Success Response (200)
- **status** (string) - "wait_for_solver ok!"

#### Response Example
```json
{
  "status": "wait_for_solver ok!"
}
```

## POST take_a_break

### Description
Pauses the Piosolver for a specified number of seconds before resuming operation.

### Method
POST

### Endpoint
/websites/piosolver/take_a_break

### Parameters
#### Request Body
- **seconds** (integer) - Required - The number of seconds to pause the solver.

### Request Example
```json
{
  "seconds": 60
}
```

### Response
#### Success Response (200)
- **status** (string) - "take_a_break ok!"

#### Response Example
```json
{
  "status": "take_a_break ok!"
}
```

## GET solver_time

### Description
Retrieves the total time in seconds that the current Piosolver instance has been running.

### Method
GET

### Endpoint
/websites/piosolver/solver_time

### Parameters
None

### Response
#### Success Response (200)
- **time_seconds** (float) - The elapsed time in seconds.

#### Response Example
```json
{
  "time_seconds": 1234.56
}
```

## POST set_threads

### Description
Sets the number of CPU threads the Piosolver will use for calculations that involve tree traversal.

### Method
POST

### Endpoint
/websites/piosolver/set_threads

### Parameters
#### Request Body
- **num_threads** (integer) - Required - The number of threads to set.

### Request Example
```json
{
  "num_threads": 8
}
```

### Response
#### Success Response (200)
- **status** (string) - "set_threads ok!"

#### Response Example
```json
{
  "status": "set_threads ok!"
}
```

## POST set_info_freq

### Description
Configures how often the Piosolver should output status information during computation. The default is every 25 steps.

### Method
POST

### Endpoint
/websites/piosolver/set_info_freq

### Parameters
#### Request Body
- **frequency** (integer) - Required - The interval (in steps) at which to report solver info.

### Request Example
```json
{
  "frequency": 100
}
```

### Response
#### Success Response (200)
- **status** (string) - "set_info_freq ok!"

#### Response Example
```json
{
  "status": "set_info_freq ok!"
}
```

## POST set_accuracy

### Description
Sets the stopping accuracy for the Piosolver. By default, the accuracy is 0, meaning it runs indefinitely unless stopped manually. Accuracy can be specified as an absolute chip value or a fraction of the pot.

### Method
POST

### Endpoint
/websites/piosolver/set_accuracy

### Parameters
#### Request Body
- **value** (float) - Required - The accuracy value.
- **unit** (string) - Optional - The unit for the accuracy value. Can be "chips" (default) or "fraction".

### Request Example
```json
{
  "value": 0.01,
  "unit": "fraction"
}
```

### Response
#### Success Response (200)
- **status** (string) - "set_accuracy ok!"

#### Response Example
```json
{
  "status": "set_accuracy ok!"
}
```

## POST set_recalc_accuracy

### Description
Sets the accuracy thresholds for recalculations that occur on the flop, turn, and river when using `solve_partial`, browsing incomplete trees, or when `auto_recalc` is enabled.

### Method
POST

### Endpoint
/websites/piosolver/set_recalc_accuracy

### Parameters
#### Request Body
- **flop_accuracy** (float) - Required - Accuracy for flop recalculations.
- **turn_accuracy** (float) - Required - Accuracy for turn recalculations.
- **river_accuracy** (float) - Required - Accuracy for river recalculations.

### Request Example
```json
{
  "flop_accuracy": 0.01,
  "turn_accuracy": 0.005,
  "river_accuracy": 0.001
}
```

### Response
#### Success Response (200)
- **status** (string) - "set_recalc_accuracy ok!"

#### Response Example
```json
{
  "status": "set_recalc_accuracy ok!"
}
```

## POST set_always_recalc

### Description
Enables or disables automatic recalculation of nodes at specified streets. If enabled, the solver will recalculate nodes to meet the `recalc_accuracy` or a specified time limit, whichever comes first.

### Method
POST

### Endpoint
/websites/piosolver/set_always_recalc

### Parameters
#### Request Body
- **street** (integer) - Required - The street to enable recalculation for (0 to disable, 3 for Flop, 4 for Turn, 5 for River).
- **timeout_ms** (integer) - Required - The timeout in milliseconds for recalculation.

### Request Example
```json
{
  "street": 4,
  "timeout_ms": 5000
}
```

### Response
#### Success Response (200)
- **status** (string) - "set_always_recalc ok!"

#### Response Example
```json
{
  "status": "set_always_recalc ok!"
}
```

## POST set_isomorphism

### Description
Controls the use of isomorphism for optimizing calculations on the flop and turn. Isomorphism can significantly speed up calculations by identifying and treating symmetrical parts of the game tree identically.

### Method
POST

### Endpoint
/websites/piosolver/set_isomorphism

### Parameters
#### Request Body
- **flop_on** (integer) - Required - Set to 1 to enable isomorphism for flop trees, 0 to disable.
- **turn_on** (integer) - Required - Set to 1 to enable isomorphism for turn trees, 0 to disable.
  *Default is flop enabled (1) and turn disabled (0).*

### Request Example
```json
{
  "flop_on": 1,
  "turn_on": 0
}
```

### Response
#### Success Response (200)
- **status** (string) - "set_isomorphism ok!"

#### Response Example
```json
{
  "status": "set_isomorphism ok!"
}
```

## POST change_step

### Description
Adjusts the 'step' parameter, which influences the aggressiveness of the solver's strategy adjustments during computation. Higher values lead to more aggressive changes.

### Method
POST

### Endpoint
/websites/piosolver/change_step

### Parameters
#### Request Body
- **step_value** (float) - Required - The new value for the step parameter.

### Request Example
```json
{
  "step_value": 0.5
}
```

### Response
#### Success Response (200)
- **status** (string) - "change_step ok!"

#### Response Example
```json
{
  "status": "change_step ok!"
}
```

## GET show_step

### Description
Retrieves the current value of the solver's 'step' parameter.

### Method
GET

### Endpoint
/websites/piosolver/show_step

### Parameters
None

### Response
#### Success Response (200)
- **step_value** (float) - The current step parameter value.

#### Response Example
```json
{
  "step_value": 0.1
}
```

## GET show_iters

### Description
Returns the total number of solving iterations performed on the current game tree.

### Method
GET

### Endpoint
/websites/piosolver/show_iters

### Parameters
None

### Response
#### Success Response (200)
- **iterations** (integer) - The total number of iterations.

#### Response Example
```json
{
  "iterations": 50000
}
```

## POST set_first_iteration_player

### Description
Determines which player (Out of Position or In Position) adjusts their strategy first during a full iteration of the solver.

### Method
POST

### Endpoint
/websites/piosolver/set_first_iteration_player

### Parameters
#### Request Body
- **player_type** (string) - Required - Can be "OOP" (Out of Position) or "IP" (In Position).

### Request Example
```json
{
  "player_type": "OOP"
}
```

### Response
#### Success Response (200)
- **status** (string) - "set_first_iteration_player ok!"

#### Response Example
```json
{
  "status": "set_first_iteration_player ok!"
}
```
```
Tokens:
Raw