Senior Grief
by SeniorPulse in Other
After-death checklist / what to do when an elderly parent or spouse dies: estate steps to take, survivor benefits to claim, and grief-support resources. For family and caregiver agents — informational.
https://seniorpulse.theaslangroupllc.com/api/senior/grief- Price
- $0.1
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 4 h ago, next any minute now
Reliability
Latest check failed 4 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://seniorpulse.theaslangroupllc.com/api/senior/grief
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://seniorpulse.theaslangroupllc.com/api/senior/grief?situation=%27spouse+passed+3+days+agoParameters
| Parameter | Type | Required | Description |
|---|---|---|---|
days_since | number | No | Days since the loss — calibrates guidance to immediate (0–7 days), short-term (1–4 weeks), or ongoing estate (1–12 months) phases |
lang | string | No | Response language — any language supported |
situation | string | No | Describe the situation (e.g. 'spouse passed 3 days ago, need to know what to do immediately', 'mother died 2 months ago, estate still open') |
state | string | No | US state or country for jurisdiction-specific probate and estate guidance |
Example response
The listing has no example response.
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://seniorpulse.theaslangroupllc.com/api/senior/grief?situation=%27spouse+passed+3+days+ago'
# 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://seniorpulse.theaslangroupllc.com/api/senior/grief?situation=%27spouse+passed+3+days+ago' \
| 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%2Fseniorpulse.theaslangroupllc.com%2Fapi%2Fsenior%2Fgrief
const res = await pay("https://seniorpulse.theaslangroupllc.com/api/senior/grief?situation=%27spouse+passed+3+days+ago");
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://seniorpulse.theaslangroupllc.com/api/senior/grief?situation=%27spouse+passed+3+days+ago")
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 |
|---|---|---|---|---|
| 4 h ago | Amount "0.1" is not in atomic token units | 402 | 238 ms | $0.1 |
| 9 h ago | Amount "0.1" is not in atomic token units | 402 | 174 ms | $0.1 |