app.fanzero/fanzero
6 changes recorded. MCP Harbor re-reads this listing from the official registry every six hours and asks the live server what it exposes, and keeps what changed between one look and the next.
− - [Pact rules](https://fanzero.app/docs/pact-rules.md): one influencer per game, dated content actions, one studio acceptance, 28-day window from the earliest scheduled action, 0 < share_pct <= 50+ - [Pact rules](https://fanzero.app/docs/pact-rules.md): one influencer per game, dated content actions, one studio acceptance, a window of the pact's weeks (2 to 8 weeks, 4 by default) from the earliest scheduled action, 0 < share_pct <= 50
− > Publish and distribute games with coding agents. FanZero connects studios with content creators through revenue-share pacts and scheduled content. A human curator approves every game. MCP endpoint: https://fanzero.app/mcp (Streamable HTTP, stateless, POST only).− Auth: `Authorization: Bearer <studio API key>`, or `api_key` on every tool call. No key needed for `read_listing_guidelines`, `check_build`, `whoami`, `create_studio`, `publish_game`, `browse_games`. Pacts are revenue commitments: obtain approval of the exact terms before publication or accepting a creator. Reuse existing explicit approval. Only legacy claims use delivery confirmation.− - [Distribute a game with Codex or Claude Code](https://fanzero.app/docs/distribute-game-with-ai-agents): complete listings, optional playable versions and launch visibility through creators− - [Pact rules](https://fanzero.app/docs/pact-rules.md): one creator per game, dated content actions, one studio acceptance, 28-day window from the earliest scheduled action, 0 < share_pct <= 50− - [How pacts work, for creators](https://fanzero.app/docs/how-pacts-work)+ > Publish and distribute games with coding agents. FanZero connects studios with influencers through revenue-share pacts and scheduled content. A human curator approves every game. MCP endpoint: https://fanzero.app/mcp (Streamable HTTP, stateless, POST only).+ Auth: `Authorization: Bearer <studio API key>`, or `api_key` on every tool call. No key needed for `read_listing_guidelines`, `check_build`, `whoami`, `create_studio`, `publish_game`, `browse_games`. Pacts are revenue commitments: obtain approval of the exact terms before publication or accepting an influencer. Reuse existing explicit approval. Only legacy claims use delivery confirmation.+ - [Distribute a game with Codex or Claude Code](https://fanzero.app/docs/distribute-game-with-ai-agents): complete listings, optional playable versions and launch visibility through influencers+ - [Pact rules](https://fanzero.app/docs/pact-rules.md): one influencer per game, dated content actions, one studio acceptance, 28-day window from the earliest scheduled action, 0 < share_pct <= 50+ - [How pacts work, for influencers](https://fanzero.app/docs/how-pacts-work)
− Auth: `Authorization: Bearer <studio API key>`, or `api_key` on every tool call. No key needed for `read_listing_guidelines`, `check_build`, `whoami`, `create_studio`, `browse_games`. Pacts are revenue commitments: ask your human before publishing and accepting a request. Only legacy claims use delivery confirmation.− - [Distribute a game with Codex or Claude Code](https://fanzero.app/docs/distribute-game-with-ai-agents): supported builds, publishing and launch visibility through creators+ Auth: `Authorization: Bearer <studio API key>`, or `api_key` on every tool call. No key needed for `read_listing_guidelines`, `check_build`, `whoami`, `create_studio`, `publish_game`, `browse_games`. Pacts are revenue commitments: obtain approval of the exact terms before publication or accepting a creator. Reuse existing explicit approval. Only legacy claims use delivery confirmation.+ - [Distribute a game with Codex or Claude Code](https://fanzero.app/docs/distribute-game-with-ai-agents): complete listings, optional playable versions and launch visibility through creators
We can't find the internet
Attempting to reconnect
Something went wrong!
Attempting to reconnect