Skip to main content

openwop-client 2.x — Python SDK for OpenWOP v2 hosts

openwop is an open, wire-level protocol for multi-agent workflow orchestration. This package is the reference Python client for the v2 major (spec/v2/, RFC 0168 §D): synchronous, zero runtime deps, one typed method per operation in spec/v2/path-manifest.json (55 operations), typed dataclasses, and pure-stdlib SSE iterators for the run and host event channels.

pip install "openwop-client>=2,<3"   # 2.4.0 — v2-only; the 1.x client stays on openwop-client<2

Spec: github.com/openwop/openwop · Corpus tag: see CORPUS_TAG · Mirrors: api/v2/openapi.yaml, schemas/v2/, spec/v2/errors.json · Sibling: the TypeScript client at sdk/typescript-v2/

The 1.x package (sdk/python/) is untouched and keeps publishing for v1 hosts. This is a v2-ONLY client: it never sends a /v1/… path. The import name stays openwop_client.

What is different from 1.x (RFC 0172 / 0171 / 0173)

1.x 2.x
/v1/runs, /v1/agents, … Bare origin, unversioned path keys: /runs, /agents, …
Negotiation by protocolVersion OpenWOP-Version: <major>.0 on every request (ctor major=2); 406 protocol_version_unsupported when the host does not list the major.
dedup=True → X-Dedup dedup=True → OpenWOP-Dedup: enforce.
runs_poll_events(last_sequence=) runs_poll_events(after_sequence=); the response is the closed { runId, events, lastSequence, status, isTerminal }.
Capabilities with supported sub-dataclasses The closed v2 root: protocolVersions + preferredVersion required, families: dict[str, CapabilityRecord] (status / since / until / witness / facets). CAPABILITY_FAMILY_KEYS is generated from the schema.
HTTP_ERROR_CODES hand-kept ERROR_CODES / ErrorCode (108) generated from spec/v2/errors.json, plus ERROR_CODE_HTTP_STATUS, RETRIABLE_ERROR_CODES, is_vendor_error_code.
*_workspace_file (4), runs_debug_bundle, RegistryClient Removed — not v2 operations (the registry is resolved through .well-known/openwop-registry.json endpoints).
quote(run_id, safe='') → t%2Fr Tenant-bound ids (run_id, subscription_id) go on the wire projected: acme/r-9f3c → acme~2Fr-9f3c (identity.md §5 "Wire form"). project_id / unproject_id are exported; unproject_id reads both the projected and the percent form a link may carry.
— runs_compensation, runs_effects, host_effect_seams (RFC 0173), host_events (the hostEvents SSE channel).
Webhook openwop-Webhook-* names, v1=<hex> OpenWOP-* only (X-openwop-* accepted through the overlap); sha256=<hex>; an unrecognized OpenWOP-Signature-Algorithm is rejected.

Quickstart

from openwop_client import CreateRunRequest, OpenwopClient, RunConfigurable, WopError, is_terminal_run_status

client = OpenwopClient(base_url="https://api.example.com", api_key="hk_test_abc123")  # major=2 → OpenWOP-Version: 2.0

caps = client.discovery_capabilities()            # the closed v2 root
print(caps.preferredVersion, caps.protocolVersions, "webhooks" in caps.families)

resp = client.runs_create(
    CreateRunRequest(workflowId="my-workflow", inputs={"q": "hello"}, configurable=RunConfigurable(run={"runTimeoutMs": 60_000})),
    idempotency_key="idem-1",
    dedup=True,
)

for event in client.runs_events(resp.runId, stream_mode=("updates", "messages")):
    print(event.sequence, event.type)

cursor = None
while True:                                       # long-poll fallback
    page = client.runs_poll_events(resp.runId, after_sequence=cursor)
    cursor = page.lastSequence
    if page.isTerminal:
        break

comp = client.runs_compensation(resp.runId)       # None when `compensation` is unadvertised

try:
    client.runs_get("tenant/does-not-exist")
except WopError as err:
    if err.envelope and err.envelope.error == "not_found":
        ...

Webhook receivers:

from openwop_client import read_webhook_headers, verify_webhook_signature

read = read_webhook_headers(request.headers)
outcome = verify_webhook_signature(secret, read.signature, read.timestamp, raw_body, algorithm_header=read.algorithm) if read else None

Generated surface

src/openwop_client/_generated.py is produced by scripts/generate.py from the vendored spec/v2/errors.json and schemas/v2/capabilities.schema.json; python3 scripts/generate.py --check (run by scripts/sdks-check.sh) fails when it drifts.

Development

python3 scripts/generate.py --check
ruff check .
PYTHONPATH=src python3 -m unittest discover -s tests

Metadata

Release files for openwop-client 2.4.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 openwop-client 2.4.0
File Size Uploaded
openwop_client-2.4.0.tar.gz 64.5 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for openwop-client 2.4.0
File Interpreter ABI Platform
openwop_client-2.4.0-py3-none-any.whl Python 3 none any Details

Total release size: 119.7 kB

Release files / openwop_client-2.4.0.tar.gz

Download URL openwop_client-2.4.0.tar.gz
Size 64.5 kB
Tags Source
SHA-256 checksum
How to use checksums
9c72354e66ba64cccbd71a27955dc99dbd37663bf125c43c0aa95e88a58c97c9
BLAKE2b-256 checksum
How to use checksums
7c2266ff739e98b365d8d8c3cc54721d61743b3943640dd15485f4d35d2f0a5d
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 Sep 28, 2026.

Transparency log

Release files / openwop_client-2.4.0-py3-none-any.whl

Download URL openwop_client-2.4.0-py3-none-any.whl
Size 55.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4f1ecc52579b25ac4dc5d396dac67e2d0a002d1e6a7834f957d486609647e083
BLAKE2b-256 checksum
How to use checksums
7fa80d5f913673aabce8ec6335fddcae558cb0c677df5408c258bbdba0d6b6b1
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 Sep 28, 2026.

Transparency log

Release history Release notifications | RSS feed

2.6.0

2 release files

2.5.0

2 release files

This release

2.4.0 This release

2 release files

2.3.0

2 release files

2.2.0

2 release files

2.1.0

2 release files

2.0.0

2 release files

1.8.0

2 release files

1.7.0

2 release files

1.6.0

2 release files

1.5.0

2 release files

1.4.1

2 release files

1.4.0

2 release files

1.3.0

2 release files

1.1.7

2 release files

1.1.5

2 release files

1.1.1

2 release files

1.1.0

2 release files

1.0.0

2 release files

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