zrovio-venues
Polymarket + Kalshi venue adapters used by Zrovio bots.
Install
From the monorepo (editable):
pip install -e packages/zrovio-venues
# optional: Polymarket live order signing
pip install -e "packages/zrovio-venues[poly]"
Usage
from zrovio_venues.clock import now_utc
from zrovio_venues.polymarket import fetch_15m_markets, PolyMarketFeed
from zrovio_venues.kalshi import KalshiClient
from zrovio_venues.polymarket_orders import PolyOrderClient
from zrovio_venues.kalshi_orders import KalshiOrderClient
poly_mkts = fetch_15m_markets(["btc", "eth"])
kalshi = KalshiClient.from_env()
kal_mkts = kalshi.fetch_15m_markets(["btc", "eth"])
poly_orders = PolyOrderClient.from_env(dry_run=True)
kal_orders = KalshiOrderClient.from_env(dry_run=True)
5-minute Polymarket discovery lives in zrovio_venues.poly_5m.
Fallback when the package is unavailable
Bots in this repo still keep the flat root modules (clock.py, polymarket_client.py, …).
If zrovio-venues is missing from the environment (pip uninstall, broken wheel, etc.),
prefer importing the package and falling back to the local copies:
try:
from zrovio_venues.clock import now_utc
from zrovio_venues.polymarket import fetch_15m_markets, PolyMarketFeed
from zrovio_venues.kalshi import KalshiClient
from zrovio_venues.polymarket_orders import PolyOrderClient
from zrovio_venues.kalshi_orders import KalshiOrderClient
except ImportError:
from clock import now_utc
from polymarket_client import fetch_15m_markets, PolyMarketFeed
from kalshi_client import KalshiClient
from polymarket_orders import PolyOrderClient
from kalshi_orders import KalshiOrderClient
Existing app code is not switched yet — migrate callers gradually.
Tests
cd packages/zrovio-venues
pip install -e ".[dev]"
pytest
Metadata
Release files for zrovio-venues 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| zrovio_venues-0.1.0.tar.gz | 28.5 kB | Without provenance | Details for zrovio_venues-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| zrovio_venues-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for zrovio_venues-0.1.0-py3-none-any.whl |
Total release size: 58.5 kB
Release files / zrovio_venues-0.1.0.tar.gz
| Download URL | zrovio_venues-0.1.0.tar.gz |
|---|---|
| Size | 28.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d576d55f0b0f366707fb9747c2d73fb6f46f54fde6a665aa7f2c63b0fe1e2017
|
|
BLAKE2b-256 checksum How to use checksums |
4d67065e1259ea2019e61d9df3d43216b23c991469faf656f8ca35c8dcfec0ee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.15
|
Release files / zrovio_venues-0.1.0-py3-none-any.whl
| Download URL | zrovio_venues-0.1.0-py3-none-any.whl |
|---|---|
| Size | 30.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c89d6b5b34903dcd4b1b2acf8e5a4090427ad4ac6b1569cff0c3983e372ef387
|
|
BLAKE2b-256 checksum How to use checksums |
58efb6d398818a8f2aaa6fe13e97d6424022c9a5d0fa85550cf16fdcf0570313
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.15
|
Security for zrovio-venues 0.1.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
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.