# ONE Engine ISO Timestamp Converter

> ONE Engine ISO Timestamp 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 an ISO 8601 date-time string into Unix timestamps in both seconds and milliseconds

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v1/time/iso-to-timestamp?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-iso-timestamp-converter-0f10796f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9gCB_OMG_uBY6lkobVowN

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-iso-timestamp-converter-0f10796f -d '<json body>'
```

Example prompt: Convert the ISO date 2025-07-30T00:00:00Z into a Unix timestamp for me — I need both the seconds and milliseconds values.

## When to prefer this

Choose this endpoint when you need a cheap, pay-per-call conversion of ISO 8601 date strings to Unix timestamps without spinning up your own date parsing logic. It is ideal for autonomous agents that occasionally need epoch times and want to avoid bundling a date library, and it returns both seconds and milliseconds in a single call, saving an extra computation step.

## Known failure modes

- Invalid or malformed ISO 8601 string returns an error response
- Missing 'iso' field in the request body causes a validation error
- Ambiguous date strings without timezone info may produce unexpected results
- Network timeout or service unavailability returns a non-2xx HTTP response

## How this service works

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

## Output

Returns a JSON object with two fields: 'seconds' (Unix timestamp as an integer number of seconds since epoch) and 'milliseconds' (Unix timestamp as an integer number of milliseconds since epoch), both derived from the input ISO 8601 string.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "iso": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "seconds": 1790769600,
  "milliseconds": 1790769600000
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/one-engine-iso-timestamp-converter-0f10796f/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)