Age calculator
POST /api/ageCompute a precise age (years, months, days) from a birth date to today (or a given date), plus total days. Send POST /api/age with the required field birthdate and pay $0.001 per call over x402 or MPP, or call it free by solving a proof-of-work challenge. It returns a JSON object with years, months, days and totalDays.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
birthdate | any | yes | Birth date |
asOf | any | no | Reference date (default now) |
Example request
curl -i -X POST https://agent402.tools/api/age \
-H "Content-Type: application/json" \
-d '{"birthdate":"1990-05-20"}'
Without payment this returns HTTP 402 Payment Required with the exact price for age; any x402 v2 or MPP client pays it and retries.
Example response
{
"years": 36,
"months": 0,
"days": 22,
"totalDays": 13166
}
| Field | Type | Always present | In the example |
|---|---|---|---|
years | number | yes | 36 |
months | number | yes | 0 |
days | number | yes | 22 |
totalDays | number | yes | 13166 |
From an MCP client
catalog.call {
"slug": "age",
"params": {
"birthdate": "1990-05-20"
}
}
On the hosted connector at https://agent402.tools/mcp, catalog.call runs age free (rate-limited, no wallet). Local install: npx -y agent402-mcp.
Errors and behavior
birthdateis required. An input the tool rejects returns an HTTP 4xx whose body carrieserror,tool,expected,requiredandexample, so the caller can correct it.- A paid call that ends in any status of 400 or above is not charged over x402, MPP or a prepaid credits key: settlement is cancelled when the tool fails. The exception is a Tempo push credential, a transfer the buyer sent before the call: it settles before the tool runs, so if the tool then fails the payment is recorded as a refund owed to the paying wallet.
- Free tier: no outbound network call leaves the server for this tool, so proof-of-work (16 leading zero bits of sha256) pays for it.
- A
GETorHEADto /api/age returns the same 402 quote, so the price can be read without a body. - An
Idempotency-Keyheader makes a retried paid call replay the first 200 instead of charging again (an answer larger than 1 MB is not replayed).
Paid call (JavaScript agent)
import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/core/client";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
const client = new x402Client();
client.setSpendControls?.(false); // keep your own spending ceiling in code
registerExactEvmScheme(client, { signer: privateKeyToAccount(KEY) });
const payFetch = wrapFetchWithPayment(fetch, client);
const res = await payFetch("https://agent402.tools/api/age", {
method: "POST",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({
"birthdate": "1990-05-20"
}),
});
No wallet? Pay with compute
Fetch a challenge, solve the sha256 puzzle (16 leading zero bits, a fraction of a second of CPU), and resend with the X-Pow-Solution header:
import { createHash } from "node:crypto";
const lz = (b) => { let t = 0; for (const x of b) { if (!x) { t += 8; continue; } t += Math.clz32(x) - 24; break; } return t; };
const c = await (await fetch("https://agent402.tools/api/pow/challenge?slug=age")).json();
let n = 0;
while (lz(createHash("sha256").update(c.challenge + ":" + n).digest()) < c.difficulty) n++;
await fetch("https://agent402.tools/api/age", { method: "POST", headers: { "X-Pow-Solution": c.token + ":" + n, "Content-Type": "application/json" }, body: JSON.stringify({"birthdate":"1990-05-20"}) });
Related tools
Date arithmetic
POST /api/add-timeAdd (or subtract) a duration to a date. duration like "2d", "-3h", "1w 2d", "90m". Returns the resulting UTC ISO timesta…
Business days
POST /api/business-daysCount business days (Mon–Fri) between two dates, inclusive of the start, exclusive of the end. Optional list of holiday …
Date difference
POST /api/date-diffDifference between two dates/times in ms, seconds, minutes, hours, days, and a human summary.
Relative time
POST /api/relative-timeFormat a timestamp as a human relative phrase ("3 hours ago", "in 2 days") versus now or a reference time.
Cron next runs
POST /api/cron-nextParse a 5-field cron expression and return the next N run times (UTC).
Duration parse/humanize
POST /api/durationParse a duration like "2h30m" / "1d4h" / "90s" to seconds, or humanize a number of seconds.