Battling.Live

What Battling.Live is

Battling.Live is an audience-directed arena rather than a chat-queue clip channel. Anyone can watch the free HLS feed without creating a fighter. Optional: build a fighter, then let the crowd vote or choose a battlefield for an upcoming match; after matchmaking, a generated fight scene is produced and appended to the broadcast.

The product mixes live generation with UI states that can look like replay. We treat the underlying HLS playlist as the live signal: if the playlist advances, the channel is on air even when the player briefly shows REPLAY chrome. That is different from Infinite Slop’s public status JSON, but it is still an external check rather than an operator claim.

It matters as another shape of audience-directed live video: not “vote the next fifteen seconds of random scenes,” but “steer a fight arena that keeps a continuous playlist running.” Claims about models, pricing beyond free spectating, or always-on uptime should stay unverified until sourced.

How the experience flows

1. Open battling.live — the arena stream plays as HLS without an account.
2. Optionally create a fighter; spectating does not require one.
3. The crowd chooses the battlefield / match setup for an upcoming fight.
4. After matching, a generated battle segment is produced and joins the live playlist (UI may flash REPLAY between segments).

Status, as checked

Website reachability and broadcast status are recorded separately; an HTTP 200 never counts as live. Expired checks degrade to Stale, detector failures to Unverified. Methodology.

Why we track it

Shows audience direction applied to a fight-arena format with a continuously open HLS playlist, not just a one-shot fight generator.

Models behind the output

Not publicly disclosed.

Timeline

No dated updates recorded yet.

Where each fact comes from

Editorial review: 8 Sep 2026. Fields marked “Officially stated” come from the operator; “Observed” fields were checked directly by AI Stream Radar at the time shown. Quoted text is marked and attributed to its source.

1. Battling.Live — The arena is hungry
   Officially statedBattling.LiveObserved 2026-09-08 01:00 UTCConfidence: high

   “Create your fighter, enter the arena, and let the crowd choose where an upcoming battle unfolds.”

   Homepage title (Battling.Live — The arena is hungry), meta description, and OG image (https://battling.live/og.png) establish the product name and audience-directed arena format. Operator contact and company name come from Privacy/Terms (We Know How to Do It LTD; [email protected]). Media type recorded as video from the continuous HLS broadcast; audio generation is not stated. Convex deployment hushed-vole-443 and PostHog are noted as infra only, not as a video model credit. No public model attribution found.

   namewebsite_urlorganization_idplatform_kindmedia_typestreams.main.watch_url
2. Direct observation of Battling.Live public HLS playlist and spectator UX
   Observed by AI Stream RadarAI Stream RadarObserved 2026-09-08 01:05 UTCConfidence: high

   Observed 2026-09-08. Public HLS playlist at /api/broadcast/playlist.m3u8 returned HTTP 200, MEDIA-SEQUENCE advanced between reads (e.g. 1894415193→1894415194), and the playlist had no ENDLIST — continuous live signal. Spectator watch loads without an account (access recorded as free). About copy states battle footage is generated when fighters are matched and the crowd chooses where an upcoming battle unfolds; audience can vote/choose fighting style — interaction recorded as audience_voting plus free_form_prompt for optional fighter creation at /create (login required; create path references 18+ and 100 credits; do not invent further pricing). Continuity recorded as prompt_linked_clips: generated fight segments join the continuous playlist after matchmaking rather than a single stateful world. Player REPLAY chrome is UI filler between segments, not evidence the playlist closed. Age restriction recorded as yes from the create-fighter 18+ requirement. Launch date unknown (no sourced launch announcement).

   interaction_modescontinuity_typeaccess_typeage_restricted

Also in these categories