Financial planning & wealthtech infrastructure
A retirement planning API with the hard parts included
A retirement planning API has to cover the math that actually decides retirements: when to claim Social Security, how to sequence withdrawals across taxable, traditional, and Roth accounts, whether a conversion ladder beats the IRMAA cliff it might trigger, and how long the money must last. Worthune ships those as verified models and coordinated household strategies — Social Security timing on SSA's own factors, RMDs, Roth ladders computed against bracket and Medicare thresholds, pension elections ranked on joint outcomes, and a Monte Carlo that draws longevity from SSA life tables instead of assuming a fixed age.
What to look for — whoever you choose
Longevity from the table, not a slider
Planning to average life expectancy is a coin flip — half of clients outlive it. The engine should draw horizons from published mortality tables and let the planning percentile be an explicit choice.
The cliff interactions
Retirement income is where three rule sets collide: Social Security taxation, Medicare surcharges, and (before 65) ACA subsidies. An API that computes each in isolation misses the true marginal rate that drives the decision.
Coordination across accounts
Withdrawal order, conversion timing, and claiming age are one decision wearing three hats. Look for strategies that answer together, with dollar deltas, rather than three calculators that disagree.
How Worthune answers it
The retirement family
FIRE, Roth vs. traditional, conversion ladders, backdoor and mega-backdoor, employer match, RMDs, SSA PIA, and Social Security timing — each spec'd, verified, and sourced.
→ see the modelsCoordinated drawdown strategies
Withdrawal sequencing, IRMAA-aware Roth ladders, claiming coordination, and pension elections run on the household's own projection, alternatives shown.
→ see the household engineLongevity-aware simulation
The Monte Carlo is seeded and mortality-aware, on SSA period life tables transcribed under a survivor-recursion check.
→ see it liveWhere this fits: everything above is one platform — calculators & models, planning software, and unified household management, on the same verified engines and one API. How the numbers are made is public: the methodology.
Common questions
Does the API compute Social Security claiming ages?
Yes — from SSA's own primary insurance amount math and actuarial factors, as a standalone model and as a household strategy that evaluates claiming ages on the household's own projection, spousal coordination included.
How does it handle Roth conversions against IRMAA?
The Roth ladder strategy computes multi-year conversion schedules against both bracket boundaries and Medicare IRMAA thresholds — the cliff a conversion can quietly cross two years out — with the cost of each alternative computed in dollars.
How is longevity modeled?
From the SSA period life table rather than a fixed horizon: deterministic projections use an explicit planning percentile, and the Monte Carlo simulates lifetimes, so "will the money last" is answered against how long lasting actually takes.
Is any of this financial advice?
No. The engine computes and shows every alternative; it never recommends, carries no market view, and states its assumptions and exclusions in published specs. The advice remains the professional's.
Talk to us