rigor_execute
Execute a structured workflow end-to-end. Call rigor_plan first (free) to preview the step sequence and cost estimate before committing credits. Classifies the task, selects the optimal tool sequence, and executes each step with the right LLM model. Returns a complete deliverable — solution designs, competitive analyses, governance documents, and more. Supports SSE streaming for real-time progress, webhook callback, or polling. For atomic work — classification, scoring, ranking, entity extraction, query parsing — set preferences.execution to 'direct' and declare preferences.output_contract to get validated JSON records from a single call, routed to the cheapest model that holds the schema.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| context | No | Additional context for the workflow. | |
| delivery | No | Delivery method. Default: polling (MCP clients typically can't handle SSE). | |
| task_type | No | Optional hint to bypass automatic classification. Passing it also removes the slowest classification tiers from the critical path, so send it whenever you know the shape. Multi-step deliverable types: solution_design, requirements_analysis, code_implementation, code_review, bug_fix, root_cause_analysis, incident_response, deployment_execution, competitive_scan, financial_analysis, research_task, documentation, governance_change, compliance_audit, data_security_assessment, performance_optimization, user_story_definition, implementation_prompt_generation. Atomic single-call types, which auto-select direct execution: tag, score, rerank, compose, extract_entities, parse_query, quick_research, quick_classification, quick_extraction, quick_scoring. Call GET /api/rigor/task-types for the full vocabulary with each type's shape. | |
| preferences | No | Optional workflow preferences. | |
| context_fields | No | Optional, with prior_workflow_id: the fields to carry over. Pass ["full_step_results"] for every step output in full. | |
| task_description | Yes | Natural language description of the task, at most 4,000 characters. Be specific — include what you want produced, constraints, and context. Example: 'Design a caching layer for our API gateway with Redis integration.' | |
| prior_workflow_id | No | Optional: the workflow_id (wr_…) of a finished workflow in your workspace to build on. Its results are passed to this run as context. It is charged as a new run at the normal quote. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ok | No | ||
| status | No | ||
| poll_url | No | ||
| execution | No | Present with value 'direct' when direct execution ran. Absent for standard multi-call execution. | |
| task_type | No | ||
| value_class | No | ||
| workflow_id | No | ||
| delivery_mode | No | ||
| available_modes | No | ||
| estimated_credits | No | ||
| execution_fallback | No | True when you explicitly requested direct execution and it could not be honoured — the workflow ran as standard multi-call instead. Never set for an auto-selected attempt, since you did not ask. |