# Delx MS To HMS

> Delx MS To HMS is a paid API for AI agents from api.delx.ai, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-13).

Converts a millisecond integer value into a human-readable HH:MM:SS string along with individual time parts

## Facts

- Endpoint: POST https://api.delx.ai/api/v1/x402/ms-to-hms
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delx-ms-to-hms-818a1e43
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_29o8iK99QH3NMwNtYH5V7

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 delx-ms-to-hms-818a1e43 -d '<json body>'
```

Example prompt: Convert 5432100 milliseconds into HH:MM:SS format so I can display the task duration nicely for the user.

## When to prefer this

Choose this endpoint when you need to display a millisecond duration as a human-readable HH:MM:SS string — especially in agent pipelines that report task durations, media lengths, or elapsed times to end users. It is a stateless, local computation with no external calls or data retention, making it safe and fast for formatting-only needs. Prefer it over writing custom conversion logic when you want a reliable, pre-built micro-utility with structured output including individual time parts.

## Known failure modes

- Missing or non-integer 'ms' field returns a validation error
- Negative millisecond values may be rejected or produce unexpected output
- Extremely large integer values beyond safe bounds may cause errors
- Network or payment (x402) failure results in no response

## How this service works

Convert milliseconds to HH:MM:SS. Call when you format agent durations for humans. Returns hms string and parts for $0.001 USDC via x402 on Base. No network, no keys, no retention; first-party local JSON only. Results are advisory; the caller owns budgets, auth, and production controls.

## Output

Returns a JSON object containing the formatted HH:MM:SS string representation of the input milliseconds, along with the individual numeric parts (hours, minutes, seconds) for further use in formatting or calculations.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "ms": {
   "type": "integer",
   "description": "Input field: ms."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ms": 61001,
  "hms": "00:01:01",
  "hours": 0,
  "schema": "delx/util-ms-to-hms/v1",
  "minutes": 1,
  "seconds": 1
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-ms-to-hms-818a1e43/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.delx.ai](https://www.zero.xyz/host/api.delx.ai/llms.txt)
