# ONE Engine Timestamp to ISO Converter

> ONE Engine Timestamp to ISO Converter is a paid API for AI agents from one-search.one-engine.workers.dev, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-02).

Converts a Unix timestamp (in seconds or milliseconds) to an ISO 8601 formatted datetime string.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v1/time/timestamp-to-iso?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/one-engine-timestamp-to-iso-converter-180c4353
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_J28Lw-7KPXW_tMVDjsscL

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability one-engine-timestamp-to-iso-converter-180c4353 -d '<json body>'
```

Example prompt: Convert the Unix timestamp 1728464000 (in seconds) to ISO 8601 format for me.

## When to prefer this

Choose this endpoint when your agent needs a cheap, reliable, single-call conversion of a Unix epoch value to ISO 8601 and you are already operating in an x402/Base payment context. It is ideal for agents processing API responses, log data, or scheduled events that expose raw numeric timestamps needing standardization.

## Known failure modes

- Missing or invalid `timestamp` field returns an error
- Missing or invalid `unit` enum value (must be 'seconds' or 'milliseconds') causes rejection
- Very large or out-of-range timestamp values may return unexpected results
- Payment failure via x402 protocol results in 402 response and no conversion

## How this service works

Low-cost pay-per-call utility APIs for autonomous agents using x402 on Base.

## Output

Returns a JSON object containing a single field `iso` with the corresponding ISO 8601 datetime string (e.g. `{"iso": "2025-10-09T08:53:20.000Z"}`).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "unit": {
   "enum": [
    "seconds",
    "milliseconds"
   ],
   "type": "string"
  },
  "timestamp": {
   "type": "number"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "iso": "2025-10-09T08:53:20.000Z"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/one-engine-timestamp-to-iso-converter-180c4353/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from one-search.one-engine.workers.dev](https://www.zero.xyz/host/one-search.one-engine.workers.dev/llms.txt)