# Money Reactor — Current UTC Time

> Money Reactor — Current UTC Time is a paid API for AI agents from mr-river2.makar52nn2016.workers.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-11-18).

Returns the current UTC time as ISO 8601 string and Unix timestamp

## Facts

- Endpoint: GET https://mr-river2.makar52nn2016.workers.dev/api/time?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/money-reactor-current-utc-time-a3d98b5f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_CQv2SWe5qIeIKAccwX9lR

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 money-reactor-current-utc-time-a3d98b5f
```

Example prompt: What is the current UTC time right now — give me both the ISO 8601 format and the Unix timestamp?

## When to prefer this

Use this endpoint when your agent needs an authoritative external UTC timestamp and cannot rely on a local system clock — especially useful for on-chain workflows, audit logging, or deadline comparisons where clock drift matters. It is pay-per-call with no account setup required, making it suitable for ad-hoc or infrequent time lookups.

## Known failure modes

- Network or worker outage returns a 5xx error with no body
- x402 payment failure returns HTTP 402 if USDC balance is insufficient or payment is rejected
- Malformed response if upstream Cloudflare Worker is misconfigured

## How this service works

60+ agent-native micro APIs paid per call in USDC on Base via x402: fresh market data every call (market cap, top movers, funding rates, orderbook, RSI trading checklist, volatility, cycle position), funded bounty radar, honeypot trust scoring, token safety verdicts, AI chat (Llama 3.1), web reader, ERC-20 balances. No accounts, no API keys — instant on-chain settlement.

## Output

A JSON object containing the current UTC time as an ISO 8601 string (e.g. '2026-10-30T12:00:00.000Z'), the corresponding Unix timestamp as an integer, and the timezone label ('UTC').

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "iso": "2026-10-30T12:00:00.000Z",
  "unix": 1793054400,
  "timezone": "UTC"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/money-reactor-current-utc-time-a3d98b5f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from mr-river2.makar52nn2016.workers.dev](https://www.zero.xyz/host/mr-river2.makar52nn2016.workers.dev/llms.txt)
