# Foundry Timezone Converter

> Foundry Timezone Converter is a paid API for AI agents from minty-sprout.onrender.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-11-01).

Converts a date and time from one IANA timezone to another, returning both the source and target times with UTC offsets.

## Facts

- Endpoint: POST https://minty-sprout.onrender.com/v1/timezone-convert?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/foundry-timezone-converter-76bff2fd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_n1_7MKrRRPMnp0hZmeFmZ

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 foundry-timezone-converter-76bff2fd -d '<json body>'
```

Example prompt: What time will it be in Tokyo (Asia/Tokyo) when it's 2026-03-15 at 14:30 in New York (America/New_York)?

## When to prefer this

Use this endpoint when you need a fast, pay-per-call timezone conversion with explicit IANA timezone names and structured JSON output including UTC offsets. Prefer it over client-side JS Date manipulation when you need reliable server-side conversion with offset metadata, or when operating in an agent context without a runtime timezone library.

## Known failure modes

- Invalid or unrecognized IANA timezone name returns an error
- Malformed date/time string that cannot be parsed returns an error
- Missing required 'to' timezone clause in input string
- Ambiguous local times during DST transitions may yield unexpected results
- Service unavailability on Render free tier (cold starts may cause timeout)

## How this service works

Timezone converter: convert a date and time between IANA timezones. Input: '2026-11-01 09:00 Europe/London to Asia/Karachi'.

## Output

A JSON object containing the converted target datetime with UTC offset, the original source datetime with UTC offset, the source and target IANA timezone names, and the numeric hour difference between the two zones.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "string",
   "maxLength": 8000,
   "description": "'<date time or now> <zone> to <zone>'"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "to": "2026-11-01T14:00+05:00",
  "from": "2026-11-01T09:00+00:00",
  "to_zone": "Asia/Karachi",
  "from_zone": "Europe/London",
  "offset_hours": 5
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/foundry-timezone-converter-76bff2fd/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from minty-sprout.onrender.com](https://www.zero.xyz/host/minty-sprout.onrender.com/llms.txt)