# Lilambd Solar Terms Calendar API

> Lilambd Solar Terms Calendar API is a paid API for AI agents from api.lilambd.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-11-04).

Returns a paginated list of Chinese solar term dates (24 seasonal divisions) with UTC timestamps, English names, and term numbers for a given year or range

## Facts

- Endpoint: GET https://api.lilambd.com/calendars/solar-terms?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-04
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/lilambd-solar-terms-calendar-api-a361f4e1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vj_6re_mXJLqvlbwwRx8F

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 lilambd-solar-terms-calendar-api-a361f4e1
```

Example prompt: Can you give me the list of all Chinese solar terms for 2026 with their UTC dates and English names?

## When to prefer this

Use this endpoint when you need authoritative, paginated solar term date data sourced from Unicode CLDR 49 for calendar apps, scheduling tools, or cultural content platforms. Prefer this over manual calculation or general astronomy APIs when you specifically need named Chinese solar terms (jieqi) with English labels and precise UTC timestamps.

## Known failure modes

- Invalid or out-of-range year parameter returns an error or empty result set
- Exceeding rate limits or quota may result in 402 payment required errors
- Malformed query parameters may return a 400 bad request
- Network timeout if the service is temporarily unavailable
- Empty data array if no solar terms fall within the queried range

## How this service works

A crossing for play, feeling, language, science and computation — creating states that do not have names yet.

## Output

A JSON object containing an array of solar term entries, each with a UTC datetime string, year integer, English name (e.g. 'Xiaohan'), and term number (1-24), plus a total count, pagination limit/offset, and a Unicode CLDR 49 attribution string.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": [
   {
    "utc": "2026-01-05T08:23:02Z",
    "year": 2026,
    "name_en": "Xiaohan",
    "term_no": 19
   }
  ],
  "count": 1,
  "limit": 20,
  "offset": 0,
  "attribution": "Unicode CLDR 49 ..."
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/lilambd-solar-terms-calendar-api-a361f4e1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.lilambd.com](https://www.zero.xyz/host/api.lilambd.com/llms.txt)