Decision API

Put the decision inside the workflow.

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

A recommendation your product can consume.

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.

Illustrative decision objectJSON
{
  "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

Keep your interface. Add a decision layer.

Your application
→
Business context + candidate actions
→
Graphite Note Decision API
→
Recommendation + impact + evidence

The receiving system can be an ERP, CRM, BI product, workflow platform, vertical SaaS product or AI agent.

What can be returned

More than a score.

RECOMMENDATION

The proposed action

A machine-readable action, target, segment, threshold or intervention appropriate to the business decision.

EXPECTED IMPACT

What is expected to change

An estimated business effect, uncertainty or confidence value when the underlying method supports it.

EVIDENCE

Why the action was selected

References to model outputs, causal evidence, constraints or other decision context required for audit and review.

Policy-bound execution

A decision object can carry the guardrails with the recommendation.

For agentic or automated workflows, the useful contract is not just an action. It is an action that has been checked against the relevant business policy and can state what the receiving system is allowed to do next.

POLICY

Eligibility and constraints

Candidate actions can be screened against product, customer, commercial and operational rules before recommendation.

AUTHORITY

Permissions and approval state

The object can distinguish actions that are safe to execute automatically from those that require review or escalation.

AUDIT

Evidence and outcome record

Keep the recommendation, expected impact, evidence, governance state and eventual outcome together so the decision can be reviewed later.

Direct answers

How the API fits.

Does the Decision API replace our application UI?

No. It is designed to let an existing product keep its own interface and workflow while consuming the decision layer programmatically.

Can the output require human review?

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.

Can Graphite Note work behind an AI agent?

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.

Can the API enforce business rules and escalation?

The integration can include policy, eligibility and operating constraints before a recommendation is returned, plus a governance state that tells the receiving workflow whether the action may proceed, needs approval or should be escalated.

Your product already has the workflow. Add the decision.

We can scope the decision object and integration around one high-value use case.