Interzoid Get Global Time API

Name: Interzoid Get Global Time API API
Brand: Interzoid Get Global Time API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentData TransformationapiKey1 EndpointsREST

For Agents

Look up the current local time, weekday, and timezone for any city, region, or country worldwide so an agent can schedule, gate, or display time-sensitive actions in the user's locale.

Connect the Interzoid Get Global Time API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Interzoid Get Global Time API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Interzoid Get Global Time API API.

Resolve a free-text locale such as 'Tokyo' or 'Buenos Aires' to its current clock time and timezone

Check whether a target locale is currently inside business hours before triggering an outreach action

Render a localized current-date string for a user without bundling a timezone database

Return the current weekday for a locale to gate weekday-only workflows

GET STARTED

Start building with Interzoid Get Global Time API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Interzoid Get Global Time API, keeping it validated and agent-ready.

The Interzoid Get Global Time API returns the current local time for a city, region, or country worldwide, along with the timezone, weekday, and pre-formatted date and time strings. It removes the need to ship a timezone database with an application by exposing a single GET call that resolves a free-text locale (Chicago, London, Tokyo, Hawaii, Buenos Aires) to a concrete clock reading. It is intended for workflows that need to schedule actions, render localized timestamps, or check business hours without embedding tz data locally.

Use Cases

Patterns agents use Interzoid Get Global Time API API for, with concrete tasks.

★ Business Hours Gating

Decide whether to send an outbound message to a customer by first checking whether the current local time at their locale falls inside business hours. The Get Global Time API returns Hour, Minute, and Weekday for the supplied locale, so an agent can compare these to a configured schedule before triggering the send. The single GET call removes the need to maintain a local tz database.

Call /getglobaltime with locale=London and skip the outreach step if the returned Hour is outside the 09-17 window or Weekday is Saturday or Sunday.

Localized UI Timestamp

Render a current local-time string in a user-facing UI without bundling a timezone library. The API returns ClockTime, CurrentDate, and Zone for the requested locale, which can be displayed verbatim. This is useful for status pages, dashboards, and notification headers that need to show the user's local time at request time.

Call /getglobaltime with locale=Tokyo and display the returned ClockTime and Zone fields in the dashboard header.

Cross-Region Scheduling

Coordinate a meeting or scheduled task across multiple regions by querying the current time for each participant locale in turn. The API accepts any of city, region, or country in the locale parameter, which is helpful when participant data only stores a country or region. CurrentTime, Weekday, and Zone together provide enough context to compute a viable shared slot.

Call /getglobaltime three times with locale set to Chicago, London, and Tokyo, then return the three ClockTime values for use in a scheduling prompt.

Agent Time-Aware Workflow via Jentic

An AI agent that fires scheduled actions uses Jentic to call the Interzoid Get Global Time API on demand for each target locale, instead of hardcoding tz lookups. The agent reads CurrentTime and Zone, decides whether to act, and proceeds. Through Jentic the Interzoid license key is held in the credential vault and never enters the agent context.

Use Jentic to search for 'get the current local time for a city', load /getglobaltime, and execute it for each of the agent's target locales before deciding whether to fire its scheduled action.

Key Endpoints

1 endpoints — the interzoid get global time api returns the current local time for a city, region, or country worldwide, along with the timezone, weekday, and pre-formatted date and time strings.

METHOD

PATH

DESCRIPTION

GET

/getglobaltime

Return the current local time and timezone for a city, region, or country

GET

/getglobaltime

Return the current local time and timezone for a city, region, or country

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Interzoid license API key is stored encrypted in the Jentic vault. Agents receive scoped access at execution time and the raw license value never enters the agent context.

Intent-based discovery

Agents search Jentic with an intent like 'get the current local time for a city' and receive the /getglobaltime operation with its input schema, ready to execute.

Time to first call

Direct integration with Interzoid: a few hours to wire up auth and error handling. Through Jentic: under 10 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Interzoid Get Weather City API

Returns current weather for a US city, often called alongside the time lookup for locale-aware status panels.

Use together when the workflow needs both current local time and current weather for a US locale.

Complementary

Interzoid Zip Code Detailed Info API

Returns city, state, latitude, and longitude for a US zip code, useful before resolving local time for a US-only locale.

Use this first when you only have a zip code and need a city string to pass to the global time lookup.

Complementary

Interzoid State Data Standardization API

Standardizes US and Canadian state names to two-letter abbreviations, helpful for cleaning locale strings before time lookup.

Use when locale data must be normalized before being sent to the time endpoint.

FAQs

Specific to using Interzoid Get Global Time API API through Jentic.

What authentication does the Interzoid Get Global Time API use?

The API uses an Interzoid license key passed as the required `license` query parameter on /getglobaltime. Through Jentic the license key is held in the credential vault and injected at execution time, so the raw key never enters the agent context.

Can I look up time by country or only by city?

Both. The locale parameter on /getglobaltime accepts a city (Chicago, London), a region (Hawaii), or a country (Spain). The API resolves the supplied string to the corresponding current local time.

What are the rate limits for the Interzoid Get Global Time API?

The OpenAPI spec does not declare a numeric rate limit. Each successful call decrements a credit balance returned in the Credits response field, and a 402 status is returned when credits are exhausted. Refer to interzoid.com for current per-license-tier throughput.

How do I get the current time for a city through Jentic?

Install the SDK with `pip install jentic`, search for 'get the current local time for a city', load /getglobaltime, and execute it with locale set to the target city. The ClockTime and Zone fields can be displayed directly.

What does the response include?

A 200 response returns ClockTime, CurrentDate, CurrentTime, Hour, Minute, Second, Day, Month, MonthNumber, Year, Weekday, Locale, Zone, and TimeStamp. Agents typically use ClockTime for display and Hour or Weekday for gating logic.

What happens when the locale is unknown?

The API returns a 404 status with no time payload if the locale cannot be matched. Agents should validate locale strings against a known whitelist before calling, or handle the 404 by falling back to a default timezone.