mirror of
https://github.com/hanzoai/kai.git
synced 2026-10-17 11:18:06 +00:00
Every runner printed whatever came back and exited 0, and fell back to a second raw HTTP call when the SDK import failed. Now each recipe carries expect.json, the answers a careful reader gives on its own input: a list of acceptable options for a choice, of level indices for a score, true or false for a noul. run.py and run.ts send request.json through the SDK, print every answer, and exit 1 when a checked one is wrong. A question with no obvious answer on its input is printed and not checked. Recipes 09 and 11 had no input with an obvious answer, so each state gains the one fact that decides it. The recipe READMEs describe what each recipe asks instead of capabilities it never exercised, and copy the request and checked answers from the two JSON files. Co-authored-by: Hanzo Dev <[email protected]>
Commerce: Plan Recommendation
Pick the plan to offer a developer from their usage and rate-limit history.
Request (request.json)
{
"model": "kai",
"state": {
"current_plan": "Free",
"monthly_tokens": 1400000,
"frequent_models": [
"zen-coder",
"zen-vl"
],
"rate_limit_hits_last_7d": 18
},
"questions": {
"recommended_plan": {
"type": "choice",
"instructions": "Which plan provides best value and capacity?",
"criteria": {
"developer_pro": "$20/mo with 500 RPM and priority inference",
"dedicated_team": "$199/mo with warm GPU instances and team seats",
"custom_enterprise": "negotiated annual commitment with SLA"
}
}
}
}
Checked answers (expect.json)
recommended_plan(choice):developer_pro
Run
From the repository root, after pip install -r requirements.txt and npm install:
curl -sS --fail-with-body https://api.hanzo.ai/v1/decisions \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d @recipes/10_commerce_recommendation/request.json
python3 recipes/10_commerce_recommendation/run.py
npx tsx recipes/10_commerce_recommendation/run.ts
run.py and run.ts print every answer and exit 1 when a checked answer is wrong.