# Lilambd Calendar Converter — Non-Gregorian to Gregorian

> Lilambd Calendar Converter — Non-Gregorian to Gregorian 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).

Converts a date from a non-Gregorian calendar system (e.g. Ethiopic) into its Gregorian equivalent, returning the Julian Day Number and formatted Gregorian date.

## Facts

- Endpoint: GET https://api.lilambd.com/calendars/to-gregorian?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-calendar-converter-non-gregorian-to-gregorian-8dd4e228
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ZweN60UEdcPwS1r-E07EP

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-calendar-converter-non-gregorian-to-gregorian-8dd4e228
```

Example prompt: What is the Gregorian date for January 1, 2019 in the Ethiopic calendar? I need the Julian Day Number too.

## When to prefer this

Use this endpoint when you need to convert a date from a specific non-Gregorian calendar system (such as Ethiopic, Julian, Hebrew, or Islamic) into the standard Gregorian calendar, especially when you also need the Julian Day Number for precise chronological calculations. Prefer this over manual lookup tables or general-purpose date libraries when you want a simple API call with reliable output for cultural or historical calendar systems.

## Known failure modes

- Invalid or unrecognized calendar name returns an error or empty result
- Malformed date string (wrong format or out-of-range) may return an error
- Unsupported calendar systems not implemented by the API will fail
- Missing required query parameters result in a bad request error
- Network or payment (x402) failures prevent the response from being returned

## How this service works

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

## Output

Returns a JSON object with the original input date, the named calendar system, the computed Gregorian date string, and the Julian Day Number (JDN) — plus an attribution field. Example: {jdn: 2461295, input: '2019-01-01', calendar: 'ethiopic', gregorian: '2026-09-11'}.

## 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": {
   "jdn": 2461295,
   "input": "2019-01-01",
   "calendar": "ethiopic",
   "gregorian": "2026-09-11"
  },
  "attribution": "..."
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/lilambd-calendar-converter-non-gregorian-to-gregorian-8dd4e228/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)