Attract ModeDeveloper workspace ↗

Attract Mode / Developers

Give your game a page players can trust.

Submit a browser game, verify control of an existing listing, manage approved pages and understand the review process for links, media and launch domains.

How do I list or claim a browser game?

Sign in to the developer workspace and submit your playable browser-game URL, or use Claim on an existing game or studio page. A new listing receives editorial review. A claim requires proof that you control the creator’s established identity before scoped page access is granted.

A public editorial listing can exist before its developer claims it. The listing itself is not an ownership verification. Claiming a page does not automatically connect player accounts, approve payments or make the game a commercial partner.

Submit a browser game

In the developer workspace, choose List a game. Enter the game and studio names, playable URL, a concrete description, genres, devices, controls, account or access requirements and an official source URL. Include original screenshot URLs, their credit and your permission to publish them. Use notes for multiplayer room instructions, release history and the URL of an existing studio page.

Use complete public HTTPS links without credentials, secret-bearing query values, fragments or custom ports. Put screenshot or press-kit URLs one per line, up to eight. Select whether you own the media, have permission, or are using a supplied press kit; include the source and credit.

Save a draft if you are missing information. Submit for review when the required fields are complete. A public contact is optional and must be a contact you want published. Your signed-in account email is not a request to publish your address.

Catalog selection is editorial. The team checks the build and sources. Submission does not guarantee a listing or a daily feature. A listing does not imply a commercial partnership or account integration.

One studio, several games

A studio page can collect multiple games. Developer and publisher credits can be different. Each approved claim is scoped to a particular page and role. Control of one game does not give you control of another developer’s game or an unrelated studio.

If a page already exists, use its claim option while signed into your Attract Mode account. Select the studio you represent. Never send passwords, private keys or identity documents as ownership evidence.

Prove control of the established identity

The team checks the creator’s established public identity independently of your claim. The claim flow supplies an expiring challenge bound to your account, studio and requested page. Available proof routes include a post from the established X account, a fixed website proof or a DNS record.

Follow the exact challenge shown in your workspace and submit its evidence for review. An operator checks the evidence and conflicts before granting scoped access. A matching display name or a paid social badge is not enough. Proof is one-use, and verification can be revoked if authority changes or evidence fails.

Make changes with a record

After verification, submit copy changes with source evidence in the workspace. The review history keeps decisions and versions. An independent operator reviews proposed copy. Approved copy is queued for the next site publication, so approval does not mean the live page has already changed.

You can also propose links, media and structured corrections through the workspace. These receive editorial review and a publication record. New launch domains require fresh domain proof and checking of the proposed site. A proposed URL does not automatically change the live launch link.

Use factual descriptions and media you have the right to publish. Include supporting sources for changes. Reviewers can reject a proposal or ask for clarification. Rollbacks preserve history rather than erasing earlier decisions.

What verification does not grant

Page verification does not grant billing access, OAuth client administration, access to other studios or control of player data. Account integration requires separate approval. Payments and revenue sharing require separate commercial terms.

Claim evidence and review records belong in the private workspace, not a public game description. Public pages show approved editorial information. Contact hello@attractmode.io if a listing’s ownership or published information is wrong.

What happens if my studio has more than one game?

Reuse your existing studio identity and connect each game to the correct developer or publisher credit. Each game keeps its own listing, playable URL, device information and editorial history. Do not create a separate studio for every title unless they are actually different organizations.

A claim is granted for a specific page and role. Check the access shown in your workspace before proposing changes. If another game from your studio is missing, submit it and include the existing studio page so the team can connect the records.

Follow your request

Draft: saved privately, not sent for review. Submitted: waiting for the team to review. Changes requested: read the review note, edit the same request and submit it again. Approved: the request passed review, but delivery still needs to happen. Declined: read the explanation before deciding what to do next. Fulfilled: the team has recorded the actual outcome. Check the outcome link and review note.

Approval alone does not put a listing online, create OAuth credentials or schedule testers. The recorded outcome explains what was delivered. Keep each request focused on one game and one goal. You can send separate listing, sign-in and playtest requests for the same game.

Submit without the interactive workspace

Cannot use the interactive workspace? Download the text or JSON request template, fill in the relevant section and email it to hello@attractmode.io. Keep fields you cannot verify marked unknown and explain them in notes. Do not invent screenshots, player counts or ownership evidence. Email is a review route, not automatic publication; the team will reply about missing information and next steps.

The templates work without an account. A coding agent can prepare a file or email draft for you, but there is no anonymous submission API and the documentation MCP cannot send it. Ask the agent to show you the completed request before you send it. Never put passwords, OAuth secrets, player data or payment details in the request or a public GitHub issue.

Example source files

Open developer workspace ↗

Download request template (text) ↗

Download request template (JSON) ↗