Quick timezone, holiday, and business-hours check for any country — avoid midnight emails and holiday disruptions.
What it does
The `/v1/time` endpoint on AgentUtil Context provides a fast timezone and holiday lookup for AI agents. Given an IANA timezone, ISO country code, and optional date, it returns the current local time, whether it's business hours, whether it's a weekend, any holidays on that date, and a human-readable summary. This lets agents gate time-sensitive actions (sending emails, scheduling meetings, triggering notifications) on whether the recipient's locale is in a reasonable window.
The endpoint is part of the broader AgentUtil Context service, which also offers a comprehensive action-check endpoint (`/v1/check`), a platform-status endpoint (`/v1/platform`), and a free holiday calendar (`/v1/calendar`) covering 11 countries. All endpoints are designed for sub-50ms latency with pure data lookups — no LLM inference in the loop.
Pricing is $0.001 per request via the x402 protocol (USDC on Base). A free tier of 10 queries per day per IP is available with no signup required. The service publishes a full OpenAPI 3.1 spec and agent discovery files (`agent-service.json`, `agent.json`) for automated integration.
Capabilities
Use cases
- —Check if it's business hours in a recipient's timezone before sending an automated email
- —Verify whether a target date is a holiday before scheduling a deployment or campaign
- —Gate meeting-scheduling workflows on local time and weekend status
- —Add timezone awareness to autonomous agent decision loops
Fit
Best for
- —AI agents that need to respect local business hours before acting
- —Workflow automation that spans multiple timezones and countries
- —Lightweight pre-flight checks before time-sensitive operations
Not for
- —Detailed calendar or scheduling management (this is a read-only check, not a booking system)
- —Historical timezone or daylight-saving-time transition data
Quick start
curl -X POST https://context.agentutil.net/v1/time \
-H "Content-Type: application/json" \
-d '{"timezone": "America/New_York", "country": "US"}'Example
Request
{
"date": "2026-12-25",
"country": "US",
"timezone": "America/New_York"
}Response
{
"date": "2026-12-25",
"summary": "It is currently business hours in America/New_York, but today is Christmas Day (public holiday) with high business impact.",
"holidays": [
{
"name": "Christmas Day",
"type": "public",
"business_impact": "high"
}
],
"timezone": "America/New_York",
"is_weekend": false,
"local_time": "10:30:00",
"is_business_hours": true
}Endpoint
Quality
Full OpenAPI 3.1 schema with clear request/response definitions, published pricing, and agent discovery files. However, the probe returned HTTP 200 on POST (not 402), suggesting the free tier served the request rather than presenting an x402 challenge, so the paid x402 flow was not directly verified. No dedicated docs page exists. Example response is inferred from the schema, not captured.
Warnings
- —The x402 payment challenge was not observed during probing — the endpoint returned 200 on POST, likely serving a free-tier response. The paid x402 flow could not be independently verified.
- —No /docs, /api, /pricing, or /README pages exist; documentation is limited to the landing page and OpenAPI spec.
- —The example response is inferred from the OpenAPI schema, not captured from a live call.
Citations
- —The /v1/time endpoint accepts timezone, country, and date parameters and returns business-hours, weekend, and holiday information.https://context.agentutil.net/openapi.json
- —Pricing for /v1/time is $0.001 per request via x402 (USDC on Base), with a free tier of 10 queries/day per IP.https://context.agentutil.net
- —Service covers 11 countries and responds in under 50ms with pure data lookups.https://context.agentutil.net
- —Agent discovery files are published at .well-known/agent-service.json and .well-known/agent.json.https://context.agentutil.net