Send the URL of a web page. A browser on our servers opens it, captures the picture and the sound, and streams it live to YouTube, Facebook, Twitch or your own server. Nothing to capture or encode on your side.
The page runs in a real browser on our servers, so its video, animations, live data and sound all go out. The picture quality, the destinations and the length are settings your code sends with the request.
The URL of a page you host. A video, an animation, a live chart, a game viewers play in it. Any page a browser can open.
The stream carries the page's own audio: a video playing on it, music, a voice your app plays. No separate audio feed to send.
YouTube, Facebook, Twitch or your own server (custom RTMP). One capture goes to several destinations at the same time.
Set the resolution, the frame rate and the bitrate for each stream. 30 frames a second by default, 60 on request.
A stream runs for the length you set, or with no end until you stop it. Your code starts and stops each one.
If the page or the browser crashes, our servers reload it on their own. Nobody has to be watching it.
Four things a team streams from a page it already has, instead of building capture and encoding of its own.
Your web app renders the show: video, graphics, a name banner, live data. The API streams that page.
Election results, match scores, an auction, a charity counter. The page updates itself, and viewers watch it change on YouTube or Twitch.
Your users press Go live in your app. Your server sends the API their page and their destination, and their stream starts.
A page that changes its own content, streamed with no end date. Viewers see each change the page makes, as it happens.
Your code sends the page's address and the destinations. Our servers open the page and start the broadcast.
One request with the URL of your page, the destinations it streams to, and the length of the stream.
A browser on our servers loads it, and the capture and the encoding start. Viewers see the page as it runs, with its sound.
The stream ends when the length you set runs out, or when your code stops it. Set no length, and it runs until you stop it, up to your plan's maximum stream length.
No. The LiveReacting API controls streams you build in the LiveReacting studio. It creates a project, fills its playlist and goes live. This API takes a web page you host and streams it as it is.
This API has no self-serve key and no public docs. Fill in the request form at the foot of this page, and our team replies by email with the details and the pricing.
Anything a Chrome browser shows: video, animations, live data, a game with viewer input, and the sound the page plays. The page has to open without a sign-in step.
YouTube, Facebook, Twitch or any server that accepts an RTMP feed, and several of them from one capture. SRT and HLS delivery come by request, on a custom plan, with SCTE-35 ad markers inside the HLS stream.
You set the resolution, the frame rate and the bitrate for each stream. The default is 30 frames a second. 60 frames a second and resolutions up to 4K are available on request.
If the page or the browser crashes, our servers reload it on their own. The status page shows the current state of the platform, and you can subscribe to updates there.
Tell us what page you want to stream, where to, and how many hours a month you expect. You get the details and the pricing by email.
Prefer to email us directly? [email protected]
Your AI then builds, schedules and starts your live streams for you.
The LiveReacting plugin opens in ChatGPT. Click Install plugin, then sign in to your LiveReacting account.
Open in ChatGPTCopy this URL. In Claude, open Customize, Connectors, Add custom connector, paste it, then sign in to your LiveReacting account.
https://mcp.livereacting.com/mcp
Copy the setup message and paste it into your agent. The agent sets up the connection for you.
Included in every paid plan. Full setup guide