UTC instant to IANA time zones
Convert one explicit UTC instant into 1–10 IANA zone local times and exact UTC offsets, including the runtime's daylight-saving transitions. No wall-time guessing, current-clock lookup, recurrence or DST boolean. Runtime tzdb version is not exposed.
standards · Operation ID: timezone-convert
Choose this operation when
- Convert one supplied UTC instant to 1–10 local representations with second-accurate offsets under the installed runtime IANA data.
Outside this profile
- Resolve an ambiguous or nonexistent local wall time, infer a city or abbreviation, fetch current time, classify DST with a boolean, schedule recurring events, or guarantee historical/future political time-zone rules.
Exact release references
Static JSON contract · Markdown reference · Fixed example response
Complete input schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"profile": {
"type": "string",
"const": "utc-instant-iana-batch-v1"
},
"instant": {
"type": "string",
"minLength": 20,
"maxLength": 24,
"pattern": "^(?:19[7-9]\\d|20\\d{2}|2100)-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}(?:\\.\\d{1,3})?Z$"
},
"zones": {
"minItems": 1,
"maxItems": 10,
"type": "array",
"items": {
"type": "string",
"minLength": 1,
"maxLength": 64,
"pattern": "^(?:UTC|[A-Za-z][A-Za-z0-9._+-]*(?:\\/[A-Za-z0-9._+-]+)+)$"
}
}
},
"required": [
"profile",
"instant",
"zones"
],
"additionalProperties": false
}
Complete output-envelope schema
{
"type": "object",
"required": [
"operation",
"version",
"result",
"provenance"
],
"properties": {
"operation": {
"const": "timezone-convert",
"type": "string"
},
"version": {
"const": "0.29.0",
"type": "string"
},
"result": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"profile": {
"type": "string",
"const": "utc-instant-iana-batch-v1"
},
"instant": {
"type": "string",
"format": "date-time",
"pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$"
},
"epochMilliseconds": {
"type": "integer",
"minimum": -9007199254740991,
"maximum": 9007199254740991
},
"zoneCount": {
"type": "integer",
"minimum": 1,
"maximum": 10
},
"rulesSource": {
"type": "string",
"const": "runtime-intl-iana"
},
"tzdbVersion": {
"type": "null"
},
"dstPolicy": {
"type": "string",
"const": "offset-at-instant; no-heuristic-DST-classification"
},
"results": {
"minItems": 1,
"maxItems": 10,
"type": "array",
"items": {
"type": "object",
"properties": {
"requestedZone": {
"type": "string",
"maxLength": 64
},
"resolvedZone": {
"type": "string",
"maxLength": 64
},
"localDateTime": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}\\.\\d{3}$"
},
"utcOffset": {
"type": "string",
"pattern": "^[+-]\\d{2}:\\d{2}(?::\\d{2})?$"
},
"utcOffsetSeconds": {
"type": "integer",
"minimum": -86400,
"maximum": 86400
},
"zonedDateTime": {
"type": "string",
"maxLength": 110
}
},
"required": [
"requestedZone",
"resolvedZone",
"localDateTime",
"utcOffset",
"utcOffsetSeconds",
"zonedDateTime"
],
"additionalProperties": false
}
}
},
"required": [
"profile",
"instant",
"epochMilliseconds",
"zoneCount",
"rulesSource",
"tzdbVersion",
"dstPolicy",
"results"
],
"additionalProperties": false
},
"provenance": {
"type": "object",
"required": [
"inputSha256",
"outputSha256",
"deterministic",
"externalRequests"
],
"properties": {
"inputSha256": {
"type": "string",
"pattern": "^[a-f0-9]{64}$"
},
"outputSha256": {
"type": "string",
"pattern": "^[a-f0-9]{64}$"
},
"deterministic": {
"const": true
},
"externalRequests": {
"const": 0
}
}
}
},
"additionalProperties": false
}
Fixed example
One accepted fixed example, not a custom-input trial. No operation runs when this static page is requested.
Example input
{
"profile": "utc-instant-iana-batch-v1",
"instant": "2026-07-01T12:00:00Z",
"zones": [
"America/New_York",
"Europe/London",
"Asia/Kolkata",
"Pacific/Auckland"
]
}
Example response
{
"operation": "timezone-convert",
"version": "0.29.0",
"result": {
"profile": "utc-instant-iana-batch-v1",
"instant": "2026-07-01T12:00:00.000Z",
"epochMilliseconds": 1782907200000,
"zoneCount": 4,
"rulesSource": "runtime-intl-iana",
"tzdbVersion": null,
"dstPolicy": "offset-at-instant; no-heuristic-DST-classification",
"results": [
{
"requestedZone": "America/New_York",
"resolvedZone": "America/New_York",
"localDateTime": "2026-07-01T08:00:00.000",
"utcOffset": "-04:00",
"utcOffsetSeconds": -14400,
"zonedDateTime": "2026-07-01T08:00:00.000-04:00[America/New_York]"
},
{
"requestedZone": "Europe/London",
"resolvedZone": "Europe/London",
"localDateTime": "2026-07-01T13:00:00.000",
"utcOffset": "+01:00",
"utcOffsetSeconds": 3600,
"zonedDateTime": "2026-07-01T13:00:00.000+01:00[Europe/London]"
},
{
"requestedZone": "Asia/Kolkata",
"resolvedZone": "Asia/Calcutta",
"localDateTime": "2026-07-01T17:30:00.000",
"utcOffset": "+05:30",
"utcOffsetSeconds": 19800,
"zonedDateTime": "2026-07-01T17:30:00.000+05:30[Asia/Calcutta]"
},
{
"requestedZone": "Pacific/Auckland",
"resolvedZone": "Pacific/Auckland",
"localDateTime": "2026-07-02T00:00:00.000",
"utcOffset": "+12:00",
"utcOffsetSeconds": 43200,
"zonedDateTime": "2026-07-02T00:00:00.000+12:00[Pacific/Auckland]"
}
]
},
"provenance": {
"inputSha256": "599c99deae8e260cb7e847cb1c355c412a58e9ff9edb355b6e066d7edef1705a",
"outputSha256": "2badc1e493bca94a8e8ab528c7a960ccc6cde822748d705f5bab5e405bb5f6c8",
"deterministic": true,
"externalRequests": 0
}
}
Bounds and precision
JavaScript IEEE-754 numbers; use strings for large integer IDs/exact decimals where the schema accepts strings. No lossless numeric parsing.
{
"global": {
"requestBytes": 131072,
"responseBytes": 524288,
"jsonDepth": 32,
"jsonNodes": 20000,
"requestsPerMinute": 60,
"paidAttemptsPerMinute": 20,
"idempotencyHours": 24
},
"operation": {
"zones": 10,
"zoneCodeUnits": 64,
"outputBytes": 16000,
"earliestUtc": "1970-01-01T00:00:00.000Z",
"latestUtc": "2100-12-31T23:59:59.999Z",
"precision": "milliseconds",
"tzdbVersion": "not exposed; depends on runtime"
}
}
Complete schemas, descriptions and cross-field validation may impose additional limits.
Proposed price and protocol definitions
{
"unit": "one successful operation call",
"proposedNominalUsd": "0.003",
"sixDecimalTokenBaseUnits": "3000",
"subscription": false,
"includesPayerWalletOrNetworkFees": false,
"liveQuoteVerified": false,
"condition": "Actual SDK challenge is authoritative only within the caller's explicit authorization; configured six-decimal token peg is an operator assertion, not a conversion guarantee."
}
Protocol definitions: x402, mpp. MPP uses Tempo charge. Paid MCP execution is unsupported. All runtime readiness is not evaluated in this build.
API path templates, not endpoints on this documentation host
{
"x402": "/v1/x402/timezone-convert",
"mpp": "/v1/mpp/timezone-convert"
}
Required headers
{
"Content-Type": "application/json",
"Idempotency-Key": "random 16–128 character operation identifier"
}
Actual SDK challenge amount, asset, network, recipient and wallet costs must pass independent authorization. Preserve identical key, body, protocol and credential on retries; on PAYMENT_UNCERTAIN stop and reconcile.
Execution profile and provider conditions
{
"deterministic": true,
"externalRequests": 0,
"maxExternalRequests": 0,
"resultSnapshotPersisted": false,
"fixedExampleIsIllustrativeSnapshot": false,
"requiresPayment": true,
"supportsMcpExecution": false
}
Deterministic supplied-input operation with no external requests or stored request/result bodies. Payment infrastructure retains payment metadata and hashes.
Failure handling
- HTTP 400: Malformed JSON, missing/invalid idempotency key, or payment identifier mismatch Correct the request before payment
- HTTP 402: Payment challenge or rejected payment Use official protocol SDK; inspect payment outcome before another payment
- HTTP 409: Idempotency conflict, duplicate proof, or PAYMENT_UNCERTAIN Keep original key, body, and proof; reconcile uncertainty with operator; never blindly repay
- HTTP 413: Input or generated output too large Reduce input; no payment attempted for validation failure
- HTTP 415: Unsupported media type or compression Send uncompressed application/json
- HTTP 422: Schema or service-specific semantic validation failure Correct input using returned error code; no payment attempted
- HTTP 429: Request/payment-attempt rate exceeded Wait for rate limit window; preserve existing payment identity
- HTTP 503: Payment configuration/provider/state unavailable, or live DNS preparation failed before settlement Check readiness; DNS preparation failures may retry the identical key/body/credential only; uncertainty requires reconciliation
Declared requirements
Before any paid call, refresh the live operation contract and POST the complete bounded budgeted plan to the separate API's /preflight. Unknown requirements block selection; compatible preflight is not permission to spend.