fittings-tz-offset-at

Original：🇺🇸 English

Translated

1 scripts

The UTC offset, abbreviation and DST state a zone was on at any moment from 1970, with the surrounding transitions, and resolution of ambiguous or nonexistent local times. Called as GET /v1/tz/offset-at, it takes timezone, instant, localTime and returns timezone, utcOffset, isDst, resolution. An agent scheduling or reconciling timestamps must know that 01:30 on a fall-back night happens twice and 02:30 on a spring-forward night never happens at all; fixed offset arithmetic silently books the wrong hour. Reading this schema and dry-running the call are free and need no wallet; a real call costs $0.004, paid in USDC on Base over x402.

1installs

Sourcefittings-sh/fittings

Added on2026-08-17

NPX Install

npx skill4agent add fittings-sh/fittings fittings-tz-offset-at

SKILL.md Content

View Translation Comparison →

Zone rules at an instant

tz.offset-at

on

https://fittings.sh

. One endpoint, deterministic compute.

The UTC offset, abbreviation and DST state a zone was on at any moment from 1970, with the surrounding transitions, and resolution of ambiguous or nonexistent local times.

The call

GET https://fittings.sh/v1/tz/offset-at

Field	Type	Required	Notes
`timezone`	string	yes	IANA zone, e.g. America/New_York
`instant`	string	no	ISO 8601 with an explicit Z or +HH:MM offset. Give this or localTime.
`localTime`	string	no	Wall-clock time with no offset, e.g. 2026-11-01T01:30:00. Give this or instant.

Example input:

json

{
  "timezone": "America/New_York",
  "localTime": "2026-11-01T01:30:00"
}

Cost and provenance


Price	$0.004
Source	none (pure compute over the runtime IANA tzdata)
Licence	none-needed

Why call it rather than answer from memory

An agent scheduling or reconciling timestamps must know that 01:30 on a fall-back night happens twice and 02:30 on a spring-forward night never happens at all; fixed offset arithmetic silently books the wrong hour.

Calling it

A skill is loaded on its own, so this document has to be enough by itself. It does not assume the general

fittings

skill is also loaded.

call.mjs

ships alongside this file; if it is missing (this document reached you without the rest of the skill), fetch it once with

curl -sO https://fittings.sh/skill/call.mjs

.

Free, and needs no wallet. Read the schema and see what a call would cost:

bash

curl -s https://fittings.sh/catalog/tz.offset-at | jq

Paying. The endpoint answers

402 Payment Required

with a signed quote, you sign an authorization, and a facilitator settles it — you never send a transaction and never pay gas. Before it spends anything, the client checks its own hash against the gateway and refuses rather than sign with logic the gateway has moved past:

bash

# Dry run. Prints the quote and pays nothing, because no key is set.
node call.mjs tz.offset-at timezone=America/New_York localTime=2026-11-01T01:30:00

# For real: a wallet holding USDC on Base, and nothing else.
export FITTINGS_PRIVATE_KEY=0x...
node call.mjs tz.offset-at timezone=America/New_York localTime=2026-11-01T01:30:00

Spending is never a side effect of curiosity: with no

FITTINGS_PRIVATE_KEY

the client fetches the quote and stops.

FITTINGS_MAX_PRICE

caps what it will pay without asking, and defaults to $0.05.

Use a throwaway wallet holding a few dollars, not a main one. The key sits in plaintext wherever the agent runs, and the whole cost of entry is USDC on Base — no account, no API key, and no ETH, because the payer signs off-chain and the facilitator broadcasts and pays the gas.

Writing your own client instead of using this one?

@x402/core

and

@x402/evm

on npm, and the

fittings

skill records the two things that cost real debugging time: the challenge is in a response header rather than the body, and it must be re-signed from the exact request being retried.

If this is not the right service,

https://fittings.sh/catalog/search?q=...

searches all of them for free.