Developer Docs

Integrate support routing in minutes.

For subscription support teams using Zendesk, Intercom, or internal agents: call /api/decide for deterministic routing, then run policy checks through MCP or REST notaries.

Open live demo Machine spec (`docs.json`)

Canonical flow: ticket to policy execution

Use one production path for both humans and agents so every action is deterministic and auditable.

Decide route (`/api/decide`)

Submit ticket intent and context. Store request_id with the ticket or workflow run.

Execute policy (`/api/mcp` or REST)

Call the relevant notary (refund, cancel, return, trial) using the routed payload.

Apply action and log evidence

Run macro or automation, then persist verdict fields and request_id for QA, disputes, and replay.

# Example (subscription refund workflow)
POST /api/decide -> { "c": "yes", "request_id": "abc123" }
POST refund notary -> { "class": "ALLOWED", "reason": "within window" }
Apply refund macro and store request_id in ticket metadata

Core endpoints

Endpoint	Method	Purpose
`/api/decide`	POST	Return deterministic `yes \| no \| tie` for routing decisions.
`https://refund.decide.fyi/api/mcp`	POST	MCP JSON-RPC for refund eligibility tools/call.
`https://cancel.decide.fyi/api/mcp`	POST	MCP JSON-RPC for cancellation penalty checks.
`https://return.decide.fyi/api/mcp`	POST	MCP JSON-RPC for return eligibility checks.
`https://trial.decide.fyi/api/mcp`	POST	MCP JSON-RPC for trial terms checks.

Quickstart: route a ticket in 60 seconds

Use one canonical path: ticket payload -> /api/decide -> workflow endpoint -> deterministic action + request_id.

cURL

curl -X POST https://www.decide.fyi/api/v1/workflows/zendesk/refund \
  -H "Content-Type: application/json" \
  -d '{
    "vendor": "adobe",
    "region": "US",
    "plan": "individual",
    "days_since_purchase": 12,
    "ticket_id": "zd-4812"
  }'

# response shape
# { "request_id": "...", "action": "refund", "policy_class": "ALLOWED" }

Node

const payload = {
  vendor: "adobe",
  region: "US",
  plan: "individual",
  days_since_purchase: 12,
  ticket_id: "zd-4812"
};

const res = await fetch("https://www.decide.fyi/api/v1/workflows/zendesk/refund", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify(payload)
});
const data = await res.json();
console.log(data.request_id, data.action, data.policy_class);

Python

import requests

payload = {
    "vendor": "adobe",
    "region": "US",
    "plan": "individual",
    "days_since_purchase": 12,
    "ticket_id": "zd-4812"
}

res = requests.post(
    "https://www.decide.fyi/api/v1/workflows/zendesk/refund",
    json=payload,
    timeout=15,
)
data = res.json()
print(data.get("request_id"), data.get("action"), data.get("policy_class"))

Pilot onboarding checklist (day 0 to day 7)

Use this exact sequence to move from intake to first live queue traffic without scope drift.

Window	Owner	Required output
Day 0-1	Support ops + decide	Queue selected, baseline KPI formulas frozen, escalation path confirmed.
Day 2-3	Platform/automation engineer	`/api/decide` wired into one macro/workflow with `request_id` persistence.
Day 4-5	Policy owner	Notary payload contract validated on sample tickets, exception classes reviewed.
Day 6-7	Support ops + QA	First live-traffic readout, replay checks, and dispute evidence export confirmed.

Operational runbook (weekly)

1) Pull metrics snapshot

Use ops console or /api/proof-metrics to capture pilot intake, delivery rate, and event activity windows.

2) Validate outcome health

Confirm escalation-rate and handle-time deltas against the locked baseline, then flag blockers before rollout expansion.

3) Publish evidence package

Export CSV + request-linked artifacts for policy owners, QA, and procurement decision threads.

Runtime and webhook endpoints

Route	Use	Readiness dependency
`/api/runtime-config`	Front-end runtime/commercial readiness config.	Payment links, booking URL, pilot confirmation channel.
`/api/pilot`	Pilot intake submission + confirmation trigger.	Webhook destination and confirmation provider config.
`/api/proof-metrics`	Pilot and activity snapshot used by proof/ops views.	`x-metrics-token` for protected reads.
`/api/pilot-export`	CSV export for rollout review and evidence packs.	Metrics token + proof metrics data availability.

Reference assets

Machine-readable catalog

/docs.json contains endpoint, schema, and rate-limit metadata.

Policy source snapshots

/rules/policy-sources.json and category-specific variants for policy provenance checks.

Confirmed policy alerts

/resources/policy-alerts and /api/policy-alerts for confirmed daily change alerts.

Live demo validation

Use live demo + audit trail to validate payloads, assertions, and replay behavior.

Security posture

Share /resources/security with procurement and security reviewers during pilot intake.