Money Moves
Money Moves are weekly personalized financial tasks. They are the engine that turns a plan into real behavior. The POST /v1/money-moves/generate endpoint is stateless — you call it with context, it returns a set of tasks, and your application stores and tracks them.
The three task types
Every money move week contains a mix of three task types:
| Type | Code | Purpose |
|---|---|---|
| Do | do | A concrete financial action with a dollar amount (e.g., transfer $375 to savings) |
| Learn | learn | An educational task tailored to the user's situation |
| Mind | mind | A mindset or reflection exercise |
The do task amount is derived from the user's future envelope allocation divided by the move cadence.
How personality shapes moves
POST /v1/money-moves/generate accepts personality_type and plan_tier as inputs. Each personality type receives distinctly framed tasks:
| Personality | Move framing style |
|---|---|
| HOTSHOT | Growth-oriented; frames savings as building future leverage |
| STOCKPILER | Security-first; emphasizes buffer milestones and fund progress |
| GIVER | People-aware; acknowledges generosity as part of the financial plan |
| INDEPENDENT | Non-prescriptive; frames moves as options the user chooses from |
How moves are generated
Your app calls: POST /v1/money-moves/generate
body: {
user_id: "ozz_usr_...",
personality_type: "STOCKPILER",
plan_tier: "30/70",
week_start: "2026-05-13"
}
│
▼
ozzie-openapi returns a set of tasks for the current week
│
▼
Your app stores the move set and tracks completion status
Integration pattern
- After plan generation, call
POST /v1/money-moves/generatewith the user'spersonality_typeandplan_tier - Store the returned task set in your database
- Display the current week's tasks in your UI
- When the user completes a task, update its status in your database
- Record goal contributions based on the
dotaskamount_cents - At the start of each new week, call
POST /v1/money-moves/generateagain for a fresh set