Implementing OpenWOP
Four ways in. Pick yours.
Four entry points cover every shape of OpenWOP work. Pick the role that matches what you're building — each card links to the role-specific landing with the specs, schemas, and conformance scenarios that role actually touches.
- Workflow authors You're wiring durable multi-agent runs into a product and calling a compliant host over REST + SSE.
- Host implementers You're implementing the OpenWOP wire surface against your own runtime (or one your customers picked).
- Pack authors You're publishing reusable workflow components — node packs, workflow-chain packs, or agent definitions — to a registry that hosts can consume.
- Production evaluators You're evaluating OpenWOP as a substrate for a production workflow.
Not sure which one you are?
- 01If you're calling somebody else's hostworkflow author
- 02If you're answering somebody else's callhost implementer
- 03If you're shipping reusable nodes for either of the above to consumepack author
- 04If you're choosing which of the above to commit toproduction evaluator
Every role touches
- The wire contract
/spec/v2/prose specs + REST reference +schemas/JSON Schema corpus. - Conformance
@openwop/openwop-conformanceplus the live leaderboard. - RFCsThe in-flight protocol evolution channel; each major stays additive-only per
COMPATIBILITY.md. - SDKsTypeScript on npm, Python on PyPI, Go module — all in
openwop/openwop-sdks.