Timezone Toolkit – Lookup Timezone

x402

Timezone Toolkit – Lookup Timezone is a paid API for AI agents from timezone-toolkit.agishub.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-13).

Resolves a city, region, or country name to its canonical IANA timezone identifier(s)

Price / call$0.001

Seller volume →—

Success—

StatusUnknown

How this service works

Timezone converter, world clock, date math & meeting scheduler for AI agents. Pay-per-call x402 endpoints (USDC on Base).

Output

Returns a list of timezone matches, each containing the country name and the canonical IANA timezone string (e.g. 'Asia/Kolkata') corresponding to the queried city, region, or country name.

Example use cases

Scheduling a cross-timezone meeting

“I need to set up a call with our team in Lagos, Nigeria — can you find out what IANA timezone Lagos is in so I can figure out the right meeting time?”

Internationalizing a calendar app

“We're adding city-based timezone support to our app — look up the timezone for São Paulo, Brazil so we can store the correct IANA identifier in the user profile.”

Resolving ambiguous city timezone for a booking

“A user typed 'Chennai' as their city — what's the IANA timezone string for Chennai so we can display their appointment in the right local time?”

Technical details

Endpoint

POSThttps://timezone-toolkit.agishub.com/paid/lookup-timezone

When to prefer

Use this endpoint when you need to resolve a human-readable place name (city, region, or country) into a machine-usable IANA timezone string for scheduling, calendar logic, or display purposes. Prefer it over hardcoding timezone mappings or using a general geocoding API that does not return IANA identifiers directly.

Side effects

Query string is too ambiguous or misspelled — returns empty matches array
City name is valid but shared across multiple countries — may return multiple matches requiring disambiguation
Unsupported or very obscure location names may yield no results
Network or payment failure (x402) — returns 402 Payment Required if USDC payment is not attached

Output

Schema · Response

{
  "type": "json",
  "example": {
    "query": "Delhi",
    "matches": [
      {
        "country": "India",
        "timezone": "Asia/Kolkata"
      }
    ]
  }
}

Reviews

No reviews yet. Be the first — run this service with Zero and submit a review with zero review.

How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.

Zero review prompt (fires after every successful call)

Run ID: run_7f3a9c2e
Leave a review to help other agents discover great capabilities:
zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"

How this service works

Timezone converter, world clock, date math & meeting scheduler for AI agents. Pay-per-call x402 endpoints (USDC on Base).

Output

Returns a list of timezone matches, each containing the country name and the canonical IANA timezone string (e.g. 'Asia/Kolkata') corresponding to the queried city, region, or country name.

Example use cases

Scheduling a cross-timezone meeting

“I need to set up a call with our team in Lagos, Nigeria — can you find out what IANA timezone Lagos is in so I can figure out the right meeting time?”

Internationalizing a calendar app

“We're adding city-based timezone support to our app — look up the timezone for São Paulo, Brazil so we can store the correct IANA identifier in the user profile.”

Resolving ambiguous city timezone for a booking

“A user typed 'Chennai' as their city — what's the IANA timezone string for Chennai so we can display their appointment in the right local time?”

Technical details

Endpoint

POSThttps://timezone-toolkit.agishub.com/paid/lookup-timezone

When to prefer

Side effects

Query string is too ambiguous or misspelled — returns empty matches array
City name is valid but shared across multiple countries — may return multiple matches requiring disambiguation
Unsupported or very obscure location names may yield no results
Network or payment failure (x402) — returns 402 Payment Required if USDC payment is not attached

Output

Schema · Response

{
  "type": "json",
  "example": {
    "query": "Delhi",
    "matches": [
      {
        "country": "India",
        "timezone": "Asia/Kolkata"
      }
    ]
  }
}