predictConsequence
Score a proposed action before it ships. `PRICING` is the first live capability.
Consequence API
Conseq is now focused on the API itself: evaluate a proposed action, return the likely second-order and third-order effects, and capture what actually happened so the system can improve over time.
Current scope
Pricing only
The first live contract focuses on price changes because outcome feedback can be gathered quickly.
Core loop
Predict → verify
A prediction is only useful if the API later learns whether it was aligned, mixed, or missed.
Proposed action
Drop bundle price from $100 to $85 in a volatile electronics category
Immediate outcome
Short-term unit lift if demand responds to the markdown
Second order
Competitors match the lower price and reset the category margin floor.
Third order
Customers anchor on the discount and future full-price conversion weakens.
Expected value
-$18.4K over 14 days
Why this matters
Most agent systems stop at guardrails. Conseq is focused on consequence modeling: what happens after the action looks valid and ships anyway.
Endpoints
Score a proposed action before it ships. `PRICING` is the first live capability.
Load the saved prediction for a specific consequence check.
Store what actually happened so the model can be checked against reality.
Design principles
The API is built to surface the consequences that look fine on the first hop but quietly create downstream losses later.
Every prediction is meant to be revisited after execution. The feedback loop matters more than a clever one-off answer.
Pricing is the first supported action family. The goal is a credible contract with real outcome data, not fake breadth.
Roadmap
The public site, the AppSync schema, and the frontend sandbox are now aligned around the API itself. Manual audits are no longer the primary product story here.