Convert a datetime from one timezone/location to another via a pay-per-call MPP endpoint.
What it does
This endpoint converts a given datetime from a source location's timezone to a target location's timezone. It is part of the Abstract Timezone service exposed through the Locus MPP (Micropayment Protocol) gateway. You provide a base location, a target location, and optionally a datetime string; the service returns the converted time.
Payment is handled via the Tempo method (pathUSD on Tempo L2) at $0.006 per call (6000 base units with 6 decimals). The endpoint accepts POST requests with a JSON body containing `base_location` (required), `target_location` (required), and `base_datetime` (optional — presumably defaults to current time if omitted).
The underlying data source is the Abstract API Time/Date/Timezone API. Documentation is available at the Abstract API docs site. Note that the probe only tested HEAD and GET methods which returned 404; the OpenAPI spec defines this as a POST endpoint, so it is expected to be live when called correctly via POST.
Capabilities
Use cases
- —Converting meeting times between offices in different cities
- —Scheduling international events by translating local times
- —Displaying localized timestamps for users in different regions
- —Building travel itinerary tools that show arrival times in destination timezone
- —Automating cross-timezone deadline calculations
Fit
Best for
- —Agents needing on-demand timezone conversion without API key management
- —Applications converting arbitrary location names to timezone-aware datetimes
- —Workflows requiring pay-per-use pricing with no subscription commitment
Not for
- —High-volume batch timezone conversions where per-call cost adds up
- —Offline or latency-critical applications that need local timezone databases
- —Use cases requiring only UTC offset lookup without datetime conversion (use the sibling current-time endpoint instead)
Quick start
curl -X POST https://abstract-timezone.mpp.paywithlocus.com/abstract-timezone/convert-time \
-H "Content-Type: application/json" \
-d '{"base_location": "New York", "target_location": "Tokyo", "base_datetime": "2024-01-15 09:00:00"}'Example
Request
{
"base_datetime": "2024-01-15 09:00:00",
"base_location": "New York",
"target_location": "Tokyo"
}Endpoint
Quality
OpenAPI schema is present with clear request parameters and pricing info. However, no example response is available, the probe returned 404 because it tested GET/HEAD rather than POST, and crawled pages yielded no additional documentation. The endpoint is likely live via POST but unconfirmed.
Warnings
- —Probe tested HEAD/GET only; endpoint requires POST per OpenAPI spec — liveness unconfirmed via probe
- —No example response schema or sample response available
- —Currency address 0x20c000000000000000000000b9537d11c60e8b50 assumed to be pathUSD with 6 decimals based on Tempo convention; not independently verified
Citations
- —The endpoint uses POST method with base_location, target_location, and base_datetime parametershttps://abstract-timezone.mpp.paywithlocus.com
- —Payment is 6000 base units via Tempo methodhttps://abstract-timezone.mpp.paywithlocus.com
- —Underlying API documentation is at Abstract APIhttps://docs.abstractapi.com/timezone
- —Service homepage is at Abstract API timezone pagehttps://www.abstractapi.com/api/time-date-timezone-api