# Built for agents, not bolted on

> Canonical HTML: https://screenrig.ai/videos/compare/

One ask, three ways to run it: screenRIG, a signage dashboard with an agent add-on, and building it yourself. A two-minute film.

<a id="watch"></a>

## Watch

- [Built for agents, not bolted on, 2:01 (MP4, 1080p)](https://screenrig.ai/videos/media/compare-1080.mp4)
- [Built for agents, not bolted on, 2:01 (MP4, 720p)](https://screenrig.ai/videos/media/compare-720.mp4)
- [English captions (WebVTT)](https://screenrig.ai/videos/media/compare.en.vtt)

Wrenfield Bakery, its twelve shops, the menu and every number are sample data, and the dashboard in the add-on lane is generic. The side-by-sides are on the [Compare page](https://screenrig.ai/compare.md).

<a id="chapters"></a>

## Chapters

One ask goes to the same agent three ways. Building it yourself sinks before it starts; the other two run the same job side by side, and a row of hands counts every step that comes back to you.

- **0:00** One ask
- **0:21** The first step
- **0:33** Published or playing
- **0:45** When a screen drops
- **1:10** Building it yourself
- **1:26** Scorecard

<a id="transcript"></a>

## Transcript

The narration, as spoken. The captions carry the same lines.

- **0:08** One ask. Three ways to run it.
- **0:12** screenRIG is built for your agent to run, start to finish.
- **0:17** Beside it, a signage dashboard with an agent add-on.
- **0:21** Here, the agent sets itself up. At the screen, you just read it the code.
- **0:26** There, the add-on needs you first: sign in, make a key, register the screen.
- **0:33** And “published” isn't the same as playing.
- **0:37** screenRIG waits until it's on the screen. Then your agent sends a screenshot from the glass.
- **0:45** A month later: twelve shops, and a new ask.
- **0:51** When a screen drops, the add-on's error is written for a person. It comes back to you.
- **0:56** screenRIG tells the agent what failed, and what to do next.
- **1:01** So when Ashgrove is back, it finishes the job and sends proof.
- **1:11** And building it yourself? A screen needs more than a Player.
- **1:15** Ten native Players. Pairing, caching, transcoding, updates, proof of play, app hosting, events.
- **1:24** You could run your own mail server, too.
- **1:26** An add-on puts your agent in front of a product built for people.
- **1:31** screenRIG was built for the agent. Author, deploy, verify and recover.
- **1:47** A generous free tier. Then pay for bytes, never per screen.
- **1:53** Ask your agent to set up screenrig.ai.
- **1:56** Give your agent a screen.

<a id="next-steps"></a>

## See the whole comparison

Side by side: the agent add-on, building it yourself and screenRIG. Then five questions to ask of the signage system you have.

- [See the comparison](https://screenrig.ai/compare/)
- [All videos](https://screenrig.ai/videos/)