# Strale Timezone Meeting Finder

> Strale Timezone Meeting Finder is a paid API for AI agents from api.strale.io, paid per call via x402, $0.0324/call, status unknown (last checked 2026-09-15).

Finds optimal meeting times across multiple timezones by identifying overlapping business hours for distributed teams

## Facts

- Endpoint: GET https://api.strale.io/x402/v2/timezone-meeting-find
- Price: $0.0324/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/strale-timezone-meeting-finder-45f924f3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_4PQ1ClhpfcTkGnt-KceBV

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 strale-timezone-meeting-finder-45f924f3
```

Example prompt: Find me a good meeting time that works for participants in America/New_York, Europe/London, and Asia/Tokyo — I want to see what hours overlap during business hours.

## When to prefer this

Choose this endpoint when you need to programmatically identify meeting-friendly time windows across multiple IANA timezones, especially for distributed team scheduling. Prefer this over generic calendar tools when you need a structured JSON response with audit trail compliance, or when orchestrating meeting scheduling within an AI agent workflow that requires verifiable outputs.

## Known failure modes

- Invalid or unrecognized timezone identifier returns an error
- No overlapping business hours found when timezones are too far apart (e.g. US West Coast and East Asia)
- Missing required 'timezones' parameter returns a validation error
- Malformed timezone string (non-IANA format) may cause parsing failure

## How this service works

The trust layer for AI agents — 250+ independently tested data capabilities across 27 countries. Execute capabilities via REST, MCP, A2A, or x402 micropayments. Every call returns an audit record with cryptographic chain hashing.

## Output

Returns a list of time windows where the specified timezones share overlapping hours, likely including the overlapping time ranges in each timezone, suitable hours for scheduling meetings, and an audit record with cryptographic chain hashing for traceability.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "timezones": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/strale-timezone-meeting-finder-45f924f3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.strale.io](https://www.zero.xyz/host/api.strale.io/llms.txt)