Skip to main content

Screen Stocks Python Bridge

The screenstocks-bridge package is a Python client for the local API exposed by the Screen Stocks Bridge BepInEx plugin. It requires the plugin to be installed in the game and the game to be running. The package itself does not install or contact the game backend; it connects to the plugin on loopback.

Install

python -m pip install screenstocks-bridge

Install the matching BepInEx plugin from the GitHub releases, then launch Screen Stocks. The default bridge address is 127.0.0.1:48721. The plugin port can be changed under [Bridge] as Port in BepInEx/config/screenstocks.bridge.cfg; close and relaunch the game after editing it. Pass the same value to BridgeClient(port=...) when it differs from the default. The example scripts also read SCREENSTOCKS_PORT. Read the token from BepInEx/config/screenstocks.bridge.cfg or the BepInEx log.

Connect

from screenstocks_bridge import BridgeClient

with BridgeClient(token="YOUR_TOKEN") as bridge:
    state = bridge.snapshot()
    print(state["ready"], state["cash"])
    print(bridge.upgrades())
    recent = bridge.transaction_history(filter="both", limit=100)
    print(recent["entries"])

The client supports state reads, leaderboard requests, transaction-history reads, activity reads and subscriptions, explicit single-stock activity-focus controls, trades, upgrade purchases, and auto-action controls. Request a game-supported leaderboard with leaderboard("current"), leaderboard("all_time"), leaderboard("ipo"), leaderboard("current_top"), leaderboard("clan_net_worth"), or leaderboard("clan_player_share"). Leaderboard requests use the game's in-process client, with one live request every 30 seconds; identical requests are served from a 30-second cache. Activity focus can be set with set_human_activity_focus(stock_id) and cleared with clear_human_activity_focus(); the in-game overlay shows the active stock, and bridge-driven focus changes have a five-second minimum. See the bridge usage guide for the full API and its online behavior. Activity history reads page through only the samples the game currently retains in memory; they do not fetch older history from the game's server, and the bridge makes no guarantee about the retained history's total depth or time span.

Use transaction_history(filter="both", limit=100) to read recent transactions. Filters are manual, both, and auto_action. The game screen can seed the in-memory cache; successful screen requests also start the bridge cooldown. The BepInEx cache lifetime and request interval can be increased from their 60-second and 30-second minimums, as described in the usage guide.

Use offline_summary() to read the latest welcome-back summary captured during the current game session. The plugin captures it in memory before automatically closing the screen; set AutoCloseOfflineSummary = false in the BepInEx config to leave the screen open while retaining API access.

Metadata

Release files for screenstocks-bridge 0.6.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for screenstocks-bridge 0.6.0
File Size Uploaded Provenance Actions
screenstocks_bridge-0.6.0.tar.gz 10.5 kB With provenance Details for screenstocks_bridge-0.6.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for screenstocks-bridge 0.6.0
File Interpreter ABI Platform Actions
screenstocks_bridge-0.6.0-py3-none-any.whl Python 3 none any Details for screenstocks_bridge-0.6.0-py3-none-any.whl

Total release size: 20.7 kB

Release files / screenstocks_bridge-0.6.0.tar.gz

Download URL screenstocks_bridge-0.6.0.tar.gz
Size 10.5 kB
Tags Source
SHA-256 checksum
How to use checksums
6a3eb8e4669667c84f31d85239c0f0d1821253c81c12dd8e16dbf7cfddcf2ddc
BLAKE2b-256 checksum
How to use checksums
a4604e1f85078ed700bf7d5b532eba666cd32e30a9cf8b72be437986a13cc3c9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 5, 2026.

Transparency log

Release files / screenstocks_bridge-0.6.0-py3-none-any.whl

Download URL screenstocks_bridge-0.6.0-py3-none-any.whl
Size 10.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a28df48cf256d4fd0232d2d0e8875cd56cf3992c719642e909f8d8079209bec0
BLAKE2b-256 checksum
How to use checksums
ea13ef62e19f9380108ebb4a9a10bcbe5fa03711ab70371533558f1c9c1511a1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 5, 2026.

Transparency log

Security for screenstocks-bridge 0.6.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for screenstocks_bridge-0.6.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 5, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page