Data Time
by pay.brianbooms.com in Markets & finance
Use when an agent needs the current local time in any IANA time zone — scheduling posts, broadcasts, reminders, or market-window checks. Computed locally from the time zone database, no upstream to fail. Pass tz. Use permitted: build it into your products and services, paid or free. Raw redistribution of the feed itself is prohibited.
https://pay.brianbooms.com/api/v1/data/time- Price
- $0.01
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 2 h ago, next any minute now
Reliability
Latest check failed 2 h ago: Expected HTTP 402, got 400
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://pay.brianbooms.com/api/v1/data/time
Each call costs $0.01 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
GET https://pay.brianbooms.com/api/v1/data/time?tz=IANA+time+zone.+Example%3A+America%2FChicagoExample response
The provider's example. We can't check it without paying.
{
"day_of_week": "Sunday",
"local_time": "2026-09-27 11:22:47",
"product": "Local time",
"timezone": "America/Chicago",
"utc_offset": "-05:00"
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.01.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://pay.brianbooms.com/api/v1/data/time?tz=IANA+time+zone.+Example%3A+America%2FChicago'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://pay.brianbooms.com/api/v1/data/time?tz=IANA+time+zone.+Example%3A+America%2FChicago' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fpay.brianbooms.com%2Fapi%2Fv1%2Fdata%2Ftime
const res = await pay("https://pay.brianbooms.com/api/v1/data/time?tz=IANA+time+zone.+Example%3A+America%2FChicago");
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://pay.brianbooms.com/api/v1/data/time?tz=IANA+time+zone.+Example%3A+America%2FChicago")
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 2 h ago | Expected HTTP 402, got 400 | 400 | 521 ms | - |
| 8 h ago | Expected HTTP 402, got 400 | 400 | 376 ms | - |
| 13 h ago | Expected HTTP 402, got 400 | 400 | 325 ms | - |
| 19 h ago | Expected HTTP 402, got 400 | 400 | 373 ms | - |
| 25 h ago | Expected HTTP 402, got 400 | 400 | 430 ms | - |
Show 10 older checks
| 30 h ago | Expected HTTP 402, got 400 | 400 | 345 ms | - |
| 36 h ago | Expected HTTP 402, got 400 | 400 | 460 ms | - |
| 41 h ago | Expected HTTP 402, got 400 | 400 | 265 ms | - |
| 47 h ago | Expected HTTP 402, got 400 | 400 | 298 ms | - |
| 2 days ago | Expected HTTP 402, got 400 | 400 | 412 ms | - |
| 2 days ago | Expected HTTP 402, got 400 | 400 | 502 ms | - |
| 3 days ago | Expected HTTP 402, got 400 | 400 | 262 ms | - |
| 3 days ago | Expected HTTP 402, got 400 | 400 | 232 ms | - |
| 3 days ago | Expected HTTP 402, got 400 | 400 | 542 ms | - |
| 3 days ago | Expected HTTP 402, got 400 | 400 | 506 ms | - |