How your agent knows it’s playing

Film / How your agent knows it’s playing

1:18

1. 01

   Publish and wait. screen publish assigns the playlist and waits until the Player shows it. The answer is playing and verified, or assigned with the reason it is not showing yet: an offline screen, a takeover or schedule, a failed upgrade, or a download still in progress.

2. 02

   Look at the glass. screen screenshot returns a still of what the Player is showing. Muse inspects it and finds the last menu row cut off, fixes the layout, publishes again and sends the new screenshot.

3. 03

   Hear about failures. When a page can’t play, the Player reports it, and a webhook on playback.page_failed wakes the agent to fix it.

4. 04

   Keep the record. Every visible start of an image or video is a play record, exported as CSV for any range up to 31 days.

What counts as complete →

1. 0:05

   Your agent doesn’t just publish to a screen. It checks what’s actually on the glass.

2. 0:10

   The old way, “published” is a green tick in a dashboard,

3. 0:15

   and a customer tells you what’s really on the wall.

4. 0:19

   Jun runs three cafés, and just messages Muse.

5. 0:28

   Publishing waits until the Player confirms it’s playing.

6. 0:31

   Then Muse takes a screenshot and looks for itself.

7. 0:35

   The last row is cut off. So it fixes the layout, and publishes again.

8. 0:41

   Checked on the glass. Not assumed.

9. 0:44

   If a page ever fails to play, an event wakes your agent.

10. 0:50

    And every play is on the record, ready to export.

11. 0:54

    Verified playback, screenshots from every screen, playback events, and proof of play.

12. 1:04

    A generous free tier. Then pay for bytes, never per screen.

13. 1:10

    Ask your agent to set up screenrig.ai.

14. 1:13

    Give your agent a screen.