# KEVAREMESH Timestamp Converter

> KEVAREMESH Timestamp Converter is a paid API for AI agents from kevaremesh-web.vercel.app, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-25).

Converts timestamps between ISO 8601 and Unix epoch formats (seconds or milliseconds), returning a normalized UTC representation.

## Facts

- Endpoint: POST https://kevaremesh-web.vercel.app/api/x402/timestamp-convert?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-25
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/kevaremesh-timestamp-converter-3cc9bc52
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_fRVIMHarMJxAxEqsOTn4d

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 kevaremesh-timestamp-converter-3cc9bc52 -d '<json body>'
```

Example prompt: Convert the ISO timestamp 2026-01-21T00:00:00Z to epoch seconds and milliseconds for me.

## When to prefer this

Use this endpoint when you need a simple, reliable timestamp format conversion between ISO 8601 and Unix epoch (seconds or milliseconds) with a normalized UTC output. It is well-suited for AI agents that process events from heterogeneous systems with inconsistent time formats and need a single canonical representation. Prefer it when you want both epoch and ISO representations returned together in one call without writing custom parsing logic.

## Known failure modes

- Missing or invalid 'value' field returns an error
- ISO input without explicit Z or numeric UTC offset may be rejected (noted in limitations)
- Unsupported input_type enum value causes validation failure
- Non-numeric string passed as epoch value will fail parsing
- Network or gateway unavailability returns a 5xx or payment-related 402 error

## How this service works

Buyer-first MCP procurement gateway that discovers, compares and routes live x402 APIs without making the buyer choose a provider.

## Output

Returns a JSON object containing the original input, the normalized ISO UTC string, epoch seconds, epoch milliseconds, detected timezone (UTC), input type, plus the service name, product identifier, a limitations note (ISO input requires explicit Z or numeric UTC offset), and a generated_at timestamp.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "value": {
   "type": [
    "string",
    "integer"
   ]
  },
  "input_type": {
   "enum": [
    "iso",
    "epoch_seconds",
    "epoch_milliseconds"
   ],
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {
   "input": "2026-01-21T00:00:00Z",
   "iso_utc": "2026-01-21T00:00:00.000Z",
   "timezone": "UTC",
   "input_type": "iso",
   "epoch_seconds": 1768953600,
   "epoch_milliseconds": 1768953600000
  },
  "product": "kevaremesh_timestamp_convert_v2",
  "service": "KEVAREMESH",
  "tool_name": "kevaremesh_timestamp_convert",
  "limitations": [
   "ISO input requires an explicit Z or numeric UTC offset"
  ],
  "generated_at": "2026-09-18T00:00:00.000Z"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/kevaremesh-timestamp-converter-3cc9bc52/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from kevaremesh-web.vercel.app](https://www.zero.xyz/host/kevaremesh-web.vercel.app/llms.txt)