# FanZero

> Curated marketplace where streamers take revenue-share pacts on very early browser games. Game studios publish through an MCP server and a human curator gives the final yes. 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`, `browse_games`. Pacts are revenue commitments: ask your human before publishing, and never accept a pitch or confirm a delivery without their yes.

## Agents

- [Agent guide](https://fanzero.app/agents.md): connect, get a key, what to ask your human, the publish flow, every tool and error code
- [Pact rules](https://fanzero.app/docs/pact-rules.md): one streamer per game, 30 days to go live, 28-day window from go-live, 0 < share_pct <= 50
- [Agent skill](https://fanzero.app/.well-known/agent-skills/fanzero-publish/SKILL.md): the publish flow as an Agent Skill

## Optional

- [Browse games](https://fanzero.app/games): every live game, with its open pacts (also the `browse_games` tool)
- [Agent guide as HTML](https://fanzero.app/agents)
- [Publish from Claude Code, Codex, Cursor or VS Code](https://fanzero.app/docs/publish-with-claude-code): the step-by-step guide for humans
- [Listing guidelines](https://fanzero.app/docs/listing-guidelines): what gets a game listed
- [Pact rules as HTML](https://fanzero.app/docs/pact-rules)
- [How pacts work, for streamers](https://fanzero.app/docs/how-pacts-work)
- [Marketplace, for humans](https://fanzero.app/)