# Orthogonal Timezone Time Converter

> Orthogonal Timezone Time Converter is a paid API for AI agents from x402.orthogonal.com, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-15).

Converts a datetime from one location or timezone to another, defaulting to the current time if no datetime is specified.

## Facts

- Endpoint: GET https://x402.orthogonal.com/timezone/v1/convert_time
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/orthogonal-timezone-time-converter-d9e8c092
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_xL3gBSjn1lBWlWNDGszff

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability orthogonal-timezone-time-converter-d9e8c092
```

Example prompt: What time will it be in Tokyo when it's 3:30pm in New York on Friday?

## When to prefer this

Choose this endpoint when you need a simple, cheap per-call timezone conversion between two human-readable locations or city names without needing to maintain timezone databases or integrate with a larger calendar/scheduling API. Especially useful for agents that occasionally need to answer 'what time is X in Y' questions in a conversational flow.

## Known failure modes

- Unrecognized or ambiguous location names may result in an error or incorrect timezone resolution
- Missing required query parameters may cause a 400 Bad Request
- Ambiguous city names (e.g. 'Springfield') without country context may resolve incorrectly
- No response if the service is unavailable or payment fails (402 Payment Required)

## How this service works

Convert time between two locations or timezones.

## Output

Returns the converted datetime in the target location's timezone, including the local time representation and relevant timezone metadata such as offset or timezone name.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "base_datetime": {
       "type": "string",
       "description": "Datetime to convert (defaults to now)"
      },
      "base_location": {
       "type": "string",
       "description": "The source location"
      },
      "target_location": {
       "type": "string",
       "description": "The target location"
      }
     }
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/orthogonal-timezone-time-converter-d9e8c092/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.orthogonal.com](https://www.zero.xyz/host/x402.orthogonal.com/llms.txt)