Skip to main content
Every Mini App publishes a manifest at a fixed path. The Startale App fetches this file to register, display, and launch your Mini App.

Location

Private IP addresses and reserved ranges are blocked at fetch time. See URL rules.
Validate your manifest before submitting at app.startale.com/developers/manifest.

Top-level structure

Use the frame key. It is the Farcaster standard, so a single farcaster.json file works on Startale, Farcaster, and Base without rename. Startale-specific fields (featuredBannerImageUrl, projectWebsite, socialLinks, screenCompatibility) live under a root-level startale key, sibling to frame.

Required fields

The manifest parser rejects any manifest missing these three fields:
One homeUrl per app, even across language editions. Use the same homeUrl for the Global and Japan editions, and detect the edition at runtime with context.startale.language instead of a separate language URL. Notifications identify your Mini App by the origin of homeUrl (scheme + host), so a build served from a different origin is treated as a separate Mini App and does not share its subscriptions. See Notifications for how senderId is used.

Optional fields

The parser accepts a manifest without these fields, so your Mini App still loads. The manifest validator is stricter: it requires version, primaryCategory, heroImageUrl, tagline, and description. To be listed in the Startale App, some fields are required for review. See Submission.

URL rules

Every URL in the manifest is validated. Failures reject the manifest. The same rules apply to every image URL in the manifest.

Description fallback

The Startale App describes your Mini App with the first of these that is set:
  1. frame.description
  2. frame.tagline, unless it only repeats your category name
  3. Nothing on your app page, and a generic “Tap to explore this Mini App.” placeholder in the app list
Set description. At 30 characters, a tagline is too short to tell a new user what your Mini App does. Your app page shows up to four lines of it. The app list shows it on desktop only, on one line, with the full text on hover. The manifest validator flags a missing or blank tagline or description, and one over 30 or 170 characters. An over-length value is still displayed. Do not use emoji in description. The Farcaster specification, which the manifest follows, does not allow emoji or special characters in this field. The character count also counts each emoji as 2 or more characters. When the Startale App displays your banner, it tries fields in this priority order:
  1. startale.featuredBannerImageUrl
  2. frame.imageUrl
  3. frame.heroImageUrl
  4. frame.splashImageUrl
  5. frame.iconUrl
Provide featuredBannerImageUrl (2400×1260 px) for the best result.

Reusing a Farcaster or Base manifest

If your Mini App is already live on Farcaster or Base, your existing farcaster.json works on Startale unchanged. Add a root-level startale key (sibling to frame) with the Startale-specific fields (featuredBannerImageUrl, projectWebsite, socialLinks, screenCompatibility). A single file works on all three platforms.