Developer ecosystem programs
PokerWorks will grow the developer ecosystem in stages:
- maintained recipes and public-clean examples;
- developer community and support surfaces;
- approved directories and programs;
- marketplace only after demand, review, support, billing, and takedown machinery exist.
Directories are discovery surfaces. They do not grant extra API access. A listed recipe, overlay, bot, coach, streamer, room, or integration still uses the underlying admitted contract: Calculation API, Management API, Webhooks, runtime/read companions, or a later certified Game Server API / Table Protocol.
What can come first
- recipe gallery;
- public-clean examples;
- developer community hub;
- streamer and overlay discovery once public-safe read rules are satisfied;
- approved integration examples once review and support ownership exist.
Marketplace, revenue-share, embedded third-party apps, certified bot listings, custom clients, and bulk private data programs remain reserved until their approval, certification, data-use, support, and integrity rules are admitted.
Listing requirements
Every public listing family needs a listing owner, support path, brand/data-use compliance, review cadence, removal rights, takedown process, and clear statement of what the listing does or does not certify.
Listings must not imply unsupported endorsement, app safety, player eligibility, prize legality, bot fairness, coaching quality, or Table Protocol access.
Canonical policy
The full policy lives in
docs/architecture/developer-ecosystem-directories-and-approved-programs.md.