Timezone planner
Time zone conversion, business day calculation, and cron schedule preview - scheduling in one pass.
3 tools run server-side in one request. You pay once, settle once, and get a single response - no orchestration, no per-step payments, and a partial-success envelope if any step fails. USDC over x402 on any supported chain.
When to use this pack
An agent coordinating across time zones needs to convert a time, count business days between dates, and preview when a cron job will fire. Three scheduling primitives bundled together for meeting planners, deployment schedulers, and coordination agents.
Tools in this pack
All 3 run inside the single $0.003 call above. Each is also callable on its own if you only need one part.
- Time convert POST /api/time-convert Convert between epoch (s or ms), ISO 8601, and any IANA timezone. Give a value (epoch seconds or milliseconds, an ISO string, or 'now'), get every representation back: utc, epochSeconds, epochMillis and, with tz, timezone, localIso (ISO 8601 with the zone's offset, e.g. 2026-06-11T19:00:00+09:00), utcOffset and local (a display string). A bare number under 1e12 is read as seconds, otherwise as milliseconds.
- Business days POST /api/business-days Count business days (Mon–Fri) between two dates, inclusive of the start, exclusive of the end. Optional list of holiday dates to skip.
- Cron next runs POST /api/cron-next Parse a 5-field cron expression and return the next N run times (UTC).
Bought one at a time, these 3 tools cost $0.003 together; the pack is that sum less a 10% bundle discount, rounded up to the $0.001 settlement floor, which is $0.003.
Workflow
- Call time-convert with the time, from timezone, and to timezone to get the converted time.
- Call business-days with start and end dates to count working days in the range.
- Call cron-next with a sample expression to preview upcoming schedule occurrences.
Arguments
| Name | Required | Description | Example |
|---|---|---|---|
time | yes | ISO datetime to convert (e.g. 2026-06-11T10:00:00) | 2026-06-11T10:00:00 |
from | no | Source timezone (e.g. America/New_York) | America/New_York |
to | no | Target timezone (e.g. Asia/Tokyo) | Asia/Tokyo |
What one call returns
A JSON object with pack, args, steps, summary; steps holds one entry per tool (time-convert, business-days, cron-next), each with its own result or error. Full example on the API page.
Call it directly
Any x402 client pays the 402 and gets the whole workflow back in one response. With the agent402-client SDK (npm i agent402-client, an ES module):
import { Agent402 } from "agent402-client";
// payFetch: an x402-wrapped fetch your wallet signs (@x402/fetch).
// Tools on the free tier need no options: new Agent402() pays them by proof-of-work.
// an existing prepaid credits key also works: new Agent402({ creditsKey })
const client = new Agent402({ fetch: payFetch });
const result = await client.call("skill-timezone-planner", {"time":"2026-06-11T10:00:00","from":"America/New_York","to":"Asia/Tokyo"});
Run it in Claude
claude mcp add agent402 -s user -- npx -y agent402-mcp@latest
Then paste this prompt into Claude:
Plan a meeting using Agent402's timezone-planner skill pack: Convert 2026-06-11T10:00:00 from America/New_York to Asia/Tokyo. Also check how many business days are between now and that date, and preview the next 5 occurrences of a weekly Monday 10am cron.