Skip to main content
POST
Rollout (Multi-Step Prediction)

Overview

The /v1/rollout endpoint provides multi-step action prediction - a crystal ball for web automation. Predict what will happen through a sequence of actions without executing them.
Think of it as: Simulating the future before you commit to it.

Use Cases

Plan Validation

Test if an action sequence will achieve your goal

Path Comparison

Compare multiple sequences to find the optimal one

Debugging

Understand why an action sequence failed

Goal Estimation

Determine minimum steps needed for a goal

Request Modes

Goal-Based Planning

Let Stratus plan the action sequence for you:

Explicit Action Sequence

Test a specific sequence you provide:

Parameters

string
required
Natural language description of what you want to achieve
integer
default:5
Maximum number of steps to plan (1-10 recommended)
integer[]
Explicit action IDs to execute (0-66). If provided, overrides planning.
boolean
default:true
Include intermediate state predictions. Note: Must be true (known bug with false)
string
Custom initial state description (optional)
string
Execution mode for the rollout (optional)

Response

Understanding Results

State Magnitude

The magnitude field indicates state complexity:

State Change

The state_change field shows transition significance:
Pro tip: Actions with state change >15 are usually the most important steps in your sequence.

Outcome Interpretation

The outcome field predicts goal achievement:
  • “Goal likely achieved” - Total state change >20, strong prediction
  • “Significant progress” - Total state change 10-20, moderate progress
  • “Minimal progress” - Total state change <10, weak prediction

Examples

Validate a Plan

Compare Action Sequences

Estimate Steps Needed

Performance

Latency increases linearly with max_steps. For best performance, use 3-5 steps.

Action Categories

Actions are categorized by their purpose:

Known Limitations

Known Bug: Setting return_intermediate: false causes a server error. Always use true.
Additional limitations:
  • 903 discrete actions (action IDs 0-902)
  • State embeddings not human-readable (use magnitude/change as proxies)
  • Planning quality depends on goal clarity

Troubleshooting

”500 Internal Server Error”

Check if return_intermediate is set to false. Change to true.

Unexpected Action Sequence

Make your goal more specific:

Slow Response (>10s)

Reduce max_steps:

Real-World Example

Here’s a complete example from production testing:
Analysis:
  • ✅ Logical sequence: search → select result → read details
  • ✅ High confidence (all states >15 magnitude)
  • ✅ Strong transitions (15.48, 11.10, 18.95)
  • ✅ Goal achievement predicted (23.45 total change)
  • ⏱️ Response time: ~2.5s

What’s Next?

  • Phase 2: Policy head for better action selection (Feb-Mar 2026)
  • Phase 3: Generative adapter to translate embeddings → text (Mar-Apr 2026)
  • Phase 4: Continuous action space for precise control (Apr-May 2026)

Need Help?

See more examples and use cases in our concepts guide