# Rover Production > Structured Rover entrypoints for Rover Production. Prefer the published shortcuts and explicit tools over raw DOM automation whenever they match the user's goal. Prefer Rover shortcuts, explicit site tools, and A2W runs over raw DOM automation when they match the requested outcome. ## Act on this site (A2W) - [Primary A2W run endpoint](https://agent.rtrvr.ai/v2/a2w/runs): POST for structured arguments, identity, auth, policy, payment, subject data, or artifacts - [A2W GET for URL-fetch chatbots](https://agent.rtrvr.ai/v2/a2w/runs?url=&prompt=): compact one-request form - [A2W workflow endpoint](https://agent.rtrvr.ai/v2/a2w/workflows): multi-step runs - [A2W OpenAPI spec](https://rtrvr.ai/openapi/a2w.yaml): full REST contract Use exactly one selector: prompt, shortcutId, or playbookId. A linked selector may also supply engagementKind. GET defaults to cloud execution, a 25-second wait, and Markdown. wait accepts 0-55 seconds (higher values are clamped to 55); runs that outlive the window return status: running plus a poll URL. Use POST whenever identity, auth, policy, payment, subject data, or artifacts are needed. Never place secrets, customer context, or subject identifiers in browser or GET URLs. ## Published skills - [setup_rover: Set up Rover](https://agent.rtrvr.ai/v2/a2w/runs?url=https%3A%2F%2Frtrvr.ai%2F&shortcutId=setup_rover) [shortcut] - Set up Rover. Rover is live on my domain, the first visitor journey works, and I know the best next customization. When to use: Use this when the user wants this exact site outcome and you want a stable path that avoids brittle DOM guessing. Why use this path: Rover shortcuts are explicit site-owned entrypoints with structured A2W run progress and cleaner recovery than generic DOM automation. - [find_plan: Find the right plan](https://agent.rtrvr.ai/v2/a2w/runs?url=https%3A%2F%2Frtrvr.ai%2F&shortcutId=find_plan) [shortcut] - Find the right plan. Compare the relevant plans and recommend the best fit. When to use: Use this when the user wants this exact site outcome and you want a stable path that avoids brittle DOM guessing. Why use this path: Rover shortcuts are explicit site-owned entrypoints with structured A2W run progress and cleaner recovery than generic DOM automation. - [fix_rover_install: Fix my Rover install](https://agent.rtrvr.ai/v2/a2w/runs?url=https%3A%2F%2Frtrvr.ai%2F&shortcutId=fix_rover_install) [shortcut] - Fix my Rover install. Diagnose, resolve, and verify a Rover installation problem. When to use: Use this when the user wants this exact site outcome and you want a stable path that avoids brittle DOM guessing. Why use this path: Rover shortcuts are explicit site-owned entrypoints with structured A2W run progress and cleaner recovery than generic DOM automation. ## Pages - [home](https://rtrvr.ai/): Set up Rover, Find the right plan, Fix my Rover install ## Discovery - [Agent capability card](https://rtrvr.ai/.well-known/agent-card.json): A2A card with skills and interfaces - [Rover site profile](https://rtrvr.ai/.well-known/rover-site.json): full site profile with actions, pages, and policies - [OpenAPI](https://rtrvr.ai/openapi/a2w.yaml): A2W REST contract ## Content - [Full docs corpus](https://rtrvr.ai/llms-full.txt): every product doc in one markdown file, built for LLM ingestion - [Docs](https://rtrvr.ai/docs): rtrvr.ai extension, cloud, API, CLI, and MCP documentation - [Rover docs](https://rtrvr.ai/rover/docs): install and integrate Rover, the embeddable site agent - [Blog](https://rtrvr.ai/blog): product launches, benchmarks, and deep dives ([RSS](https://rtrvr.ai/blog/rss.xml)) - [Rover blog](https://rtrvr.ai/rover/blog): research and field notes on agents and the web ([RSS](https://rtrvr.ai/rover/blog/rss.xml)) - [Sitemap](https://rtrvr.ai/sitemap.xml) ## Recent posts - [The Self-Improving Action Layer: What We're Building Over the Next Year](https://rtrvr.ai/blog/self-improving-action-layer-roadmap) - [Turn event attendees into pipeline: enrichment that runs in your browser](https://rtrvr.ai/blog/agentic-dataset-enrichment-in-your-browser) - [Websites need headless agents, not chatbots](https://rtrvr.ai/blog/the-web-needs-headless-website-agents) - [Web agents now 100x cheaper by making DeepSeek write code](https://rtrvr.ai/blog/code-as-plan-deepseek-flash-text-only-browser-agent) - [Navigation Was Never the Moat: Why Agents Make the Sell Side Bigger, Not Smaller](https://rtrvr.ai/blog/navigation-was-never-the-moat) - [150 open roles. 125 job titles. One missing employee.](https://rtrvr.ai/rover/blog/150-customer-engineering-jobs) - [Read the work, not the face: what an AI customer engineer should watch in a live call](https://rtrvr.ai/rover/blog/face-is-not-the-meeting) - [The hive mind for your product](https://rtrvr.ai/rover/blog/hive-mind-for-your-product) - [Narration engineering: real-time speech for the AI sales engineer inside your product](https://rtrvr.ai/rover/blog/agent-voice-is-commentary) - [1 in 80 of our website interactions is already an AI agent](https://rtrvr.ai/rover/blog/agentic-web-in-our-logs) ## Discovery - [Agent card](https://rtrvr.ai/.well-known/agent-card.json): A2A capability card for this site - [Rover site profile](https://rtrvr.ai/.well-known/rover-site.json): full site profile with actions and policies - [AGENTS.md](https://rtrvr.ai/agents.md): integration guide for coding agents - [A2W OpenAPI](https://rtrvr.ai/openapi/a2w.yaml): REST contract for agent-to-web runs