DST hazards for hourly and daily buckets in a zone: skipped hours, repeated hours, 23- and 25-hour days
For a time zone and a date range of up to 1100 days, lists every offset transition and what it does to local bucketing: the hourly labels that never occur (spring-forward), the hourly labels that occur twice and would merge two real hours when grouped by local time (fall-back), and the 23-, 24.5- or 25-hour days; optionally checks up to 500 caller hourly labels (YYYY-MM-DDTHH:00) for non-existent or ambiguous ones. Built for an agent aggregating metrics, billing or schedules by local hour or day. It does not bucket your data or choose a policy (bucket by UTC instead is the safe default).
What you get
Hourly dashboards and daily billing silently double-count or drop an hour twice a year per zone.
Call it
Send the JSON body below to https://agents.writerslogic.com/api/v1/time-bucket-check. 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/time-bucket-check \
-H 'content-type: application/json' \
-d '{"timeZone":"America/New_York","from":"2026-01-01","to":"2026-12-31","labels":["2026-03-08T02:00","2026-11-01T01:00","2026-06-01T12:00"]}'
Input
| Field | Type | Required | Description |
|---|---|---|---|
timeZone | string; length 0..64 | yes | |
from | string; length 0..10 | yes | First local date, inclusive. |
to | string; length 0..10 | yes | Last local date, inclusive. |
labels | array<string; length 0..30>; max 500 items | no | Local hour labels to check, e.g. 2026-03-08T02:00. |
Example request body
{
"timeZone": "America/New_York",
"from": "2026-01-01",
"to": "2026-12-31",
"labels": [
"2026-03-08T02:00",
"2026-11-01T01:00",
"2026-06-01T12:00"
]
}
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. |
transitions | array<object> | no | |
labelProblems | array<object> | 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