Provider dashboards.
Where to click in every outside service.

01Before you click

• Your accounts, your bills. For every service on this page you open your own account, you accept that provider's terms, and you pay that provider for your own usage above any free tier. No account, key or credit is included in the item, and the author is not a party to these accounts.
• Menus move. The click paths are those of each dashboard in October 2026. Providers rename menus from time to time; if a name differs, use the dashboard's search or its help pages, and look for the same words ("API keys", "Ad units", "Service accounts").
• Keys are secrets. Copy a key straight into the console's Set field. Do not paste it into chats, e-mails, support comments or files in the project. The console encrypts it and never shows it again.
• Spending limits first. Where a provider offers a spending limit or a prepaid balance, set it before you paste the key.

02Firebase and Google Cloud

The full Firebase setup (create the project, Blaze, Authentication providers, Firestore, Storage, the service account for the console and the signed-URL permission) is written step by step in Installation, steps 1 to 3. Two more Google Cloud steps that buyers often look for:

1. Budget alertconsole.cloud.google.com/billing → your billing account → Budgets & alerts → Create budget → scope: your project → amount → alert thresholds (for example 50 %, 90 %, 100 %) → Finish. A budget alerts you; it does not stop spending.
2. Functions logsFirebase console → Build → Functions → tab Logs (or Google Cloud console → Logging → Logs Explorer). The backend's log lines carry ids, model and status, never message text.

03AI provider keys

Each key goes into the console field named in the last column, then Save changes and Test connection. A provider you do not use needs no account.

04Google Play Console

Needed to publish on Android and to sell plans, credit packs and Remove ads. Your own developer account (one-time registration fee to Google).

Create the in-app products

1. App firstplay.google.com/console → Create app → name, language, app, free → declarations → Create app. Upload one build (internal testing is enough) that contains the billing library: Play only lets you create products after that. Muse AI's release build contains it.
2. Payments profilePlay Console → Settings → Payments profile must be set up to sell anything.
3. Subscriptions (one per period)Your app → Monetize with Play → Products → Subscriptions → Create subscription → Product ID exactly as in Console → Plans (for example pro_monthly) → name → Create. Inside it → Add base plan → Base plan ID → type Auto-renewing → billing period (Monthly) → Set prices → Save → Activate. Repeat with a new subscription for each period you sell (pro_yearly with a yearly base plan, and so on). Muse AI maps one product id to one period, so keep one base plan per subscription.
4. One-time productsYour app → Monetize with Play → Products → One-time products (older layouts: In-app products) → Create product → Product ID (remove_ads, credits_small, credits_medium, credits_large, or a lifetime plan id) → name, description, price → Save → Activate. Google has no separate "consumable" type: the app buys credit packs as consumables through Google Play Billing, so they can be bought again.
5. TestersPlay Console (all apps) → Settings → License testing → add the Google accounts of your testers, so they can buy without being charged.

Let the backend verify purchases

1. Enable the APIGoogle Cloud console, the project whose service account will verify (your Firebase project) → APIs & Services → Library → "Google Play Android Developer API" → Enable.
2. Choose the service accountBy default the backend uses the Cloud Functions runtime account <project-number>-compute@developer.gserviceaccount.com. Or create a separate one: Google Cloud console → IAM & Admin → Service accounts → Create service account → name → Done (no project roles needed) → open it → Keys → Add key → Create new key → JSON.
3. Invite it in Play ConsolePlay Console → Users and permissions → Invite new users → e-mail address of the service account → tab App permissions → Add app → your app → tick View financial data, orders and cancellation survey responses (the backend reads purchases and order prices; it changes nothing) → Invite user. It can take up to a day before Google accepts calls with it.
4. ConsoleMuse AI console → Store & purchases → Android package name (your application id) and, if you made a separate account, paste the whole JSON into Google Play service account (JSON) → Save changes → Test (it checks the file's shape; nothing is sent).

05App Store Connect

Needed to publish on iOS and to sell. Your own Apple Developer Program membership (yearly fee to Apple).

Create the in-app purchases

1. Agreementsappstoreconnect.apple.com → Business (or Agreements, Tax, and Banking) → the Paid Apps agreement must be Active, with bank and tax details. Without it the app cannot load any product.
2. App recordApps → + → New App → platform iOS, name, language, your bundle id, SKU → Create.
3. SubscriptionsYour app → Monetization → Subscriptions → Create a subscription group (for example "Pro") → in the group Create → Reference name, Product ID exactly as in Console → Plans (for example pro_monthly) → Create → Subscription Duration (1 Week, 1 Month, 1 Year) → Subscription Prices → Add Subscription Price → App Store localization (display name, description) → Review information (a screenshot of the paywall) → Save. Put every period of one plan in the same group so users can switch.
4. One-time purchasesYour app → Monetization → In-App Purchases → + → type Non-Consumable for remove_ads and lifetime plans, Consumable for credits_small, credits_medium, credits_large → Reference name, Product ID → Create → price, localization, review screenshot → Save.
5. First reviewNew in-app purchases are submitted together with an app version the first time: on the version page, section In-App Purchases and Subscriptions, select them before you submit.
6. Sandbox testersUsers and Access → Sandbox (Test Accounts) → + → an e-mail you do not use as an Apple ID → sign in with it on the test device under Settings → App Store → Sandbox Account.

Let the backend verify purchases (App Store Server API key)

1. Generate the keyUsers and Access → Integrations → In-App Purchase → Generate In-App Purchase Key (or +) → name → Generate.
2. Download onceClick Download next to the new key. The .p8 file can be downloaded only once: keep it with your backups.
3. Copy two idsThe Key ID is in the key's row; the Issuer ID is shown at the top of the Integrations page.
4. ConsoleMuse AI console → Store & purchases: iOS bundle id, App Store Connect issuer id, In-app purchase key id, In-app purchase key (.p8 contents) (open the file in a text editor and paste everything including the BEGIN and END lines), App Store environment = Sandbox (TestFlight) while testing, Production when live → Save changes → Test (it checks that the key parses; nothing is sent).

06AdMob

Your own AdMob account; Google pays you under its terms and keeps its share.

1. Add the appadmob.google.com → Apps → Add app → platform Android (or iOS) → "Is the app listed on a supported app store?" No until it is published (link it later) → app name → Add app. Do it once for Android and once for iOS.
2. App IDApps → your app → App settings → copy the App ID (ca-app-pub-…~…). It goes into AndroidManifest.xml / Info.plist and Console → AdMob ids (Ads, step 1).
3. Ad unitsApps → your app → Ad units → Add ad unit → format (Banner, Interstitial, Rewarded, Native advanced, App open) → name → Create ad unit → copy the ad unit ID (ca-app-pub-…/…) → Console → AdMob ids, matching field.
4. Rewarded server-side verification (optional)Apps → your app → Ad units → click the Rewarded unit → Edit ad unit → Advanced settings → pencil next to Server-side verification ("No callback URL provided") → dialog "Set up and verify callback URL" → Enter callback URL: <API_BASE_URL>/v1/rewarded/ssv (for example https://us-central1-<project-id>.cloudfunctions.net/api/v1/rewarded/ssv) → Verify url → Use verified url → Save. Then Console → Ads → Rewarded ads: server-side verification (AdMob SSV) on. Details: Ads → rewarded.
5. Consent messagesPrivacy & messaging → create a European regulations (GDPR) message and, for iOS, an IDFA explainer message → publish. The app shows them through Google's consent SDK (UMP).
6. Revenue reporting (optional)Google Cloud console → APIs & Services → Library → enable "AdMob API" → Credentials → Create credentials → OAuth client ID → then obtain a refresh token with the scope https://www.googleapis.com/auth/admob.readonly → Console → Ad revenue reporting. Publisher id: AdMob → Settings → Account information.

07Unity Ads

Your own Unity account; Unity pays you under its terms.

1. Project and appscloud.unity.com → sign in → create or pick a project (Development → Settings shows the project name and Project ID) → left menu Monetization → Apps → add your Android app and your iOS app to the project.
2. Game IDsMonetization → Apps → click an app → tab Monetization → section Network → Game ID (copy icon). The Android app and the iOS app each have their own → Console → Unity Ads ids → Android game id, iOS game id.
3. Ad unitsMonetization → Placements → copy the ids of the Banner, Interstitial and Rewarded placements for each platform (Unity creates defaults such as Rewarded_Android and Rewarded_iOS; you can add your own) → Console → Unity Ads ids, matching unit fields.

08ironSource LevelPlay

Your own LevelPlay (Unity) account; payouts under its terms.

1. Add the appUnity LevelPlay dashboard (platform.ironsrc.com, also reachable from cloud.unity.com) → Apps → Add app (top right) → platform, store status, name → Add app. Once for Android, once for iOS.
2. App keyIn the Apps list, the app key is the short code under each app's name (with a copy icon) → Console → ironSource LevelPlay ids → Android app key, iOS app key.
3. Ad unitsLeft menu Setup → Ad units → pick the app → create a Rewarded, an Interstitial and a Banner ad unit → copy each Ad unit ID → Console → matching fields. Connect the networks you want to mediate under Setup → Networks.
4. S2S reward callbackLevelPlay offers a server-to-server reward callback (Apps → the app row's ⋯ menu → Set S2S callback, with a callback URL and a private key). Muse AI has no LevelPlay callback endpoint, so do not create one for this app; a callback URL pointing at Muse AI would not be used.