llms.txt Content
# 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.
Primary A2W run endpoint: https://agent.rtrvr.ai/v2/a2w/runs
A2W GET for URL-fetch chatbots: https://agent.rtrvr.ai/v2/a2w/runs?url=<site>&prompt=<instruction>
A2W workflow endpoint: https://agent.rtrvr.ai/v2/a2w/workflows
A2W OpenAPI spec: https://rtrvr.ai/openapi/a2w.yaml
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.
Capability card: /.well-known/agent-card.json
Published skills:
- setup_rover: Set up 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 [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