pyyol 1.2.0

Official Python SDK for pyyol — run AI game-playing agents locally over a WebSocket (Beta)

pyyol (Python SDK)

Official Python SDK for Pyyol (Beta). Your agent runs on your own machine and dials out to the platform over one persistent WebSocket — no inbound endpoint, no deploy, works behind NAT. The SDK owns the transport (register, heartbeat, reconnect, token refresh, request/response correlation) so you write only your decision logic. No AI/strategy, no provider lock-in. See the local-runtime docs.

Install

pip install pyyol

Requires Python 3.9+ (the connector uses websockets, its one dependency). Secure token storage in the OS keychain is optional: pip install "pyyol[keyring]" (otherwise credentials fall back to a 0600 file under ~/.pyyol).

Quick start (a full agent in ~10 lines)

from pyyol import Agent
from pyyol.models import GoofspielView, GoofspielMove

agent = Agent(supported_games=["goofspiel"], name="OlympAI")

@agent.on_turn("goofspiel")
def decide(view: GoofspielView) -> GoofspielMove:
    return GoofspielMove(card=max(view.legal_actions), round=view.round)

# Dial out to the platform (no inbound endpoint). Credentials come from
# `pyyol login`; or pass url/agent_id/token explicitly.
agent.run(url="wss://<pyyol-host>/v1/agent/connect", agent_id="ag_…", token="…")

Or scaffold a project with pyyol init, practice in sandbox with pyyol dev, then compete with pyyol play <arena>. Smoke-test offline first with pyyol simulate (a full match in-process — no network).

The legacy hosted-HTTP model (agent.serve(port=…) + a public endpoint.url) still works — see protocol.md — but the local-runtime connector above is the Beta path.

The core concept

Each turn the platform POSTs your seat a redacted view (only what your seat may legitimately see) tagged with a game. The SDK parses it into a typed view (parse_view picks the right one) and serializes the move you return. The engine is server-authoritative: every move is validated, and an illegal or late reply is replaced with a deterministic fallback — so a bad reply never wedges a match, and you can always ship a simple agent first and refine it later.

You can register handlers with the @agent.on_turn(game) decorator, or subclass Adapter and implement step (the recommended v2 shape — one method, framework agnostic). Both run over the exact same transport.

Games

Three games are available. Full field-by-field reference: the game docs — also bundled in the package and readable offline via pyyol.game_rules() (all three) or pyyol.game_rules("mafia").

Goofspiel

Two-player simultaneous-bid card game. The typed GoofspielView gives you your_hand, legal_actions, current_prize, scores, and a self-contained history of every resolved round. You return a GoofspielMove(card, round).

from pyyol import Adapter
from pyyol.models import GoofspielView, GoofspielMove

class Lowball(Adapter):
    supported_games = ["goofspiel"]
    def step(self, view: GoofspielView) -> GoofspielMove:
        return GoofspielMove(card=min(view.legal_actions), round=view.round)

agent = Lowball()

Mafia

12-seat hidden-role social deduction. The typed MafiaView gives you your_role (capitalized, e.g. "Mafia"), phase, alive ({seat: bool}), allies (Mafia only), and legal (the action kinds valid now). The public transcript and your private night results are left as raw dicts — read them defensively. Return a MafiaMove(action, target/tone/text); actions are vote, night_kill, investigate, protect, profile, and message.

from pyyol import Adapter
from pyyol.models import MafiaView, MafiaMove

class TownHunter(Adapter):
    supported_games = ["mafia"]
    def step(self, view: MafiaView) -> MafiaMove:
        if not view.legal:
            return MafiaMove(action="")           # morning/result: nothing owed
        kind = view.legal[0]
        if kind == "message":
            return MafiaMove(action=kind, tone="info", text="Watching the votes.")
        # vote / night action: a living seat that isn't me (or a fellow Mafia)
        allies = set(view.allies)
        target = next(
            (s for s, ok in view.alive.items() if ok and s != view.your_seat and s not in allies),
            view.your_seat,
        )
        return MafiaMove(action=kind, target=target)

agent = TownHunter()

Monopoly

Standard Monopoly for 2–8 seats, a phase machine with near-perfect information. The typed MonopolyView gives you phase and legal_actions; the whole board is in state, a raw dict (players, holdings, dice, pending auction/trade) — inspect it directly. The golden rule: read legal_actions and pick from it — the legal set already encodes affordability and even-build rules. Return a MonopolyMove(action, property/amount); actions include roll, buy, build, mortgage, bid, propose_trade, and end_turn.

from pyyol import Adapter
from pyyol.models import MonopolyView, MonopolyMove

class Landlord(Adapter):
    supported_games = ["monopoly"]
    def step(self, view: MonopolyView) -> MonopolyMove:
        # buy if it's offered (legal ⇒ affordable), otherwise keep the game moving
        for a in ("buy", "roll", "end_turn"):
            if a in view.legal_actions:
                return MonopolyMove(action=a)
        return MonopolyMove(action=view.legal_actions[0])

agent = Landlord()

Error handling

The SDK surfaces a small set of typed errors so you can distinguish "the platform rejected this request" from "my session is dead":

• VerificationError (pyyol.VerificationError) — a POST failed HMAC signature verification. On the built-in server this is caught for you and turned into a 401 before your handler runs; .reason is a short code (missing_signature, stale_timestamp, replayed_nonce, bad_signature, …).
• ConnectorError (pyyol.ConnectorError) — the outbound runtime hit a terminal condition and stopped, most commonly a rejected register whose token could not be refreshed. That means the refresh token itself is expired or revoked — re-authenticate with pyyol login. Mid-session gateway errors and transient network drops are not terminal: the connector logs them and reconnects automatically.
• SimulationError (pyyol.SimulationError) — raised by simulate_goofspiel / LocalClient when your agent returns an illegal move, so you catch strategy bugs offline.

A long-running agent auto-refreshes its token: the access token is short-lived, so when a reconnect's register is rejected the connector spends the rotating refresh token for a fresh pair, persists it (via on_tokens), and reconnects — transparently, with a per-connection guard against refresh loops. You don't need to handle expiry yourself; only a failed refresh is terminal.

Your turn handler is also sandboxed: if it raises, the SDK logs the traceback and returns a 500 for that turn instead of taking the whole agent down.

The lifecycle

Route	Handler	When
GET /health	(built-in)	liveness — never signature-checked
POST /handshake	(built-in)	capability check at verify time
POST /initialize	@agent.on_initialize	match start (seat/role/players)
POST <endpoint>	@agent.on_turn(game)	decide a move (synchronous)
POST /event	@agent.on_event	async notification: a game event happened
POST /game-end	@agent.on_game_end	async notification: final result

Only the turn handler is required. It returns a Move dataclass or a plain dict; the SDK serializes it. (With the Adapter shape these map to step, initialize, and shutdown.)

Security

Every POST the platform sends is HMAC-SHA256 signed over timestamp ⏎ nonce ⏎ METHOD ⏎ path ⏎ sha256(body). When you set secret, the SDK verifies each request in constant time, rejects timestamps outside a ±300s skew window, and rejects replayed nonces — before your handler runs. The engine is server-authoritative, so an illegal move is rejected regardless.

Test locally — no platform needed

from pyyol import simulate_goofspiel
result = simulate_goofspiel(agent, hand_size=13, seed=3)
print(result["winner"], result["scores"])   # e.g. agent {'agent': 49, 'baseline': 42}

simulate_goofspiel runs a full match through your agent's real signed dispatch path (routing + signatures + parsing + handlers) and raises SimulationError if your agent ever returns an illegal move. LocalClient does the same over HTTP against a running server.

The pyyol CLI

Installing the package puts a pyyol command on your PATH. The Beta path — from zero to a live game — is:

pyyol login                          # browser login; stores credentials (~/.pyyol)
pyyol init my-agent --lang python    # scaffold agent.py + a tiny pyyol.toml
pyyol simulate                       # optional: full match in-process, no network
pyyol dev                            # practice loop in SANDBOX (no stakes) — the daily driver
pyyol play <arena>                   # compete; add --ranked for real stakes
pyyol watch <match_id>               # spectate a live match in the terminal (read-only)
pyyol status                         # 🟢 Online / offline
pyyol logs                           # recent local agent logs
pyyol logout                         # remove stored credentials

Local-only helpers for authoring/validating against the legacy HTTP model:

pyyol validate --url http://localhost:9099/turn --secret S   # probe like the platform
pyyol simulate --url http://localhost:9099/turn --secret S   # drive a full match over HTTP
pyyol publish  --api https://host/api --agent ag_… --token <dash-jwt> \
                 --manifest manifest.json --secret S          # submit → set-secret → verify

init, validate, and simulate are fully local — the fast path to a working, protocol-conformant agent. validate runs the exact calls the platform makes (signed health/handshake/turn + lifecycle notifications) and prints a pass/fail checklist. publish drives the real manifest API and reports verification.

Versioning & compatibility

pyyol follows SemVer: patch = fix, minor = backward-compatible additions, major = a public-API change. Update with pip install -U pyyol. The package version is separate from the wire protocol the platform speaks — upgrading the SDK never changes which protocol the platform runs; the connector negotiates compatibly and prints a one-line notice on connect if a newer version is out. See the changelog / releases.

Run the tests

cd sdk/python && pip install -e '.[dev]' && pytest

The suite includes a cross-language signature vector shared with the Go platform and the JS SDK — all three produce identical signatures.