App contest — how to enter, and how it shapes the build

Higgsfield runs an app contest with a $100,000 total prize pool. If the user wants to enter (or asks what the contest is), this is the reference. higgsfield website contest <website_id> is the command that submits an app.

Prizes, dates, and rules below are the current contest as of 2026-07-08. The contest is admin-curated and recurs — treat specifics (amounts, dates) as this round's, and the live details are on https://higgsfield.ai/supercomputer/apps?tab=prizes. The mechanics (auto-publish on entry, social-link submission, judging on real usage) are stable.

What it is

How entering shapes what you build (bake this in from the start)

Even before the user mentions the contest, these are just good type: "app" practice — and they're the eligibility bar and the scoring rubric:

Entering — higgsfield website contest (it publishes for you)

An app not yet on the community feed is published automatically by the entry — no separate higgsfield website publish needed. The flow when the user asks to enter:

  1. Make it listable. The app needs a live production deploy (higgsfield website deploy <website_id>) — an undeployed app is rejected ("deploy first"). And because the entry lists the app on the feed, the page metadata (cover + og_title, see references/app-flow.md) must be filled BEFORE entering — the auto-published listing renders from it, and an empty og_title is invisible on the feed. Deploy after changing metadata.
  2. Get the social link(s). The contest requires the app posted to at least one public social platform (Instagram, TikTok, YouTube, or X) with a link back to the Higgsfield app and the #HiggsfieldApp hashtag. Pass one or more --url flags, each a link to that public post — any other host is rejected. The user posts it themselves; ask for the URL(s) if you don't have them, and remind them to include the app link + #HiggsfieldApp in the post.
  3. Submit. Run higgsfield website contest <website_id> with the --url flag(s). There's a single active contest, so no contest id. One entry per app — re-running OVERWRITES the urls (use it to fix or add links, it doesn't create a second entry).
# after `higgsfield website deploy <website_id>` has shipped (metadata filled)
higgsfield website contest <website_id> \
  --url https://x.com/<user>/status/…   # ≥1 public post, #HiggsfieldApp

If the user asks to enter but hasn't posted anywhere yet, get the app deployed with real metadata, then tell them the one thing only they can do — post it publicly with the app link and #HiggsfieldApp — and enter as soon as they give you the URL.

Eligibility (relay if asked)

18+, a Higgsfield account, free to enter. No third-party IP. Prizes paid within 30 days of the announcement after eligibility verification; winners cover their own taxes. Void where prohibited. Jury decisions are final. Full official rules are on the prizes page.