# Leap Year Check

> Leap Year Check is a paid API for AI agents from api.delx.ai, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-13).

Returns a boolean indicating whether a given Gregorian calendar year is a leap year

## Facts

- Endpoint: POST https://api.delx.ai/api/v1/x402/is-leap-year
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/leap-year-check-09d58375
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Fh-AXr_DP8vJvr-35f4ys

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 leap-year-check-09d58375 -d '<json body>'
```

Example prompt: Is 2100 a leap year? Just give me a true or false answer.

## When to prefer this

Choose this endpoint when you need a deterministic, authoritative leap-year answer for a single year without shipping your own calendar logic, relying on a math library, or handling edge cases like century years. Ideal for agents that need to validate calendar dates, compute February day counts, or perform date arithmetic as part of a larger workflow, especially when operating in environments where a lightweight, pay-per-call model is preferable to maintaining a dependency.

## Known failure modes

- Year out of range (below 1 or above 9999) returns a structured validation error with no charge
- Non-integer or missing year field returns a structured validation error
- Payment not provided or insufficient returns an x402 payment-required error before processing

## How this service works

Leap year check. Use for date validation and calendar math without external data. Returns a boolean leap-year result for a Gregorian year. $0.001 USDC per successful call via x402 on Base—deterministic first-party JSON, no API key, no subscription, and nothing is billed on structured validation errors.

## Output

A JSON object containing a boolean field indicating whether the supplied year is a leap year under Gregorian calendar rules (divisible by 4, except century years unless also divisible by 400). Response is deterministic and first-party; no external data sources are consulted.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "year": {
   "type": "integer",
   "maximum": 9999,
   "minimum": 1,
   "description": "Gregorian calendar year."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "year": 2028,
  "schema": "delx/is-leap-year/v1",
  "is_leap_year": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/leap-year-check-09d58375/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.delx.ai](https://www.zero.xyz/host/api.delx.ai/llms.txt)
