RAZOOM Engine
Problem-solving intelligence as infrastructure.
An API intended to expose structured problem solving — problem models, attack plans, evidence and Case outcomes.
You send a problem. You get back a structure.
Illustrative API
POST /casesContent-Type: application/json{ "problem": "Should we expand into Poland?", "depth": "deep", "constraints": {}, "context": {}}{ "problem_model": {}, "questions": [], "attack_plan": {}, "analysis": {}, "case_outcome": {}, "confidence": "medium"}- problem_model
- The diagnosed problem: objective, any choice at stake, constraints and reframing.
- questions
- Clarifying questions worth answering — often an empty list.
- attack_plan
- Subproblems, their dependencies and the method chosen for each.
- analysis
- Results of each method, with inputs and evidence references.
- case_outcome
- The current conclusion or next step, its type and conditions.
- confidence
- Calibrated confidence in the Case outcome, when applicable.
Designed for software that needs a structured outcome.
RAZOOM Engine is intended to return the problem structure, supporting analysis and current Case outcome in fields your application can use.
Structured, not generated
Responses are typed objects — problem models, plans and claims — not paragraphs to parse.
Asynchronous by design
Deep Cases take time. The API is designed around Case state and events, not a single blocking call.
Same execution policy
Local by default. Frontier escalation through the API still requires operator authorization.
Clarifying questions as data
When RAZOOM needs information, your application receives the questions and answers them programmatically.
Build on structured reasoning.
Tell us what you would build with an API that returns attack plans and reasoned Case outcomes.
