Get the current time for any location via a pay-per-call MPP endpoint.
What it does
This MPP (Micro-Payment Protocol) endpoint returns the current time and timezone information for a given location. It is part of the Abstract Timezone service, which wraps the Abstract API Time/Date/Timezone API behind a Locus MPP paywall. You send a POST request with a location string (city name, address, or coordinates) and receive the current local time and timezone details for that location.
The endpoint is priced at 6,000 base units of pathUSD (currency address 0x20c…b50) per call, which equals $0.006 (six-tenths of a cent) settled on Tempo L2. Payment intent is "charge", meaning each call is a one-shot micropayment. A sibling endpoint at `/abstract-timezone/convert-time` handles timezone conversion between two locations.
Note: The probe only tested HEAD and GET methods, which returned 404. The OpenAPI spec declares this as a POST endpoint, so the 404s on HEAD/GET are expected routing behavior and do not indicate the endpoint is down. The underlying Abstract API documentation is available at https://docs.abstractapi.com/timezone and the Locus-specific LLM docs at https://beta.paywithlocus.com/mpp/abstract-timezone.md.
Capabilities
Use cases
- —Retrieving the current local time for a city or coordinate pair in an automated workflow
- —Displaying timezone-aware timestamps for users in different regions
- —Feeding current time data into scheduling or calendar agents
- —Checking UTC offset and timezone abbreviation for a given location
Fit
Best for
- —Agents needing on-demand current time for arbitrary locations
- —Lightweight per-call timezone lookups without API key management
- —Micropayment-friendly integrations on Tempo L2
Not for
- —Bulk historical time-series data retrieval
- —Offline or latency-critical applications that cannot tolerate network round-trips
- —Use cases requiring free or subscription-based pricing models
Quick start
curl -X POST https://abstract-timezone.mpp.paywithlocus.com/abstract-timezone/current-time \
-H "Content-Type: application/json" \
-d '{"location": "New York, NY"}'Example
Request
{
"location": "Tokyo, Japan"
}Endpoint
Quality
The OpenAPI spec provides clear request schema, pricing, and endpoint paths, but no response schema or example responses are available. The probe only tested HEAD/GET (not POST), so liveness via the correct method is unconfirmed. Crawled pages returned only generic 404 JSON; no additional documentation was captured.
Warnings
- —Endpoint liveness not confirmed: probe used HEAD/GET but the endpoint requires POST; 404 on HEAD/GET is expected but POST was not tested.
- —No response schema or example response is documented in the OpenAPI spec.
- —Currency address 0x20c000000000000000000000b9537d11c60e8b50 is assumed to be pathUSD with 6 decimals; if this assumption is wrong the price calculation would differ.
- —No crawled documentation was successfully retrieved beyond the OpenAPI manifest.
Citations
- —The endpoint is documented as a POST method accepting a JSON body with a required 'location' field.https://abstract-timezone.mpp.paywithlocus.com
- —Price is 6000 base units settled via Tempo L2 with intent 'charge'.https://abstract-timezone.mpp.paywithlocus.com
- —Abstract API timezone documentation is available at docs.abstractapi.com/timezone.https://www.abstractapi.com/api/time-date-timezone-api
- —Locus LLM-specific docs referenced at beta.paywithlocus.com/mpp/abstract-timezone.md.https://beta.paywithlocus.com/mpp/abstract-timezone.md