# Listing and publishing You list your app yourself, in the [listing wizard](https://portal.cherry.fun/dashboard/launch). Each step saves as you go, so you can stop and come back from **Mini apps** in your project. ## The wizard | Step | You provide | | --- | --- | | Your app | Name, a one-line pitch, a category, an icon and a cover image. No address yet: you add it under Integrate once the app is deployed | | Who runs it | Company or individual, legal name, country, your email and Telegram, and optionally your X and the project's X | | Where it runs | Chains, countries you do not serve, age rating | | How your app makes money | Sales, Commission (with the share you keep), Other (described in your words, the share optional) or Free | | Terms | Cherry's standard Terms of Service and Privacy Policy in one tick, or links to your own with the [Terms checklist](https://portal.cherry.fun/docs/mini-apps/terms-checklist.md), and the Developer Agreement for this app, which includes the [Mini App Policy](https://portal.cherry.fun/docs/mini-apps/policy.md), accepted with your wallet | | Integrate | The generated brief for your AI agent, the framing header and the domain proof file; then, once deployed, where your app runs (its address and up to three test addresses) with your private test room, the automated checks and the automated test | | Go live | Which address users get, what is still missing and where the automated test stands, then **Publish to Cherry** | ## Test addresses and your test room Most apps run in more than one place: staging, a preview deploy, then production. Under **Integrate**, after the brief for your agent, **Where your app runs** asks for the address your app runs on once you deploy it; staging is fine. That becomes its main address. Add up to three test addresses beside it, each with a name such as Staging. Pick an address and press **Open in test room**. Cherry opens your private test room, a private group in Cherry with your app inside, on that address. Only your team is in it: whoever opens it from the portal joins it, and users never see it. Switch the address and the room follows, for everyone in it. Use it before you go live and after: the next release is tried on staging in the same room before it reaches users. The test room stays private. You cannot make it public in Cherry; opening your app to everyone is **Go live**. The selected address is also what the automated checks and the automated test run on. On a test address the domain proof is shown but not required, and a test run is shown but not kept: publishing needs a passing test on the address users get. On **Go live**, **Users get** shows which address your listing opens. Pick another one and it becomes your app's address; the old one stays as a test address named Previous. Then run the automated test on it. Test addresses are never part of your listing: they need no domain proof, no other app is refused because of them, and only your test room opens them. ## Automated checks Run them under **Integrate** after you deploy. Publishing runs them again. | Check | Passes when | | --- | --- | | Reachable | Your URL answers 200 over https, without a login wall | | Framing | Your `Content-Security-Policy` `frame-ancestors` includes Cherry, and no `X-Frame-Options` blocks it | | Origin | The bridge trusts exactly your URL's origin, no wildcards | | Terms of Service | The link is public and names your operator | | Privacy Policy | The link is public and names your operator | ## Automated test The checks above read your app from the outside. The automated test, also under **Integrate**, opens it the way a user does: in a real browser, on a phone-sized screen, inside an iframe on `https://chat.cherry.fun`, signed in as a Cherry test user. Your own headers and the SDK's origin check run for real, and third-party cookies are blocked, as on a phone. It takes about a minute. Cherry plays its own part exactly as the app sees it in production: it sends `cherry:init` with a real launch token and the launch context until your app answers `cherry:ready`, connects the test wallet when asked, and declines every signature request as if the user closed the prompt. Nothing is clicked. Publishing needs a passing test **on your current URL**. Change the URL and you run it again. Warnings never block publishing. | Check | Fails or warns | Passes when | | --- | --- | --- | | `frame_loads` Loads inside Cherry | Fails | No `frame-ancestors` or `X-Frame-Options` block, no HTTP error, no redirect to another origin, and the page is ready within 10 seconds | | `handshake` Answers the handshake | Fails | Your app answers `cherry:ready` within 5 seconds of loading | | `signed_in` Signs the user in by itself | Fails | Within 10 seconds of the handshake the page shows the test user's name or the first 4 characters of their wallet, or a request carrying the launch token gets a 2xx | | `no_connect_prompt` No connect button or signature request | Fails | For 15 seconds there is no visible connect-wallet button or link (in any language) and no signature request | | `backend_verifies_token` Backend verifies the token | Fails | Runs when your app sends the launch token to a server of its own (the test detects that; otherwise it is skipped). The test opens the app again twice: with a token signed by Cherry but for another app, and with an expired one. Both times your backend answers 401 or 403, or the user is not signed in | | Domain proof | Fails | `https:///.well-known/cherry-app.json` answers 200 with your app ID, on the tested URL's origin. See [Domain proof](#domain-proof) | | `console_errors` Console errors | Warns | Nothing is logged as an error and nothing throws | | `time_to_ready` Time to ready | Warns | `cherry:ready` arrives within 8 seconds of Cherry opening the app | | `external_payment_links` External checkouts | Warns | No links or navigation to external checkouts (Stripe, PayPal, Paddle, Lemon Squeezy, Gumroad, Coinbase Commerce, card on-ramps) | Each result says what happened and what to change, with a screenshot and the console lines or requests that matter. Requests to Cherry's own API (`https://chat.cherry.fun/api/miniapp/...`) count for sign-in but never as your backend. If you said the app has no backend, `backend_verifies_token` is skipped. The test needs no setup from you beyond what the [Quickstart](https://portal.cherry.fun/docs/mini-apps/quickstart.md) covers: the SDK at your listed URL, sign-in from the launch token, the framing header, token verification on your backend with `audience` set to your app ID, and the domain proof file. [Troubleshooting](https://portal.cherry.fun/docs/mini-apps/troubleshooting.md) maps each failure to its fix. ## Domain proof Every origin your app uses, the app URL's origin and each allowed origin, serves a file that names your app: ```http GET https://app.example.com/.well-known/cherry-app.json ``` ```json { "appId": "YOUR_APP_ID" } ``` `appId` is the mini app ID the portal shows for your app. Serve the file as JSON, over https, with a 200. The automated test checks it on whatever URL you test and shows the result as **Domain proof**. Publishing needs the proof on every origin. One origin belongs to one listed app. Publishing is refused when another listed app already uses one of your origins, with one exception: the domain's owner, whose file proves the domain, takes the origin over from a listing that never proved it, and that listing is taken off the marketplace. Apps listed before this rule keep working without the file until they change their URL. ## Statuses | Status | Meaning | | --- | --- | | Not listed | Still in the wizard | | Listed | In the marketplace and open to everyone | | Paused | Stopped by Cherry, automatically or by the team (see [Pauses](#pauses)); your app does not open and its transactions are refused | | Delisted | Removed from the marketplace, by you or by Cherry, or because a domain's owner proved one of your origins (see [Domain proof](#domain-proof)) | You can unpublish at any time from the wizard's last step, and publish again whenever you are ready. To delete an app, use **Delete app** at the top of the wizard. A listed or paused app is unpublished first. Deleting removes the app from your portal and it no longer opens anywhere; bills already issued for it stay due. ## Pauses Cherry may pause an app, automatically or by hand, for example when its outflow is far above its usual level, when it keeps sending refused transactions, or after several user reports in a day. Cherry decides when to pause, and has no duty to watch apps or to pause any of them. When it pauses yours, you get an email and a Telegram message with the reason. Pauses for a technical reason lift once the cause is fixed. The [Mini App Policy](https://portal.cherry.fun/docs/mini-apps/policy.md#support-and-enforcement) lists what else Cherry may do. ## Changing the operator The Developer Agreement is accepted per app, for the operator named in the listing. If you change the operator's legal name, entity type or country after accepting, accept the agreement again before the app goes live. ## Verified Verified apps get higher limits and the Verified check. Verification is a short identity check of the project owner, done once in the portal. It is not a review of your app; see [Verification](https://portal.cherry.fun/docs/mini-apps/verification.md). ## What you may list Every app follows the [Mini App Policy](https://portal.cherry.fun/docs/mini-apps/policy.md). Gambling and games of chance with stakes are listed in the iGaming category, by an identity-checked operator, under its rules. Prediction markets, token launches and regulated financial services are open only to licensed Partner apps, under a written agreement with Cherry.