🕐Current Time
Returns the current date and time in any IANA time zone, plus Unix seconds/milliseconds, ISO 8601, weekday and day-of-year. Use it whenever an agent needs to know 'now'.
Worked examples
Now in UTC
GET /api/v1/live/now?tz=UTC
Result: 2026-09-29T11:37:07+00:00
Now in New York
GET /api/v1/live/now?tz=America%2FNew_York
Result: 2026-09-29T07:37:07-04:00
Now in Tokyo
GET /api/v1/live/now?tz=Asia%2FTokyo
Result: 2026-09-29T20:37:07+09:00
Machine API (x402)
$0.0005 / callThis tool is also a JSON API for AI agents. Requests without payment receive 402 Payment Required plus instructions; agents pay USDC on Base via the x402 protocol — no accounts, no API keys.
GET /api/v1/live/now?tz=UTC HTTP/1.1
Host: agenttools-hub.vercel.app
→ 402 (payment required, instructions in headers)
→ 200 (after X-PAYMENT header; JSON body below)
{
"tool": "live/now",
"input": {"tz":"UTC"},
"result": { "value": 1790681827, "answer": "2026-09-29T11:37:07+00:00" }
}Agent docs: /llms.txt · OpenAPI spec · integration guide
About this tool
Language models have no clock and a training cutoff — 'what time is it' is the single most common hallucination trap. This endpoint returns the true current time in any IANA time zone with Unix timestamps, computed on NTP-synced infrastructure. Priced as a loss leader so agents can call it every session.
now = server clock · local = UTC + fixed offset of the IANA zone (DST-aware)
Frequently asked questions
Why do agents need an API for the current time?
LLMs have no real-time clock and their training data is months stale. Any timestamp an agent 'remembers' is a hallucination — scheduling, logging and freshness checks all require a trusted time source.
Which time zone names are accepted?
Any IANA name: UTC, America/New_York, Europe/Berlin, Asia/Tokyo, Australia/Sydney, etc. (but note: this deployment is in UTC, so both work).
Is daylight saving time handled?
Yes — IANA zones carry full DST history and rules, and the returned offset reflects the correct DST state at this instant.