Bots St

bots.st/fanzero

FanZero

Publish and manage game listings with contracts

2324 ms

answered our call

State
Answered
Protocol
MCP 2025-06-18
Tools listed
15
Answered
3 of the last 3 calls

How to reach it

  • MCP, HTTPhttps://fanzero.app/mcp

What it can do

ToolWhat it says it does
add_pactOffers one more revenue-share pact on one of your games. Same rules for every pact: one influencer at a time, for the pact's weeks (2 to 8, 4 if left out) from the first proposed action date, share_pct% of net revenue from every store. Get the terms, length included, from your human.
browse_gamesSearches the public catalog of live games: who is free, top share, studio. Public, no key. free = nobody holds the game right now and it has an open pact; taken_until = when the current holder's window ends (each pact runs its own weeks; for a legacy holder who has not gone live yet, the latest…
check_buildValidates a listing or optional preview. Agents sending html/files need preview_review; static checks do not certify its truth. Saves nothing. Original game links are the default. Optional dry run: send media, platforms/prices or monetization, description and pacts without html/files. A new agent…
close_pactCloses a pact; requests still waiting on it are declined. Running deals keep their terms. No new requests on it; pending requests are declined so influencers can request an open pact. Accepted and running deals keep their terms. Closing a closed pact changes nothing.
confirm_deliveryLegacy contracts only: confirms proof under the older go-live rules. Scheduled pacts need no delivery confirmation. Legacy contracts only. Scheduled pacts (rules_version 3) never need this call. Check the proof link with your human first, then call with human_approved: true (otherwise it fails…
create_studioRegisters the studio once and returns its API key. Refuses an exact duplicate. Call it once per studio, only after asking your human whether they already have a key. An exact duplicate (same name and contact) fails with duplicate_studio, and so does a call made with a working key. Store the key…
get_reviewStatus, next step, check results, critic notes, curator note and log for one of your games. Checks run inside submit_game and update_game, so there is nothing to poll: call this to read the result again or to see the curator's decision (check back later, a day is a good interval). game_id takes…
list_my_gamesYour games, who holds each one, and every pact request with its proposed actions, dates and next step. Per game: status, pacts, holder and pending request count. For rules_version 3, each claim includes proposed actions with scheduled_at and the window starting on the earliest action; pitched is…
publish_gamePublish the original game through media and platform links in one operation. A preview only if representative, sandbox-tested and better than the original. Safe retries never expose credentials. One-operation flow for the original game: complete media, platform links, per-platform prices/model…
read_listing_guidelinesList the original game with media and platform links. Optional preview quality, pact rules and review. Read before submitting: original game links are the default, while agent previews require an explicit quality assessment. Also resource fanzero://guidelines.
respond_to_claimApproves or declines a proposed action schedule. Legacy proof responses remain supported. accept: approves the influencer action plan once. For rules_version 3, sharing runs for the pact's weeks from the earliest proposed action, never from approval; late approval keeps the same dates. No proof or…
submit_gameLegacy key flow: list the original game through media and platform links. Agent html/files require preview_review. Prefer publish_game for one-operation submission. List the original game with media and platform links by default. Every new html/files upload needs preview_review with all flags true…
submit_settlementAfter a pact window: declares each platform's net revenue, with its own report. The influencer accepts or disputes. After a scheduled pact's window: one line per key in claim.distribution with the net revenue that platform pays or will pay for the window's sales, in-game purchases and ads (after…
update_gameChange the listing or offers; remove_preview retires a demo, keeping the original links and pact windows. Agent uploads need preview_review. Automated checks read the code without playing it. Original game links remain the default. remove_preview:true retires an optional demo, keeping the listing…
whoamiWhich studio the key belongs to, with game and pact-request counts. Without a key, how to get one. Optionally check an existing studio key. With an unknown key it fails with invalid_api_key (the key shown masked).

In its maker's words

Publish game listings with Codex or Claude. Media, prices and direct links to the original game.

Website
fanzero.app/agents
Publisher
fanzero.app
Listed from
the official MCP Registry as app.fanzero/fanzero
Version
0.5.0, updated 13 Oct 2026
Kinds of work
Shops and payments, Documents and files, Browser and automation

The domain it lives on

fanzero.app
registered 11 Oct 2026 (1 month ago), at Squarespace Domains II LLC, its home page is a working site

From our own crawl of domain names: registry records and the home page as our crawler last saw it.

Every call we made

WhenWhat happenedTime
Answered2324 ms
Answered2592 ms
Answered1075 ms

Next door

Is this your bot? Claim its address to add a verified badge and keep the listing current.