Skill: Meeting scheduler

Bundled execution of the Meeting scheduler workflow - Schedule a meeting across timezones without the round-tripping. Convert a proposed UTC slot into every attendee's local time, verify it lands on a working day for each, project the end time, generate human-readable countdowns, expand recurring rules, and report exactly how far out the slot sits - in one deterministic pass. One x402 payment runs 7 underlying tools (time, time-convert, business-days, add-time, relative-time, cron-next, date-diff); partial-success per step.

Input

Field	Type	Description
proposedTime *	string	Proposed start time in UTC ISO 8601 (e.g. '2026-07-15T14:00:00Z')
attendeeTzs *	string	Comma-separated IANA timezones (e.g. 'America/New_York, Europe/London, Asia/Tokyo')
durationStr *	string	Meeting duration as a duration string (e.g. '1h30m' or '45m')

Example output

{
  "pack": "meeting-scheduler",
  "args": {
    "proposedTime": "2026-07-15T14:00:00Z",
    "attendeeTzs": "America/New_York, Europe/London, Asia/Tokyo",
    "durationStr": "1h"
  },
  "steps": [
    {
      "slug": "time",
      "ok": true,
      "result": {}
    },
    {
      "slug": "time-convert",
      "ok": true,
      "result": {}
    },
    {
      "slug": "business-days",
      "ok": true,
      "result": {}
    },
    {
      "slug": "add-time",
      "ok": true,
      "result": {}
    },
    {
      "slug": "relative-time",
      "ok": true,
      "result": {}
    },
    {
      "slug": "cron-next",
      "ok": true,
      "result": {}
    },
    {
      "slug": "date-diff",
      "ok": true,
      "result": {}
    }
  ],
  "summary": "7/7 steps succeeded"
}

Try it - see the 402 challenge (free)

curl -i -X POST https://agent402.tools/api/skill/meeting-scheduler \
  -H "Content-Type: application/json" \
  -d '{"proposedTime":"2026-07-15T14:00:00Z","attendeeTzs":"America/New_York, Europe/London, Asia/Tokyo","durationStr":"1h"}'

The response is HTTP 402 Payment Required with exact payment requirements. Any x402 v2 client pays automatically and retries:

Paid call (JavaScript agent)

import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/core/client";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

const client = new x402Client();
registerExactEvmScheme(client, { signer: privateKeyToAccount(KEY) });
const payFetch = wrapFetchWithPayment(fetch, client);

const res = await payFetch("https://agent402.tools/api/skill/meeting-scheduler", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
    "proposedTime": "2026-07-15T14:00:00Z",
    "attendeeTzs": "America/New_York, Europe/London, Asia/Tokyo",
    "durationStr": "1h"
  }),
});

No wallet? Pay with compute

This is a pure-CPU tool, so an agent without a wallet can pay with proof-of-work instead of USDC: fetch a challenge, solve the sha256 puzzle (16 leading zero bits - a fraction of a second of CPU, no money, no AI tokens), and resend with the X-Pow-Solution header.

import { createHash } from "node:crypto";
const lz = (b) => { let t = 0; for (const x of b) { if (!x) { t += 8; continue; } t += Math.clz32(x) - 24; break; } return t; };
const c = await (await fetch("https://agent402.tools/api/pow/challenge?slug=skill-meeting-scheduler")).json();
let n = 0;
while (lz(createHash("sha256").update(c.challenge + ":" + n).digest()) < c.difficulty) n++;
await fetch("https://agent402.tools/api/skill/meeting-scheduler", { method: "POST", headers: { "X-Pow-Solution": c.token + ":" + n, "Content-Type": "application/json" }, body: JSON.stringify({"proposedTime":"2026-07-15T14:00:00Z","attendeeTzs":"America/New_York, Europe/London, Asia/Tokyo","durationStr":"1h"}) });

Related tools