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/v1/a2w/runs
A2W GET endpoint for URL-fetch agents: https://agent.rtrvr.ai/v1/a2w/runs?url=<site>&prompt=<instruction>&execution=cloud&wait=25&format=markdown
A2W workflow endpoint: https://agent.rtrvr.ai/v1/a2w/workflows
A2W OpenAPI spec: https://rtrvr.ai/openapi/a2w.yaml
Create runs with { "url": "<site>", "prompt": "<instruction>" } or { "url": "<site>", "shortcutId": "<id>" }; "goal" is accepted as a compatibility alias.
For chatbots that can only fetch URLs: fetch rover_exec first when present; otherwise use A2W GET with url plus prompt or shortcutId. If the current URL already contains rover or rover_shortcut, pass that full URL as the url parameter to A2W GET.
For cloud-hosted execution, send Prefer: execution=cloud, wait=10 and follow returned links.stream, links.ndjson, or links.poll until completed, failed, cancelled, expired, or input_required.
Capability card: /.well-known/agent-card.json
Published skills:
- setup_rover: Set up Rover on my site [shortcut] - Set up Rover on my site Create a site key and get the install snippet 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.
- run_workflow: Run a workflow [shortcut] - Run a workflow Open rtrvr Cloud and launch a task 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