# aye.today Daylight Hours Check

> aye.today Daylight Hours Check is a paid API for AI agents from api.aye.today, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Returns a signed aye/nay attestation of whether astronomical daylight at a covered location meets a minimum-hours threshold on today or tomorrow.

## Facts

- Endpoint: POST https://api.aye.today/v1/daylight_check
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/aye-today-daylight-hours-check-13e2a683
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mkNqYmRn0yoQ-8J69F61y

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 aye-today-daylight-hours-check-13e2a683 -d '<json body>'
```

Example prompt: Will Orlando get at least 12 hours of daylight today — I need a signed aye/nay attestation?

## When to prefer this

Choose this endpoint when you need a cryptographically signed, deterministic attestation that a specific location will have at least a set number of daylight hours on today or tomorrow — particularly for smart contracts, automated workflows, or auditable records where a verifiable aye/nay claim hash matters. It is not suitable for continuous solar irradiance data, historical queries, or locations outside ORL/DEN.

## Known failure modes

- Unsupported place code (only ORL and DEN are covered) — likely returns a validation error
- Invalid day value outside 'today'/'tomorrow' enum — request rejected
- Invalid min_hours value outside 10/12/14 enum — request rejected
- Payment failure via x402 protocol — call not executed
- Stale or incorrect UTC day interpretation if caller's timezone differs from UTC assumption

## How this service works

Attested resolution: will astronomical day length at a covered place meet a minimum-hours bar today or tomorrow? Computed-deterministic tier — pure celestial math, zero upstream license exposure. Deterministic per UTC day; same inputs, same claim hash. Delivered as a signed result capped by an aye/nay receipt.

## Output

A signed aye/nay receipt indicating whether the astronomical day length at the specified location meets the minimum-hours threshold on the chosen day, along with a deterministic claim hash tied to the UTC day and inputs.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/aye-today-daylight-hours-check-13e2a683/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.aye.today](https://www.zero.xyz/host/api.aye.today/llms.txt)