# FastX402 Epoch Convert

> FastX402 Epoch Convert is a paid API for AI agents from fastx402.tools, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-30).

Converts a Unix epoch timestamp (seconds or milliseconds) or ISO 8601 date string into multiple human-readable and machine-readable datetime formats

## Facts

- Endpoint: GET https://fastx402.tools/epoch-convert?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-30
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/fastx402-epoch-convert-d4801fe2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ENIWDBC2nCHvD90gUiBzz

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 fastx402-epoch-convert-d4801fe2
```

Example prompt: What date and time does the Unix timestamp 1729267200 correspond to? Give me the ISO 8601 string and a readable UTC description.

## When to prefer this

Use this endpoint when you need a quick, no-account, pay-per-call conversion of Unix epoch timestamps (seconds or milliseconds) or ISO 8601 strings into multiple datetime representations including human-readable UTC. Ideal for AI agents processing API responses, log files, or database records containing raw epoch values and needing to present them in a human-friendly format.

## Known failure modes

- Missing or malformed 'timestamp' query parameter returns an error
- Non-numeric, non-ISO string that cannot be parsed as a date returns a parse error
- Out-of-range epoch values may return unexpected results
- Payment failure (HTTP 402) if USDC balance is insufficient

## How this service works

200 pay-per-call tools for AI agents, from $0.001 per request in USDC on Base or Solana with x402. No account, no API key.

## Output

Returns a JSON object containing the original input value, the ISO 8601 datetime string (e.g. '2024-10-18T16:00:00.000Z'), a human-readable UTC string (e.g. 'Friday, October 18, 2024 at 16:00:00 UTC'), the epoch in seconds as an integer, and the epoch in milliseconds as an integer.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "timestamp"
     ],
     "properties": {
      "timestamp": {
       "type": "string",
       "description": "Unix epoch seconds or milliseconds, or ISO 8601 date string"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "properties": {
      "input": {
       "type": "string"
      },
      "iso8601": {
       "type": "string"
      },
      "human_utc": {
       "type": "string"
      },
      "epoch_seconds": {
       "type": "integer"
      },
      "epoch_milliseconds": {
       "type": "integer"
      }
     }
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "input": "1729267200",
  "iso8601": "2024-10-18T16:00:00.000Z",
  "human_utc": "Friday, October 18, 2024 at 16:00:00 UTC",
  "epoch_seconds": 1729267200,
  "epoch_milliseconds": 1729267200000
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/fastx402-epoch-convert-d4801fe2/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from fastx402.tools](https://www.zero.xyz/host/fastx402.tools/llms.txt)