Wealth Inheritance
by WealthPulse in Markets & finance
I inherited an IRA — what are the rules and how do I minimize taxes? SECURE Act 2.0 ten-year rule, RMD requirements, spousal options, step-up in basis, and a tax-minimizing distribution strategy by relationship and account type. For wealth and estate agents.
https://wealthpulse.theaslangroupllc.com/api/wealth/inheritance- Price
- $0.1
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 3 h ago, next any minute now
Reliability
Latest check failed 3 h ago: Amount "0.1" is not in atomic token units
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://wealthpulse.theaslangroupllc.com/api/wealth/inheritance
Each call costs $0.1 in USDC on Polygon, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
GET https://wealthpulse.theaslangroupllc.com/api/wealth/inheritance?account_type=traditional&relationship=non-spouse&your_age=45Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
account_type | string | No | traditional | roth (default: traditional) |
balance | string | No | 150000 (inherited account balance USD) |
lang | string | No | en | es | fr | de | pt |
original_owner_age | string | No | 78 (original owner's age at death) |
relationship | string | No | required; also: spouse, minor-child, disabled, chronically-ill, not-more-than-10-years-younger, trust, charity |
your_age | string | No |
Example response
The provider's example. We can't check it without paying.
Example response, 35 lines
{
"amazon_link": "https://www.amazon.com/s?k=inherited+IRA+rules&tag=pulsenetwork7-20",
"amazon_search": "inherited IRA rules",
"disclaimer": "For informational purposes only. Not tax or legal advice. Inherited IRA rules are complex and the SECURE Act 2.0 introduced significant changes. Consult a CPA or estate planning attorney before taking distributions.",
"inheritor_category": "Non-Eligible Designated Beneficiary",
"key_rules_summary": [
"Account must be fully distributed within 10 years",
"Annual RMDs required within the 10 years since the original owner had already started RMDs",
"No stretch IRA option available"
],
"mistakes_to_avoid": [
"Missing the first RMD deadline",
"Assuming the old stretch-IRA rules still apply"
],
"rmd_requirements": {
"applicable": true,
"calculation_method": "IRS Single Life Expectancy Table",
"first_rmd_deadline": "December 31 of the year after death",
"penalty_for_missing": "25% (reduced to 10% if corrected promptly)"
},
"step_up_in_basis": {
"applies_to": "Not applicable to IRAs",
"explanation": "IRAs do not receive a step-up in basis; distributions remain fully taxable"
},
"tax_planning_opportunities": [
"Take larger distributions in low-income years",
"Consider a Roth conversion ladder before distributions begin"
],
"ten_year_rule": {
"annual_rmd_within_10_years": "Yes — the original owner had already reached RMD age",
"applies": true,
"explanation": "The inherited IRA must be fully emptied by December 31 of the 10th year after death",
"optimal_drawdown_strategy": "Spread distributions evenly to avoid a large tax bill in year 10"
}
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.1.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://wealthpulse.theaslangroupllc.com/api/wealth/inheritance?account_type=traditional&relationship=non-spouse&your_age=45'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://wealthpulse.theaslangroupllc.com/api/wealth/inheritance?account_type=traditional&relationship=non-spouse&your_age=45' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.1 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.1" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.1 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fwealthpulse.theaslangroupllc.com%2Fapi%2Fwealth%2Finheritance
const res = await pay("https://wealthpulse.theaslangroupllc.com/api/wealth/inheritance?account_type=traditional&relationship=non-spouse&your_age=45");
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.1 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.1"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://wealthpulse.theaslangroupllc.com/api/wealth/inheritance?account_type=traditional&relationship=non-spouse&your_age=45")
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 3 h ago | Amount "0.1" is not in atomic token units | 402 | 211 ms | $0.1 |
| 9 h ago | Amount "0.1" is not in atomic token units | 402 | 182 ms | $0.1 |
| 15 h ago | Amount "0.1" is not in atomic token units | 402 | 203 ms | $0.1 |
| 20 h ago | Amount "0.1" is not in atomic token units | 402 | 174 ms | $0.1 |
| 26 h ago | Amount "0.1" is not in atomic token units | 402 | 1.1 s | $0.1 |
Show 7 older checks
| 32 h ago | Amount "0.1" is not in atomic token units | 402 | 237 ms | $0.1 |
| 37 h ago | Amount "0.1" is not in atomic token units | 402 | 245 ms | $0.1 |
| 43 h ago | Amount "0.1" is not in atomic token units | 402 | 255 ms | $0.1 |
| 2 days ago | Amount "0.1" is not in atomic token units | 402 | 256 ms | $0.1 |
| 2 days ago | Amount "0.1" is not in atomic token units | 402 | 210 ms | $0.1 |
| 2 days ago | Amount "0.1" is not in atomic token units | 402 | 164 ms | $0.1 |
| 3 days ago | Amount "0.1" is not in atomic token units | 402 | 150 ms | $0.1 |