time-convert

Convert between epoch (s or ms), ISO 8601, and any IANA timezone.

Convert between epoch (s or ms), ISO 8601, and any IANA timezone. Give a value (epoch seconds or milliseconds, an ISO string, or 'now'), get every representation back: utc, epochSeconds, epochMillis and, with tz, timezone, localIso (ISO 8601 with the zone's offset, e.g. 2026-06-11T19:00:00+09:00), utcOffset and local (a display string). A bare number under 1e12 is read as seconds, otherwise as milliseconds.

UNRATEDListed

Overview

Grade?

UNRATED

0 of 30 paid calls toward a letter

Price

$0.001 per call

Paid calls

none yet

delivery unknown until someone pays

More info

Seller?

0x77065d81…16744121

URL

https://agent402.tools/api/time-convert

MCP server on this host: io.github.MikeyPetrillo/agent402

Seen

first 34 days ago · last 12 hr ago

64 free handshakes

Payment

Pays through

x402 · MPP evm, tempo

Offered on?

algorand:wGHE2Pwdvd7S12BL5FaOP20EGYesN73ktiC1qzkkit8=, eip155:10, eip155:1329, Polygon, eip155:143, Arbitrum, eip155:42220, Avalanche, Robinhood Chain, Base USDC, Solana, stellar:pubnet, Tempo USDC.e

Listed on?

Polygon, Arbitrum, Avalanche, Base, Solana

Handshakescomputed 1 day ago

0.734 from 56 free handshakes over 30 days · UNRATED ?

How the composite of 0.734 is made up, part by part
Component	Weight	Measured	Lower bound ?		Adds	Short ?	Uncertain ?
latency p95costs the most it answered as fast as its class	0.20	0.00	0.000		0.000	−0.200	0
liveness it answered at all	0.60	1.00	0.890		0.534	0	−0.066
price stability the price stayed where it was listed	0.20	1.00	1.000		0.200	0	0
Composite	1.00		0.734	gap to 1.000 = 0.266 · 0.200 short · 0.066 uncertain	0.734	−0.200	−0.066

Not measured: correctness · nobody paid; honesty · nobody paid; schema conformance · no answer had a published shape to check

BURN_INFREE_TIER_ONLY

Verify it yourselfnpx teppi-check https://agent402.tools/api/time-convertcurl -s https://api.teppi.xyz/v1/trust/cap_01M1A59KM2PVV9TM9Y1K3SD6P0