13trust / 100

Wealth Ssa

by WealthPulse in News & content

x402 APIFailing, checked 3 h ago

What age should I claim Social Security? Optimal claiming-age analysis with benefit estimates at 62, full retirement age, and 70, break-even math, spousal and survivor benefits, and tax implications. For retirement and wealth agents.

GET
https://wealthpulse.theaslangroupllc.com/api/wealth/ssa
Price
$0.15
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

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Latest check failed 3 h ago: Amount "0.15" 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/ssa

Each call costs $0.15 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/ssa?birth_year=1965&marital_status=single

Parameters

ParameterTypeRequiredDescription
birth_yearstringNorequired
healthstringNogood | fair | poor
incomestringNo95000 (current annual earnings USD)
langstringNoen | es | fr | de | pt | zh
marital_statusstringNosingle | married | divorced | widowed (default: single)

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=Social+Security+claiming+strategy&tag=pulsenetwork7-20",
  "amazon_search": "Social Security claiming strategy",
  "birth_year": "1965",
  "breakeven_analysis": {
    "early_vs_fra": "Age 78 vs claiming at 62",
    "fra_vs_70": "Age 82-83 vs claiming at FRA",
    "interpretation": "Delaying pays off if you expect to live past your late 70s"
  },
  "disclaimer": "For informational purposes only. Benefit estimates are illustrative. Use SSA.gov My Social Security for your actual projected benefits based on your earnings record.",
  "key_ages": {
    "earliest_claiming": "62",
    "fra_note": "Born in 1960 or later, FRA is 67",
    "full_retirement_age": "67",
    "maximum_delay_age": "70"
  },
  "monthly_benefit_scenarios": [
    {
      "claim_age": "62",
      "reduction_or_increase": "30% reduction vs FRA",
      "relative_benefit": "If FRA benefit is $2,600: ~$1,820/mo"
    },
    {
      "claim_age": "70",
      "reduction_or_increase": "24% increase over FRA",
      "relative_benefit": "If FRA benefit is $2,600: ~$3,224/mo"
    }
  ],
  "optimal_strategy": "Delay to 70 given married status and good health — 24% higher benefit and larger survivor protection",
  "spousal_benefits": {
    "applies": true,
    "strategy": "The higher earner should delay to maximize the survivor benefit",
    "survivor_benefit_note": "A surviving spouse steps up to the higher of the two benefits"
  }
}

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.15.

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/ssa?birth_year=1965&marital_status=single'

# 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/ssa?birth_year=1965&marital_status=single' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: 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.15 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.15" });
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.15 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fwealthpulse.theaslangroupllc.com%2Fapi%2Fwealth%2Fssa
const res = await pay("https://wealthpulse.theaslangroupllc.com/api/wealth/ssa?birth_year=1965&marital_status=single");
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.15 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.15"})
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/ssa?birth_year=1965&marital_status=single")
    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

WhenResultHTTPTimePrice
3 h agoAmount "0.15" is not in atomic token units402442 ms$0.15
9 h agoAmount "0.15" is not in atomic token units402208 ms$0.15
15 h agoAmount "0.15" is not in atomic token units402168 ms$0.15
20 h agoAmount "0.15" is not in atomic token units402211 ms$0.15
26 h agoAmount "0.15" is not in atomic token units402197 ms$0.15
Show 7 older checks
32 h agoAmount "0.15" is not in atomic token units402214 ms$0.15
37 h agoAmount "0.15" is not in atomic token units402254 ms$0.15
42 h agoAmount "0.15" is not in atomic token units402246 ms$0.15
2 days agoAmount "0.15" is not in atomic token units402188 ms$0.15
2 days agoAmount "0.15" is not in atomic token units402197 ms$0.15
2 days agoAmount "0.15" is not in atomic token units402151 ms$0.15
3 days agoAmount "0.15" is not in atomic token units402158 ms$0.15