HELIX Docs
Platform API

Content rating & maturity

Every item and world declares a maturity rating. The platform gates discovery by it, and creators attest to it at publish time.

HELIX is an adults-allowed platform with higher creative freedom than most, which only works with a clear maturity model. Every and every world carries a content rating, declared by its creator and enforced platform-wide for discovery.

The ratings

Prop

Type

Two fields, two jobs

contentRating is what the creator declares. contentRatingStatus is where moderation stands on that declaration: pending_review → approved / flagged / rejected. Discovery uses the declared rating; enforcement can tighten it after review.

Declaring a rating (publish-time attestation)

A creator must attest to the rating when publishing — it isn't inferred. The items publish pipeline rejects a publish that doesn't carry the attestation, and records when + what was declared (attestation version ugc-maturity-self-rating-v1). Any value other than the four ratings is a 400.

Prop

Type

How it gates

  • Discovery — listings are filtered to the viewer's maturity cap: their account setting (default everyone; anonymous visitors are everyone). A maxContentMaturity query parameter can only narrow that cap, never widen it.
  • The platform ceiling is mature. No age verification exists on the platform yet, so no viewer's cap can reach adult: adult-rated content is listed to nobody except its own creator. The ceiling rises when real age verification ships.
  • Worlds inherit a floor — when a world is published, its rating must be at least the highest rating declared by the Vault assets it uses. A lower declaration is raised, and the assets that caused it are reported. Undeclared (unrated) assets never raise the floor.

When in doubt, rate up

Creator content is reviewed and can be reported by the community. Repeated intentional misrating can flag or permanently ban the creator account. Rate to the strongest content actually present.

In the SDK

Ratings are platform-enforced — worlds don't compute them. An item's contentRating and contentRatingStatus are part of its schema; discovery filtering happens on the server, not in world code.

Reference

On this page