Geo Data time zone and local time API
Use the Geo Data time zone and local time API to retrieve time-zone information, local date and time and geographic position as structured JSON from Geo Data. Choose coordinates, longitude and search words as optional query conditions to select the source records or view required for your request. Use these results to resolve local clock information and account for time-zone changes when scheduling across locations. The detail page includes parameter definitions, paired request and response examples, and usage pricing for this operation.
- Selected price
- $0.002 / billing creditPublished pricing
- Sellers / implementations
- 1 / 1
- Requests · 30d
- —Loading...
- Success rate · 30d
- —Loading...
| Seller | Pricing | Requests · 30d | Performance | Access |
|---|---|---|---|---|
apishCurrent Geo Data time zone and local time API · GET · View API reference | $0.002 / billing credit | — | —successP50— |
Run sends a real API request. Charges follow the published API contract.
Response structure
abbreviationstringattributionstringcachedbooleancredits_usedintegerdst_offsetnullfetched_atstringis_dstbooleanlatnumberlocal_timestringlocationobjectadmin1stringadmin1_codestringadmin2stringascii_namestringcountrystringcountry_codestringdistance_kmnumberelevation_mintegerfeaturestringfeature_codestringgeonameidintegerlatnumberlonnumbernamestringpopulationintegertimezonestring
lonnumberobserves_dstbooleanqueryobjectlatnumberlonnumber
standard_offsetstringtimezonestringutc_offsetstringutc_offset_minutesintegerutc_timestring
// Inferred from response examples. Fields are optional and other fields may be returned.
export type ApiResponse = {
abbreviation?: string;
attribution?: string;
cached?: boolean;
credits_used?: number;
dst_offset?: null;
fetched_at?: string;
is_dst?: boolean;
lat?: number;
local_time?: string;
location?: {
admin1?: string;
admin1_code?: string;
admin2?: string;
ascii_name?: string;
country?: string;
country_code?: string;
distance_km?: number;
elevation_m?: number;
feature?: string;
feature_code?: string;
geonameid?: number;
lat?: number;
lon?: number;
name?: string;
population?: number;
timezone?: string;
};
lon?: number;
observes_dst?: boolean;
query?: {
lat?: number;
lon?: number;
};
standard_offset?: string;
timezone?: string;
utc_offset?: string;
utc_offset_minutes?: number;
utc_time?: string;
};- Method
- GET
- Endpoint
https://api.openany.si/v1/agent-apis/apish/geo/v1/timezone- Content type
- application/json
- Authentication
Authorization: Bearer $OPENANY_API_KEY
curl \
'https://api.openany.si/v1/agent-apis/apish/geo/v1/timezone?lat=35.6762&lon=139.6503&output=json&raw=0' \
-X GET \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json'Input parameters
Fields in this listing; additional options and input encoding can vary by provider.
| Parameter | Location | Type | Required | Description |
|---|---|---|---|---|
lat | URL query parametersquery | number | No | Latitude (-90 to 90). Pass with `lon`; or use `q`, `postal_code` or `geonameid` instead. |
lon | URL query parametersquery | number | No | Longitude (-180 to 180). |
q | URL query parametersquery | string | No | Place name in any language, optionally with region and country: `Paris`, `Springfield, IL, US`, `München`. The most populous match wins (towns of 1,000+ people). |
postal_code | URL query parametersquery | string | No | Postal code, with `country` (default US): `10001`, `SW1A 1AA` + `country=GB`. |
country | URL query parametersquery | string | No | Country for `q` or `postal_code`: ISO code (`US`, `GB`, `DE`) or English name. |
raw | URL query parametersquery | string | No | 0 leaves out the bulky `raw` source blocks (often 10-30x smaller). enum: "0", "1" |
fields | URL query parametersquery | string | No | Comma-separated fields to return, e.g. `posts.id,posts.title`. Call metadata is always included. |
fresh | URL query parametersquery | string | No | 1 skips the 24-hour cache and fetches live. enum: "1" |
output | URL query parametersquery | string | No | JSON only for this OpenAny product. Omit output or use json; CSV and NDJSON are not supported. enum: "json" |
records | URL query parametersquery | string | No | With output=csv|ndjson: the top-level list to turn into rows (e.g. `reviews`), or `.` for the whole object as one row. |
Required markers inside a nested object or variant apply when that object or variant is used.
Sample response
Sample response · Documented HTTP 200 Example from the provider's documentation. Field values in your results will differ.
{
"abbreviation": "GMT+9",
"attribution": "Place data: GeoNames (geonames.org), CC BY 4.0",
"cached": false,
"credits_used": 1,
"dst_offset": null,
"fetched_at": "2026-11-19T12:26:41.894Z",
"is_dst": false,
"lat": 35.6762,
"local_time": "2026-11-19T21:26:41+09:00",
"location": {
"admin1": "Tokyo",
"admin1_code": "40",
"admin2": "Suginami-ku",
"ascii_name": "Eifuku",
"country": "Japan",
"country_code": "JP",
"distance_km": 0.9,
"elevation_m": 46,
"feature": "section of a populated place",
"feature_code": "PPLX",
"geonameid": 8573723,
"lat": 35.6755,
"lon": 139.63992,
"name": "Eifuku",
"population": 15709,
"timezone": "Asia/Tokyo"
},
"lon": 139.6503,
"observes_dst": false,
"query": {
"lat": 35.6762,
"lon": 139.6503
},
"standard_offset": "+09:00",
"timezone": "Asia/Tokyo",
"utc_offset": "+09:00",
"utc_offset_minutes": 540,
"utc_time": "2026-11-19T12:26:41Z"
}Composite rule pricing
Calculated from input parameters and actual returned quantities. Estimate the maximum cost before calling.
Base fee: $0.000000. One matching variant replaces the base fee. Matching add-ons and quantity charges are added.
| Fee item | Price | Metering source | When | Quantity limit |
|---|---|---|---|---|
| Actual API.SH credits consumed | $0.002000 / billing credit | Response · /credits_used · Numeric value | Always | 1 billing credit · Decimal places: 0 |
Each quantity charge is rounded before summing: ceil. Requests exceeding this cost limit are rejected; it is not a price cap: $0.002000.
Response quantities settle after the response. Before execution, the maximum quantity determines the reservation; unused reservation is released. Missing or invalid quantities are not treated as zero.
Pricing parameters and defaults
[]
Agent integration
Copy the resource contract without sharing an API key.
View API Markdown
# Geo Data time zone and local time API
Use the Geo Data time zone and local time API to retrieve time-zone information, local date and time and geographic position as structured JSON from Geo Data. Choose coordinates, longitude and search words as optional query conditions to select the source records or view required for your request. Use these results to resolve local clock information and account for time-zone changes when scheduling across locations. The detail page includes parameter definitions, paired request and response examples, and usage pricing for this operation.
Documentation: https://openany.si/apis/94dc9b66-8fce-4bfc-a58f-33e199a00a4c
Method: GET
Endpoint: https://api.openany.si/v1/agent-apis/apish/geo/v1/timezone
Price: $0.002 / billing credit
Provider: apish
Contract revision: 2
Price source: OpenAny public API contract and documented provider unit rates. Price update time: not supplied.
Use OPENANY_API_KEY from the environment. API Key calls use your shared balance.
## Prepared request
```bash
curl \
'https://api.openany.si/v1/agent-apis/apish/geo/v1/timezone?lat=35.6762&lon=139.6503&output=json&raw=0' \
-X GET \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json'
```
## API contract
```json
{
"resource_type": "api",
"name": "Geo Data time zone and local time API",
"endpoint": "https://api.openany.si/v1/agent-apis/apish/geo/v1/timezone",
"method": "GET",
"content_type": "none",
"execution_mode": "sync",
"authentication": {
"type": "bearer",
"environment_variable": "OPENANY_API_KEY"
},
"inputs": [
{
"description": "Latitude (-90 to 90). Pass with `lon`; or use `q`, `postal_code` or `geonameid` instead.",
"location": "query",
"name": "lat",
"nullable": false,
"required": false,
"type": "number"
},
{
"description": "Longitude (-180 to 180).",
"location": "query",
"name": "lon",
"nullable": false,
"required": false,
"type": "number"
},
{
"description": "Place name in any language, optionally with region and country: `Paris`, `Springfield, IL, US`, `München`. The most populous match wins (towns of 1,000+ people).",
"location": "query",
"name": "q",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "Postal code, with `country` (default US): `10001`, `SW1A 1AA` + `country=GB`.",
"location": "query",
"name": "postal_code",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "Country for `q` or `postal_code`: ISO code (`US`, `GB`, `DE`) or English name.",
"location": "query",
"name": "country",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "0 leaves out the bulky `raw` source blocks (often 10-30x smaller).",
"enum_values": [
"0",
"1"
],
"location": "query",
"name": "raw",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "Comma-separated fields to return, e.g. `posts.id,posts.title`. Call metadata is always included.",
"location": "query",
"name": "fields",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "1 skips the 24-hour cache and fetches live.",
"enum_values": [
"1"
],
"location": "query",
"name": "fresh",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "JSON only for this OpenAny product. Omit output or use json; CSV and NDJSON are not supported.",
"enum_values": [
"json"
],
"location": "query",
"name": "output",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "With output=csv|ndjson: the top-level list to turn into rows (e.g. `reviews`), or `.` for the whole object as one row.",
"location": "query",
"name": "records",
"nullable": false,
"required": false,
"type": "string"
}
],
"billing": {
"currency": "USD",
"mode": "rules",
"parameters": [],
"policy_version": 2,
"sale": {
"addons": [],
"base_price_micro_usd": "0",
"max_cost_micro_usd": "2000",
"quantities": [
{
"id": "upstream_credits",
"label": "Actual API.SH credits consumed",
"max_quantity": "1",
"measure": "value",
"pointer": "/credits_used",
"price_micro_usd": "2000",
"quantity_scale": 0,
"source": "response",
"unit": "credit",
"unit_quantity": "1"
}
],
"rounding": "ceil",
"variants": []
}
},
"examples": [
{
"http_status": 200,
"name": "Official example · Live API.SH response · Minimal request",
"request": {
"body": null,
"headers": {},
"path": {},
"query": {
"lat": "35.6762",
"lon": "139.6503",
"output": "json",
"raw": "0"
}
},
"response_body": {
"abbreviation": "GMT+9",
"attribution": "Place data: GeoNames (geonames.org), CC BY 4.0",
"cached": false,
"credits_used": 1,
"dst_offset": null,
"fetched_at": "2026-11-19T12:26:41.894Z",
"is_dst": false,
"lat": 35.6762,
"local_time": "2026-11-19T21:26:41+09:00",
"location": {
"admin1": "Tokyo",
"admin1_code": "40",
"admin2": "Suginami-ku",
"ascii_name": "Eifuku",
"country": "Japan",
"country_code": "JP",
"distance_km": 0.9,
"elevation_m": 46,
"feature": "section of a populated place",
"feature_code": "PPLX",
"geonameid": 8573723,
"lat": 35.6755,
"lon": 139.63992,
"name": "Eifuku",
"population": 15709,
"timezone": "Asia/Tokyo"
},
"lon": 139.6503,
"observes_dst": false,
"query": {
"lat": 35.6762,
"lon": 139.6503
},
"standard_offset": "+09:00",
"timezone": "Asia/Tokyo",
"utc_offset": "+09:00",
"utc_offset_minutes": 540,
"utc_time": "2026-11-19T12:26:41Z"
}
}
]
}
```Error handling
| Status | Next step |
|---|---|
400 | Check the offering and request fields. |
401 / 403 | Verify your credentials and access permissions. |
402 | Inspect the selected access mode and returned payment requirements. |
429 | Respect the returned rate limit and retry guidance. |
5xx | Inspect the error and usage record before retrying a paid operation. |
Official example · Live API.SH response · Minimal request
Example from the provider's documentation. Field values in your results will differ.
Prepare your environment
Use a terminal with cURL installed.
Use an OpenAny API key with shared-balance access. Confirm availability and price before running; a call may charge your balance.
Set the key in your terminal using the hidden prompt below. Keep its value out of source files and logs.
Terminal · macOS / Linuxprintf 'OpenAny API key: ' read -r -s OPENANY_API_KEY export OPENANY_API_KEY printf '\n'Run the request
Paste the complete command below into your terminal.
Values to replace before running 10
Review these request fields before running. Keep the published provider and request method unchanged.
lat- Latitude (-90 to 90). Pass with `lon`; or use `q`, `postal_code` or `geonameid` instead.
lon- Longitude (-180 to 180).
q- Place name in any language, optionally with region and country: `Paris`, `Springfield, IL, US`, `München`. The most populous match wins (towns of 1,000+ people).
postal_code- Postal code, with `country` (default US): `10001`, `SW1A 1AA` + `country=GB`.
country- Country for `q` or `postal_code`: ISO code (`US`, `GB`, `DE`) or English name.
raw- 0 leaves out the bulky `raw` source blocks (often 10-30x smaller).
fields- Comma-separated fields to return, e.g. `posts.id,posts.title`. Call metadata is always included.
fresh- 1 skips the 24-hour cache and fetches live.
output- JSON only for this OpenAny product. Omit output or use json; CSV and NDJSON are not supported.
records- With output=csv|ndjson: the top-level list to turn into rows (e.g. `reviews`), or `.` for the whole object as one row.
Terminal · cURLcurl \ 'https://api.openany.si/v1/agent-apis/apish/geo/v1/timezone?lat=35.6762&lon=139.6503&output=json&raw=0' \ -X GET \ -H "Authorization: Bearer $OPENANY_API_KEY" \ -H 'Content-Type: application/json'Check the response
Sample response · Documented HTTP 200
Sample response{ "abbreviation": "GMT+9", "attribution": "Place data: GeoNames (geonames.org), CC BY 4.0", "cached": false, "credits_used": 1, "dst_offset": null, "fetched_at": "2026-11-19T12:26:41.894Z", "is_dst": false, "lat": 35.6762, "local_time": "2026-11-19T21:26:41+09:00", "location": { "admin1": "Tokyo", "admin1_code": "40", "admin2": "Suginami-ku", "ascii_name": "Eifuku", "country": "Japan", "country_code": "JP", "distance_km": 0.9, "elevation_m": 46, "feature": "section of a populated place", "feature_code": "PPLX", "geonameid": 8573723, "lat": 35.6755, "lon": 139.63992, "name": "Eifuku", "population": 15709, "timezone": "Asia/Tokyo" }, "lon": 139.6503, "observes_dst": false, "query": { "lat": 35.6762, "lon": 139.6503 }, "standard_offset": "+09:00", "timezone": "Asia/Tokyo", "utc_offset": "+09:00", "utc_offset_minutes": 540, "utc_time": "2026-11-19T12:26:41Z" }
Loading related APIs…
Common questions
Do I need a separate key for every provider?
Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.
Are these providers interchangeable?
No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.
How is this API billed?
API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.
Where do the price and contract come from?
The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.
How do OpenAny Balance and x402 differ?
OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.
Does Playground send a paid request?
Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.
Use Geo Data time zone and local time API with your agent
Inspect endpoint contracts and confirm availability and pricing before a paid call.