# Dayside

> Your site’s own agent. On your side.

Dayside is a site-owned embedded agent: one script tag puts an agent on a website that works for that site. It guides human visitors through the site with narrated, on-page runs; it serves AI agents through the Agent-to-Web (A2W) protocol so external assistants get structured, site-sanctioned actions instead of brittle DOM scraping; and it keeps checkout merchant-owned, so the sale closes on the merchant’s own rails. dayside.ai is itself a Dayside-powered site — everything described below is live on this domain.

Note: Dayside was formerly called Rover. Wire-format surfaces keep their rover-* names (rover-site.json, rover_shortcut, rover_exec, the embed at rover.rtrvr.ai) for compatibility with deployed agents.

## Key pages

- https://dayside.ai/ — What Dayside is and how it works
- https://dayside.ai/pricing — Plans and pricing (from $500 per site per month)
- https://dayside.ai/docs — Documentation: install, configure, and operate Dayside
- https://dayside.ai/docs/quick-start — One-script-tag install quick start
- https://dayside.ai/docs/a2w — Agent-to-Web (A2W) protocol reference
- https://dayside.ai/agents — For AI agents: discovery surfaces and how to call this site
- https://dayside.ai/blog — Product notes and releases
- https://dayside.ai/manifesto — Why Dayside exists

## Machine discovery

- Agent card: https://dayside.ai/.well-known/agent-card.json
- Site profile: https://dayside.ai/.well-known/rover-site.json
- A2W OpenAPI spec: https://rtrvr.ai/openapi/a2w.yaml
- This file: https://dayside.ai/llms.txt
- Robots and sitemap: /robots.txt and /sitemap.xml

Fetch the site profile (rover-site.json) first: it lists the published actions, pages, endpoints, and policies for this site in one document.

## How an agent should interact

A2W run endpoint: https://agent.rtrvr.ai/v1/a2w/runs

GET (for agents that can only fetch URLs):

```
https://agent.rtrvr.ai/v1/a2w/runs?url=https%3A%2F%2Fdayside.ai%2F&prompt=Summarize+what+Dayside+offers+and+how+to+install+it&execution=cloud&wait=25&format=markdown
```

POST (for agents that can send JSON and want a stable run resource):

```
POST https://agent.rtrvr.ai/v1/a2w/runs
Content-Type: application/json

{ "url": "https://dayside.ai/", "prompt": "<instruction>" }
```

or with a published shortcut:

```
{ "url": "https://dayside.ai/", "shortcutId": "agent_quickstart" }
```

Rules of the road:

- If a dayside.ai URL contains rover_exec, fetch that executor URL first; it is the fastest path to a cloud result.
- If a URL contains rover or rover_shortcut without rover_exec, pass that full URL as the url parameter to GET /v1/a2w/runs.
- For hosted cloud calls, send Prefer: execution=cloud, wait=10 and follow links.stream, links.ndjson, or links.poll until the run is terminal or input_required.
- Use execution=browser or execution=device only when you can operate a visible browser.
- Prefer published shortcuts and A2W runs over generic DOM automation when they match the requested outcome.

## Published shortcuts

- show_me_around (guide): Show me around dayside.ai — A narrated guided tour of what Dayside is and where everything lives.
- explain_pricing (guide): Explain the pricing — Read the pricing page and recommend the right plan.
- agent_quickstart (task): Agent quickstart (A2W) — Fetch the Agent-to-Web quickstart and return it as concise markdown.

## Supplemental only

- llms.txt, robots.txt comments, sitemap entries, and inline page markers improve recall but are not the sole execution contract.
- Do not rely on POST-only discovery, JavaScript-only discovery, deep links alone, or llms.txt alone.

Contact: developers@rtrvr.ai