Get Users Current Time / Date

Core Utility

Available ActionsEach successful request consumes credits as outlined below.

get_current_datetime^3cr

Details

Agents running in the cloud don't know what timezone their users are in. This tool returns the current date and time in the user's configured timezone so agents can schedule, format, and reason about time using the user's local context. The tool returns both local and UTC timestamps, the timezone name, and useful derived fields such as local date, local time, and UTC offset. This enables time aware workflows like reminders, deadlines, and calendar or messaging logic without repeatedly asking the user what time zone they are in.

Use Cases

Get current local time for a user, Build time aware reminders, Schedule messages in the user timezone, Add local timestamps to logs, Convert between UTC and user local time, Validate timezone configuration, Generate date strings for reports

Connect Your Agent In 5 Min

Watch the setup guide for your platform

Or Install Locally

STDIO connector for Claude Code, Codex, Cursor, Zed, and other LLMs that require STDIO or custom connections. This lightweight connector routes requests to https://api.agentpmt.com/mcp. All tool execution happens in the cloud and the server cannot edit any files on your computer.

npm install -g @agentpmt/mcp-routeragentpmt-setup

Credentials

User Timezone *

Select your IANA timezone (e.g. US/Eastern, Europe/London, Asia/Tokyo).

other

Manage credentials in your dashboard.

Actions(1)

get_current_datetime^3cr0 params

Returns the current local datetime, UTC datetime, and derived fields (local date, local time, UTC offset, DST status) based on the user's configured timezone.

No parameters for this action.

curl -X POST "https://api.agentpmt.com/products/purchase" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer ********" \
  -d '{
    "product_id": "6987b3363a2127a981e41238",
    "parameters": {
      "action": "get_current_datetime"
    }
  }'

import requests
import json

url = "https://api.agentpmt.com/products/purchase"

headers = {
    "Content-Type": "application/json",
    "Authorization": "Bearer ********"
}

data = {
    "product_id": "6987b3363a2127a981e41238",
    "parameters": {
        "action": "get_current_datetime"
    }
}

response = requests.post(url, headers=headers, json=data)
print(response.status_code)
print(response.json())

const url = "https://api.agentpmt.com/products/purchase";

const headers = {
  "Content-Type": "application/json",
  "Authorization": "Bearer ********"
};

const data = {
  product_id: "6987b3363a2127a981e41238",
  parameters: {
    "action": "get_current_datetime"
  }
};

fetch(url, {
  method: "POST",
  headers,
  body: JSON.stringify(data)
})
  .then(response => response.json())
  .then(data => console.log(data))
  .catch(error => console.error("Error:", error));

const axios = require('axios');

const url = "https://api.agentpmt.com/products/purchase";

const headers = {
  "Content-Type": "application/json",
  "Authorization": "Bearer ********"
};

const data = {
  product_id: "6987b3363a2127a981e41238",
  parameters: {
    "action": "get_current_datetime"
  }
};

axios.post(url, data, { headers })
  .then(response => {
    console.log(response.status);
    console.log(response.data);
  })
  .catch(error => {
    console.error("Error:", error.message);
  });

Login to view your API and budget keys. The example above uses placeholder values. Sign in to see personalized code with your bearer token.

This tool supports credit-based access for external agents using AgentAddress identities or standard crypto wallets. External agents should use the External Agent API to buy credits with x402 and invoke this tool.

1. Buy Credits

Purchase credits via x402 payment (500 credit minimum, 100 credits = $1).

# Request payment requirements (returns 402 + PAYMENT-REQUIRED header)
curl -i -s -X POST "https://www.agentpmt.com/api/external/credits/purchase" \
  -H "Content-Type: application/json" \
  -d '{ "wallet_address":"0xYOUR_WALLET", "credits": 500, "payment_method":"x402" }'

# Sign the EIP-3009 authorization, then retry with signature header
curl -s -X POST "https://www.agentpmt.com/api/external/credits/purchase" \
  -H "Content-Type: application/json" \
  -H "PAYMENT-SIGNATURE: <base64-json>" \
  -d '{ "wallet_address":"0xYOUR_WALLET", "credits": 500, "payment_method":"x402" }'

2. Create a Session Nonce (nonce used in signed balance/invoke)

curl -s -X POST "https://www.agentpmt.com/api/external/auth/session" \
  -H "Content-Type: application/json" \
  -d '{ "wallet_address":"0xYOUR_WALLET" }'

3. Invoke This Tool

Sign the message with your wallet (EIP-191 personal-sign), then POST to the invoke endpoint.

# Sign this message (wallet MUST be lowercased):
# agentpmt-external
# wallet:0xyourwallet...
# session:<session_nonce>
# request:<request_id>
# method:POST
# path:/external/tools/user-timezone-datetime/actions/<actionSlug>/invoke
# payload:<sha256(canonical_json(parameters))>

curl -s -X POST "https://www.agentpmt.com/api/external/tools/user-timezone-datetime/actions/<actionSlug>/invoke" \
  -H "Content-Type: application/json" \
  -d '{
    "wallet_address": "0xYOUR_WALLET",
    "session_nonce": "<session_nonce>",
    "request_id": "invoke-uuid",
    "signature": "0x<signature>",
    "parameters": {
      "your_param": "value"
    }
  }'

Usage Instructions

Usage guidance provided directly by the developer for this product.

User Timezone DateTime

Returns the current date and time based on the user's configured timezone setting. Uses IANA timezone names (e.g., "America/New_York", "Europe/London") to provide accurate local time with UTC offset, DST detection, and formatted date/time components.

Actions

get_current_datetime

Returns the current local datetime, UTC datetime, and derived fields for the user's configured timezone.

Required Parameters: None (timezone is automatically injected from the user's account settings)

Response Fields:

timezone (string) -- IANA timezone name used (e.g., "America/Chicago")
utc_datetime (string) -- Current UTC datetime in ISO 8601 format
local_datetime (string) -- Current local datetime in ISO 8601 format
local_date (string) -- Local date in YYYY-MM-DD format
local_time (string) -- Local time in HH:MM:SS format
utc_offset (string) -- UTC offset formatted as "+HH:MM" or "-HH:MM"
utc_offset_minutes (integer) -- UTC offset in total minutes
is_dst (boolean or null) -- Whether daylight saving time is currently active

Example Request:

{
  "action": "get_current_datetime"
}

Example Response:

{
  "action": "get_current_datetime",
  "timezone": "America/New_York",
  "utc_datetime": "2026-03-10T18:30:00+00:00",
  "local_datetime": "2026-03-10T14:30:00-04:00",
  "local_date": "2026-03-10",
  "local_time": "14:30:00",
  "utc_offset": "-04:00",
  "utc_offset_minutes": -240,
  "is_dst": true
}

Workflows

Check current time before scheduling -- Call get_current_datetime to determine the user's current local time before creating calendar events or setting reminders.
Time-aware greetings -- Use local_time to provide contextual greetings (good morning/afternoon/evening) based on the user's actual local time.
Cross-timezone coordination -- Use utc_datetime and utc_offset together to help users coordinate meetings across different timezones.
DST awareness -- Check the is_dst field to inform users about daylight saving time status when scheduling recurring events.

Notes

The user's timezone is automatically provided from their account settings; no manual timezone input is needed.
If the user has not configured a timezone, the request will fail with a validation error ("User timezone is required").
All IANA timezone names are supported (e.g., "US/Eastern", "Asia/Tokyo", "Pacific/Auckland").
The is_dst field may return null for timezones that do not observe daylight saving time.
UTC offset is provided in both human-readable string format and numeric minutes for programmatic use.