Which timestamps are anchored? Flags naive local times, zone abbreviations, date-only, epoch units and d/m ambiguity
Classifies up to 200 timestamp strings as anchored (RFC 3339 with Z or offset), naive local (no offset), date-only, epoch seconds or milliseconds, zone abbreviation, ambiguous numeric date, or unparseable, and lists the hazard of each; with assumedTimeZone it also reports whether a naive time falls in a DST gap or overlap there, every instant it could mean, and offsets that contradict the zone. Built for an agent about to store, compare or schedule timestamps it was handed. It reports hazards and candidates; it never picks a zone for you and never reads the clock.
What you get
A timestamp without an offset is a bug waiting for a deploy in another zone.
Call it
Send the JSON body below to https://agents.writerslogic.com/api/v1/naive-timestamp-hazard. An unpaid request answers 402 with the price and how to pay; a request that fails with a 5xx status is not charged.
curl -i -X POST https://agents.writerslogic.com/api/v1/naive-timestamp-hazard \
-H 'content-type: application/json' \
-d '{"timestamps":["2026-03-08T02:30:00","2026-07-01T12:00:00+01:00","03/04/2026","1793836800"],"assumedTimeZone":"America/New_York"}'
Input
| Field | Type | Required | Description |
|---|---|---|---|
timestamps | array<string; length 0..64>; max 200 items | yes | |
assumedTimeZone | string; length 0..64 | no | IANA zone the producer is believed to use; used for gap/overlap and offset-consistency checks. |
Example request body
{
"timestamps": [
"2026-03-08T02:30:00",
"2026-07-01T12:00:00+01:00",
"03/04/2026",
"1793836800"
],
"assumedTimeZone": "America/New_York"
}
Result
The response is { "data": ..., "_provenance": ... }. data carries these fields; _provenance is a signed W3C Verifiable Credential with a C2PA-style manifest, checked free at POST /api/v1/verify-provenance.
| Field | Type | Required | Description |
|---|---|---|---|
status | string; one of "pass", "fail", "unknown", "unsupported" | no | pass: every rule held. fail: a rule was violated (see witnesses). unknown: the input lacks the evidence to decide. unsupported: outside what this engine covers. Missing evidence is never a pass. |
items | array<object> | no | |
anchoredCount | integer | no | |
witnesses | array<object> | no | |
versions | object | no | Every semantic dependency of this answer (engine, tables and their as-of dates, tokenizer, calendar, rounding profile). |
limits | array<string> | no | |
deterministic | boolean | no | Always true: pure code, no model. |
Pay and connect
Available through: x402 (USDC on Base), MCP. MCP clients reach it through the calendar-deadline-kit package.
Machine-readable
- This agent as JSON (schemas, example, OpenAPI operation)
- Free signed sample response
- OpenAPI 3.1 · Catalog · Index of every agent