# JSON Timestamp Fields Check

> JSON Timestamp Fields Check 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-15).

Validates selected fields in a JSON object as integer epoch seconds, checking they fall within caller-supplied minimum and maximum bounds, and returns counts, normalized values, and a versioned result contract.

## Facts

- Endpoint: POST https://api.delx.ai/api/v1/x402/json-timestamp-fields-check
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/json-timestamp-fields-check-b64ccc1c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ugDjzUNPcPbbj82l4QcsS

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 json-timestamp-fields-check-b64ccc1c -d '<json body>'
```

Example prompt: Before passing this order payload to the fulfillment API, check that the fields 'created_at' and 'expires_at' are valid integer epoch seconds between 1700000000 and 1800000000 — here's the object: {"order_id": "abc", "created_at": 1712345678, "expires_at": 1812345678}.

## When to prefer this

Use this endpoint when you need a deterministic, bounded, in-memory check of integer epoch second timestamps across multiple fields of a JSON object before passing structured data to a downstream system with a strict contract. It is especially useful in agentic pipelines where you want a versioned, auditable validation result without retaining or externalizing the data. Prefer it over generic JSON schema validators when epoch-second bounds checking per named field is the specific requirement.

## Known failure modes

- Field names in 'fields' array do not exist in the provided object — fields will be counted as invalid or missing
- Non-integer values in timestamp fields cause validation failures
- minimum_epoch greater than maximum_epoch causes undefined or error response
- Object exceeds maxProperties limit of 128 — request rejected
- Fields array exceeds maxItems limit of 256 — request rejected
- Network or payment failure returns HTTP 402 or connection error

## How this service works

JSON Timestamp Fields Check: JSON Timestamp Fields Check checks selected fields as integer epoch seconds within bounds from bounded caller-supplied values without an external provider. Call JSON Timestamp Fields Check before an agent hands structured data or a batch plan to a downstream tool with a stricter contract. Returns the bounded transformation or validation finding with counts, normalized values, and a versioned result contract for JSON Timestamp Fields Check as versioned deterministic…

## Output

Returns a versioned deterministic result containing: validation finding (pass/fail per field), counts of valid and invalid fields, normalized epoch values for each checked field, and a versioned result contract describing the schema of the response.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "fields": {
   "type": "array",
   "items": {
    "type": "string",
    "maxLength": 8192
   },
   "maxItems": 256,
   "description": "Fields supplied to JSON Timestamp Fields Check; used only for this bounded calculation and processed in memory without retention."
  },
  "object": {
   "type": "object",
   "description": "Object supplied to JSON Timestamp Fields Check; used only for this bounded calculation and processed in memory without retention.",
   "maxProperties": 128,
   "additionalProperties": true
  },
  "maximum_epoch": {
   "type": "integer",
   "description": "Maximum Epoch supplied to JSON Timestamp Fields Check; used only for this bounded calculation and processed in memory without retention."
  },
  "minimum_epoch": {
   "type": "integer",
   "description": "Minimum Epoch supplied to JSON Timestamp Fields Check; used only for this bounded calculation and processed in memory without retention."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {
   "passed": true,
   "invalid_fields": []
  },
  "schema": "delx/util-json-timestamp-fields-check/v1",
  "status": "pass",
  "evidence": {
   "retained": false,
   "input_sha256": "c12d2ec16714eac59b617fadcb92ec5fbee3fc2095362925f77691ae25cca0ee",
   "external_calls": 0
  },
  "operation": "data_batch:json_timestamp_fields_check"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/json-timestamp-fields-check-b64ccc1c/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)