Every client’s whole picture. Current, coordinated, under your brand.
Worthune is the household platform wealth software is built on. Unified household management keeps every client’s accounts, plans and decisions current and coordinated; a full planning engine and verified calculators run on the same API.
no API key · no card · 3 models free · pricing
✓ what every response looks like
| targetAmount | $25,200 |
| monthsToGoal | 25 |
| specVersion | 1.0.0behavior pinned |
| record.sha256 | 29d48bd8…storable proof |
Live in weeks.
One API from a single calculator to a client’s whole picture. Two-line embeds, SDKs on npm and PyPI, and an MCP server so your AI assistant computes instead of guessing. A real model runs in five minutes, without a sales call.
Your brand, your client.
The product conforms to your brand, your workflows and your domains, never the other way around. Your theme, your disclosures, your client portal. We stay invisible.
Current every year. Provable on request.
Tax and benefit rules change every year. They land in the engine, sourced and versioned, not on your roadmap. And every number comes with a record you can hold it to, years later.
Unified household management. Planning. Calculators.
Three solutions, one integration. Start with whichever your roadmap needs first; the other two are already on the same API.
Unified household management
One client, every account, one current picture, and it stays true after the plan is made. Bring a book in from the systems you use today, keep it current from your aggregator feeds, and put the whole household in front of clients and advisors under your brand. Your systems hear about every change as it happens, and a weekly scan tells you which plans have gone stale.
Financial planning software
Build planning features, or a whole planning product, without building the math. The household engine takes a client’s full picture and returns a year-by-year projection, a longevity-aware Monte Carlo, and 7 strategies that answer together: withdrawal sequencing, Social Security timing, Roth ladders against IRMAA cliffs, pension elections, and more.
Financial models & calculators
Ship a finished calculator this week: retirement, refinance, AMT on an option exercise, Social Security timing. 61 models across 9 families. Embed one with a script tag, call it from your backend, or hand it to an AI copilot.
All three run on the same engine. A calculator answer and a full plan use the same rules and the same sourced figures; inputs out of range are rejected with a message, never silently adjusted; and the engine never carries a market view. Return assumptions are yours to supply, or labeled illustrative defaults until you do. Start anywhere and add the rest without re-integrating.
Computing a projection is the easy part. Keeping it current, coordinated and defensible is the work.
Any strong engineering team can compute a retirement projection. The four things below are what that team ends up owning forever.
The rules never stop moving.
A planning engine is hundreds of statutory rules with annual expiry dates: brackets and AMT every fall, Medicare tiers in November, contribution limits, RMD tables, cost-of-living adjustments. Built in-house, that is a permanent tax on your roadmap. Here, each change lands in the engine from the primary source, versioned and tested, before your users notice.
Coordination is the hard math.
One calculator is a weekend project. 7 strategies that answer together, withdrawal order against bracket management against IRMAA cliffs against Roth ladders against claiming ages, is the math that moves real client dollars, and the part in-house builds rarely reach. Every recommendation comes with its computed dollar difference and every alternative shown.
AI raised the stakes.
The moment a copilot discusses money, “mostly right” becomes a liability. The fix is not a better prompt. It is a deterministic engine the assistant calls instead of guessing, which is what our MCP server gives yours.
Someday, someone asks you to prove it.
A client disputes a number. A regulator asks where it came from. Your own QA asks what changed between March and May. Every answer here carries its record, a pinned version and cited sources, so the paper trail exists from day one instead of being reconstructed under pressure.
Built to be checked.
Every claim on this page resolves to something you can open, download or re-run. The four that matter most to a buyer are below; the full method, for the people who evaluate engines for a living, is a click deeper.
| The claim | What enforces it | Check it yourself |
|---|---|---|
| ✓You know what it computes | Every model's contract is public: inputs, units, valid ranges, and what it deliberately leaves out. An input out of range is rejected with a message, never silently adjusted. | the model contracts |
| ✓The math is checked by a second, independent build | A second implementation, written from the published specification alone, must agree with the engine on 250 cases per model before a release ships. A disagreement stops the release. | how a model earns a release |
| ✓The constants are sourced and dated | IRS, SSA, CMS, HHS: each figure with its primary source, its effective period, and the date a person last checked it. Every answer cites the figures it used. | the facts registry |
| ✓You can prove where a number came from | Every answer, calculator or household, carries a record you can recompute at any time. Paste one in and check it now. | check a record now |
Four ways to ship. The same engine underneath.
Lightest first. Most builds use two or three.
Embed it
Two lines of markup on any page, a script tag or a web component. Calculators and household widgets, framed, disclosed and self-sizing.
Call it
REST from your backend, SDKs on npm and PyPI, and signed webhooks when a stored household changes or a plan goes stale. Send JSON, get the number and its receipt.
Connect an agent
Over MCP, an assistant can create a household, project it, run the strategies and check its own claims before it speaks.
Make it yours
The React kit and white-label tenant configuration: your brand and theme, your disclosures appended, embeds bound to your own domains.
<div data-worthune-embed="household-overview"></div>
<script async src="https://worthune.com/embed.js"></script>Bringing a book of clients? Bulk import moves a book from the systems you use today: a dry run first that lists every problem row, imports you can re-run safely, and an AI that drafts the field mapping while deterministic code executes it. See how integration works.
Three doors into the same room.
Product & engineering teams
Wealthtech and fintech with planning on the roadmap and no appetite to build and maintain an engine every tax year. Start with one model; grow into households.
start with the API →Wealth firms, banks & their agencies
Advisory firms, banks and insurers shipping client experiences under their own brand: white-label theming, appended disclosures, a reference build to fork, and migration for the book.
start with the reference build →AI & agent platforms
Copilots that discuss money cannot improvise it. Real computation over MCP, claim checks before the agent speaks, and a benchmark that shows why both matter.
start with MCP →Priced on households you keep, never on calls.
3 models are free to call with no signup and no key, and the household engine runs free on your own numbers. There is no run meter, and there will not be.
- 3 full models, keyless
- The household engine on your own numbers, nothing stored
- A free 30-day test key for the stored household features
- Specs, case files and the record check, open
- Both engines: the whole catalog and households
- API, MCP, SDKs, embeds, webhooks
- Bulk import for migration
- 250 active households included
- Unbranded embeds and API results
- White-label: your brand, theme, and disclosures
- Tenant-bound embeds on your domains
- Attribution removal
- 2,500 active households included
- Priority support, first access to new families
The questions a careful buyer asks
Why not build this in-house?
You can; the arithmetic is not the hard part. Staying current every tax year, re-testing everything after each change, reaching the coordination math, and defending numbers under dispute is a permanent team, not a project. Buying that back lets your engineers build what makes you different.
How fast is “live in weeks,” really?
An embedded calculator: the same day, two lines of markup. Planning features over the API: a sprint. A white-labeled client portal: weeks, starting from the reference build. The free tier lets you prove all of this on real calls before paying anything.
Is this three products?
No. Three solutions on one platform. Unified household management is the household engine kept current across a client’s life; planning is the same engine at one moment; calculators are single decision models. Same rules, same constants, one integration, and the pricing does not split them.
Is any of this financial advice?
No. The engines compute; they do not recommend, and they carry no market view. Return assumptions are yours to supply, or labeled illustrative defaults until you do. Every decision surface shows the alternatives, not just the winner.
We already built our own engine.
Then grade it: post your inputs and answers and get a pass or fail per case at the tolerances we hold ourselves to. Agreement hands you a regression suite; a disagreement hands you a bug worth finding before a customer does.
What happens when tax law changes?
We update the figures from the primary source, version the affected models, note it in the changelog, and your integration keeps working with current numbers. That maintenance is the product as much as the math is.
See it work in five minutes.
Paste this into a terminal. No account, no key, no sales call. The fastest way to evaluate us is to use us.
# compute
$ curl -s -X POST https://worthune.com/api/v1/models/emergency-fund \
-H 'content-type: application/json' \
-d '{"monthlyExpenses":4200,"targetMonths":6,
"currentSavings":8000,"monthlySavings":650,
"savingsAccountRate":0.042}'Want to see it before you write any code? Every calculator is a live demo, the planning engine runs end to end on a labeled fictional household, and you can put your own household — or a whole book — through it without an account, because nothing is stored. Try the calculators → See a full plan → Use your own numbers → Scan a book →