The timestamp tool converts between time formats: Unix epoch, ISO 8601, RFC 2822, and human-readable strings. It handles timezone conversions and relative time calculations. Agents use it for log timestamp normalization, scheduling, expiration checks, and cross-timezone coordination. It's stateless, free, and responds in under 5ms.
POST /api/v1/utils/timestamp| Name | Type | Required | Description |
|---|---|---|---|
| input | string | No | Timestamp to convert. Accepts Unix epoch (seconds or milliseconds), ISO 8601, or natural language. Defaults to current time. |
| timezone | string | No | Target timezone (IANA format, e.g., America/New_York). |
| format | string | No | Output format: iso, unix, human, rfc2822. |
POST /api/v1/utils/timestamp {}Returns current time in all formats when called with no arguments.
POST /api/v1/utils/timestamp {"input": "1773687000", "timezone": "America/New_York"}Converts a Unix timestamp to Eastern time with proper DST handling.
The tool auto-detects input format. Unix epoch in seconds (10 digits) and milliseconds (13 digits) are both supported. ISO 8601 with or without timezone offset. RFC 2822 email date format. Human-readable strings like 'March 14, 2026' or 'yesterday' or '2 hours ago'. If the format is ambiguous (like 03/04/2026), the tool assumes MM/DD/YYYY.
Yes. The tool uses the IANA timezone database and correctly handles DST transitions. Specify the IANA timezone name (e.g., America/New_York, not EST) for accurate results.
Yes. Inputs like '2 hours ago', 'yesterday', 'next Monday', and 'in 30 minutes' are supported. Relative times are calculated from the current server time.
Yes. Free utility tool, no API key required.
The tool handles dates from 1970-01-01 to 2099-12-31. Dates outside this range return an error.
delx utils timestamp "2026-03-14" --timezone Asia/Tokyo. Outputs the converted timestamp in all formats.