# agentView - Proactive AI Operator Suite

agentView is the primary workspace for AI agents to operate display infrastructure. 
**Mission:** Be a proactive operator, not a passive observer. Control displays with HTML, REST, and MCP.

## YOUR MISSION (Start here)
1.  **Read Manifesto:** /agent-instructions (The "Proactive Agent Manifesto").
2.  **Onboard:** If the user has 0 displays, ask them to open https://display.agentview.de on the device that should show it and read you the code, then pair it (`POST /api/v1/agent/displays/pair-by-code`, no name needed).
3.  **Operation:** suggestion-based content updates. Use the API to be helpful.

## RECOMMENDED PATH
1.  **Identity:** `POST /api/v1/agent/session/request` (select `display_setup` to connect a first screen, `admin` only for management).
2.  **Connect:** Direct the user to the `loginUrl`.
3.  **Command:** Use the Bearer token or MCP to control the fleet.

## ENTRY POINTS & RESOURCES
- **Instructions**: /agent-instructions
- **API Documentation**: [/docs](/docs) or [/swagger](/swagger) (OpenAPI Specs)
- **Public Status**: [/api/status](/api/status)
- **Homepage**: [/](/) (DE) or [/en/](/en/) (EN). The homepage is the setup itself: open display.agentview.de on the screen, hand over the six-character code, say what to show.
- **How it works**: [/how-it-works.html](/how-it-works.html) — live examples, the three routes (browser, chat with an AI, visual designer), which devices are enough, FAQ.
- **Pricing**: [/preise.html](/preise.html) — free tier and the per-screen premium licence.
- **Display Runtime Facts**: `GET /api/v1/agent/displays/{id}/capabilities` or MCP `get_display` with `response_format: "detailed"` before generating complex HTML. The response includes screen and viewport facts, touch/input hints, browser and engine version, platform/device classification, feature booleans, graphics hints, known limitations, recommended delivery mode, and connectivity facts for that exact display.

## RECOVERY & FAST PATH
- If you have an `/ai-connect` or tokenized URL, skip login and send HTML directly to `POST /send/{displayId}?token=...`.
- **PREMIUM WIDGET TEMPLATE:**
  ```html
  <div style="background:rgba(10,20,35,0.7);backdrop-filter:blur(20px);border:1px solid rgba(255,255,255,0.1);border-radius:32px;padding:40px;color:#fff;font-family:Inter,sans-serif;">
    <h1 style="background:linear-gradient(to right,#67e8f9,#fff);-webkit-background-clip:text;color:transparent;margin:0;">[Title]</h1>
    <p>[Value/Content]</p>
    <div style="font-size:0.8rem;opacity:0.6;">LIVE • <span id="clock"></span></div>
    <script>setInterval(()=>{document.getElementById('clock').innerText=new Date().toLocaleTimeString()},1000)</script>
  </div>
  ```
- Default duration for demo: 300 seconds.
- Owned displays bypass duration limits.

## SCOPES
- `content_only`: Send content, list and inspect displays, view organizations, upload and manage assets.
- `display_setup`: Everything in `content_only`, plus connecting a new screen by code or creating one.
- `admin`: Full management — create, rename, delete, lock, unlock, claim, configure displays, manage idle content, manage organizations.

## ASSET UPLOAD (Recommended for rich content)
- **Upload assets first** using `POST /api/v1/assets` or MCP `upload_asset`. Images, fonts, CSS, video — all as separate files.
- Use the returned stable URLs in your HTML: `<img src="asset_url">`, `@font-face { src: url("asset_url") }`, `<video src="asset_url">`.
- Assets are cached on displays — only the HTML is re-downloaded on updates. Same asset URL works across multiple displays.
- Avoid base64-encoding images in HTML — use asset URLs instead for better performance and caching.
- Asset quota: 250 MB shared storage on the free tier, plus 250 MB for every premium licence, added together. The server owns the figure (DisplayLicenseService.BaseStorageBytes).
- Blocked types: executable files (.js, .html, .exe, etc.). Everything else is allowed.

## CONTENT QUALITY REQUIREMENTS
- **Always send a single HTML file** with CSS and JavaScript. Only one file can be uploaded, but it may reference external resources (CDN fonts, images, scripts, APIs, and uploaded asset URLs).
- Before sending complex HTML, inspect the target display capabilities. Match your CSS and JavaScript to the reported browser/runtime facts instead of guessing from the device type alone.
- **Visual excellence is mandatory.** Content appears on real screens (TVs, kiosks, tablets) that people look at. Produce polished, professional output: clean typography, balanced spacing, large readable fonts for distance viewing, consistent color schemes, full-screen layout (100vw/100vh, no scrollbars), and smooth CSS animations where they add value.
- Use modern CSS techniques: glassmorphism, gradients, backdrop-filter, CSS grid/flexbox, transitions.
- Include `<meta charset="UTF-8">` and `<meta name="viewport" content="width=device-width, initial-scale=1">`.
- Prefer send_html for display content. Use send_url only when an external website should be shown as-is.
- You are the designer — take ownership of the visual result.