Agentic reasoning, explained
The API is intentionally simple: you send a short case description, and the system returns a three‑part reflection. Under the hood, it runs a constrained, auditable pipeline so outputs stay grounded and consistent.
Normalize the case, classify the dominant tension, and deterministically select a KB cluster using selection rules.
Compose a three‑part response using only the verse set for the chosen cluster and a lens‑specific principle template.
A strict validator checks headings, verse usage, and tone; a repair step fixes drift without changing the core intent.
In dev, each request returns a trace of the chosen tension, cluster, verses, and validator result.
Ready to try the endpoint?
Use the Reflect form or call the endpoint with your own input.
Example request
A minimal POST that triggers the agentic pipeline. Customize the situation as needed.
curl -sS -X POST "http://localhost:3000/api/reflect" \
-H "Content-Type: application/json" \
--data-binary '{
"situation": "I keep changing direction because I compare myself to other founders.",
"roles": ["founder_builder"],
"dominantEmotion": "restlessness",
"primaryTensionUserSelected": "not_sure",
"blockedOn": "comparison and over-optimization",
"lens": "secular"
}'