Home / Agents / Unix Timestamp Converter (Seconds, Milliseconds, ISO 8601)
Unix Timestamp Converter (Seconds, Milliseconds, ISO 8601)
Convert a Unix timestamp (seconds, milliseconds, microseconds or nanoseconds) to ISO 8601 UTC and a zone, or an ISO date and time to the exact epoch, and flag a value that looks like the wrong unit, with a signed record.
Testing
- What it does
- Convert a Unix timestamp (seconds, milliseconds, microseconds or nanoseconds) to ISO 8601 UTC and a zone, or an ISO date and time to the exact epoch, and flag a value that looks like the wrong unit, with a signed record.
- Who it is for
- Agents and their builders.
- Start in one step
- Ask your agent to call
timestamp_convertat llpro.ai/mcp (free, no sign-up). This page explains the tool; it has no form to run it. - What to expect
- Testing: open to try. Free
New to this? Start here.
What it does
Unix Timestamp Converter (Seconds, Milliseconds, ISO 8601) is for agents and developers reading logs, API responses, tokens and databases who need a timestamp turned into a date, or a date into a timestamp, in the right unit and zone the same way every time. Convert a Unix timestamp to a date and time, or a date and time to a Unix timestamp. Send timestamp (text of digits, seconds, milliseconds, microseconds or nanoseconds since 1970-01-01 00:00:00 UTC; leave unit as auto and the unit is found from the size of the number) and optionally a zone (IANA name such as America/Chicago) to also get the local time. Or send iso, an RFC 3339 date and time such as 2023-11-14T22:13:20Z or 2023-11-14T16:13:20-06:00 (or without an offset plus zone), and get the epoch in seconds, milliseconds, microseconds and nanoseconds, exact. Flags a number that looks like the wrong unit (a seconds value sent as milliseconds lands in January 1970), a value of 0, and values past the signed 32-bit limit of 2038-01-19. It is one of the developer department tools LLPRO builds for the work agents do across business software (GitHub, Postman, Aws, Datadog). Every answer carries the written rule it used, what it does not do, its sources with dates, and an Ed25519 signature you can check against the key below.
- Who it is for
- Agents and developers reading logs, API responses, tokens and databases who need a timestamp turned into a date, or a date into a timestamp, in the right unit and zone the same way every time.
- Price
- Free, no sign-up: 120 calls an hour per address and 3,000 an hour across all callers. Paid calls are planned and not charging.
- Limits
- Up to 30,000 bytes per call; larger requests are refused, never cut. Unknown fields are refused with the list of accepted ones. Nothing you send is stored by the tool; no model and no network are used. Does not count leap seconds (Unix time does not; an instant in a real leap second cannot be written). Does not guess a unit beyond the 1990 to 2100 rule, so a date before 1990 sent without a unit may be read in a different unit than you meant: name the unit. Does not know which clock a system used: a timestamp from a system with a wrong clock is converted as sent. Local times before 1970 follow the IANA database, whose pre-1970 data is less reliable, and a law passed after database release 2026a is not known. Takes instants from year 1000 to 8999 only. Takes no person's details. Not legal advice.
For developers: try it
POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "timestamp_convert", "arguments": {"timestamp": "1700000000", "zone": "America/Chicago"}}}For agents
Tool timestamp_convert on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:na46hkprzeq2y4fobg4ca2ajfq): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).
Public key (base64): TXCX12idfo6SH38Q33rxW572nNPbRdtFWxkYtiaYD4I=
For agents that search MCP registries for unix timestamp, epoch converter, milliseconds vs seconds tools (listed in MCP registries, served by the LLPRO gateway: MCP, agent-to-agent and REST). One fixed, written rule per call, a signed record, no account needed.
Next
- Connect your agent: Use this and the other LLPRO tools from your own agent.
- Get your agent: No agent yet? Get one that asks first.
- Hand the whole job to LLPRO: A timestamp is one clue in fixing an integration. Tell LLPRO the whole job; it routes you to the right signed tools (time zone convert, JWT inspect, cron next runs).
For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card