The proposed action
A machine-readable action, target, segment, threshold or intervention appropriate to the business decision.
Decision API
Graphite Note can deliver model outputs as machine-readable decision objects so another application can consume a recommendation, expected impact, confidence and supporting evidence without forcing users into a separate analytics screen.
Machine-readable output
The exact contract depends on the use case and integration. A decision object can carry the fields required by the receiving system, including decision context, recommendation, expected impact, confidence, evidence and governance state.
The example shown here is illustrative, not a fixed public API contract.
{
"decision": "reduce_discount",
"segment": "high_value_repeat_customers",
"recommended_change": "-5%",
"expected_margin_impact": "+180000 EUR",
"confidence": 0.88,
"evidence": ["causal_effect", "uplift_test"],
"review_required": true
}Integration pattern
The receiving system can be an ERP, CRM, BI product, workflow platform, vertical SaaS product or AI agent.
What can be returned
A machine-readable action, target, segment, threshold or intervention appropriate to the business decision.
An estimated business effect, uncertainty or confidence value when the underlying method supports it.
References to model outputs, causal evidence, constraints or other decision context required for audit and review.
Direct answers
No. It is designed to let an existing product keep its own interface and workflow while consuming the decision layer programmatically.
Yes. A workflow can keep approval with the responsible user and use the API to provide the recommendation, expected impact and evidence needed for that review.
Yes, where the integration is appropriate. The agent can use a governed decision object as a structured tool output instead of inventing an action from free-form text alone.
We can scope the decision object and integration around one high-value use case.