x402AgentsToolsHub

Meeting Time Planner

Given 2-8 cities, find the UTC hours where everyone sits inside acceptable local business hours (default 9-17) for a given date — DST-correct via the IANA tz database. Returns every feasible hour with each city's local time, or the best partial-overlap hours if none fit.

🔌 Server-side tool

This tool runs on the server (it fetches third-party URLs directly and cannot run in your browser). Use the paid JSON API below — the worked examples show real server-side results and refresh automatically.

Worked examples

Berlin · New York · Tokyo

GET /api/v1/geo-time/meeting-planner?cities=Berlin%2C%20New%20York%2C%20Tokyo

Result: No hour fits all 3 cities on 2026-10-19 — best is 07:00 UTC (2/3 in window)

London · San Francisco

GET /api/v1/geo-time/meeting-planner?cities=London%2C%20San%20Francisco&date=2026-07-15

Result: No hour fits all 2 cities on 2026-07-15 — best is 08:00 UTC (1/2 in window)

Sydney · Berlin (hard pair)

GET /api/v1/geo-time/meeting-planner?cities=Sydney%2C%20Berlin&window=7-19

Result: 3 hour(s) work for all 2 cities: 05:00 UTC, 06:00 UTC, 07:00 UTC

Machine API (x402)

$0.02 / call

This tool is also a JSON API for AI agents. Requests without payment receive 402 Payment Required plus instructions; agents pay USDC on Base via the x402 protocol — no accounts, no API keys.

GET /api/v1/geo-time/meeting-planner?cities=Berlin%2C%20New%20York%2C%20Tokyo HTTP/1.1
Host: agentstoolshub.com

→ 402 (payment required, instructions in headers)
→ 200 (after X-PAYMENT header; JSON body below)

{
  "tool": "geo-time/meeting-planner",
  "input": {"cities":"Berlin, New York, Tokyo"},
  "result": { "value": 0, "answer": "No hour fits all 3 cities on 2026-10-19 — best is 07:00 UTC (2/3 in window)" }
}

Agent docs: /llms.txt · OpenAPI spec · integration guide

About this tool

The across-timezones scheduling answer with real math: geocodes each city to its IANA timezone, applies DST-correct offsets for the exact date, and lists every UTC hour where all participants sit in local business hours (9-17 by default, configurable). No full overlap? It ranks the best partial hours instead.

Frequently asked questions

Is daylight saving handled?

Yes — offsets come from the IANA tz database for the specific date via Intl, so a July meeting between Europe and the US reflects summer-time rules, and dates on DST-switch days are computed correctly.

What if no hour works for everyone?

Classic far pairs (Sydney–Berlin) may have no overlap inside 9-17. The tool then ranks hours by how many cities fit, so you can see who would have to flex — widen the window parameter to explore compromises.

Related tools