api.duoleads.com
https://api.duoleads.com/v1/time/calendarShares a payout wallet with 32 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.
Convert a Gregorian date to other calendar systems and back: Islamic (both the tabular civil calendar and the Umm al-Qura variant), Hebrew, Japanese imperial era, Republic of China, Buddhist and Persian. Also computes Easter Sunday for a year in both the Gregorian and Julian reckonings. Uses the calendar support built into the runtime, with the algorithm named in every response.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
100.0% avgResponse time
p50 8ms · p95 19msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 9/29/2026, 9:00:00 AM | 100% | 1 | 7ms |
| 9/29/2026, 10:00:00 AM | 100% | 1 | 6ms |
| 9/29/2026, 12:00:00 PM | 100% | 1 | 7ms |
| 9/29/2026, 2:00:00 PM | 100% | 1 | 7ms |
| 9/29/2026, 4:00:00 PM | 100% | 1 | 6ms |
| 9/29/2026, 7:00:00 PM | 100% | 1 | 7ms |
| 9/29/2026, 9:00:00 PM | 100% | 1 | 7ms |
| 9/29/2026, 11:00:00 PM | 100% | 1 | 8ms |
| 9/30/2026, 1:00:00 AM | 100% | 1 | 9ms |
| 9/30/2026, 3:00:00 AM | 100% | 1 | 8ms |
| 9/30/2026, 5:00:00 AM | 100% | 1 | 10ms |
| 9/30/2026, 7:00:00 AM | 100% | 1 | 8ms |
| 9/30/2026, 9:00:00 AM | 100% | 1 | 7ms |
| 9/30/2026, 11:00:00 AM | 100% | 1 | 8ms |
| 9/30/2026, 1:00:00 PM | 100% | 1 | 8ms |
| 9/30/2026, 3:00:00 PM | 100% | 1 | 9ms |
| 9/30/2026, 5:00:00 PM | 100% | 1 | 9ms |
| 9/30/2026, 7:00:00 PM | 100% | 1 | 8ms |
| 9/30/2026, 9:00:00 PM | 100% | 1 | 7ms |
| 9/30/2026, 11:00:00 PM | 100% | 1 | 8ms |
| 10/1/2026, 1:00:00 AM | 100% | 1 | 10ms |
| 10/1/2026, 3:00:00 AM | 100% | 1 | 8ms |
| 10/1/2026, 5:00:00 AM | 100% | 1 | 8ms |
| 10/1/2026, 7:00:00 AM | 100% | 1 | 11ms |
| 10/1/2026, 9:00:00 AM | 100% | 1 | 9ms |
| 10/1/2026, 11:00:00 AM | 100% | 1 | 8ms |
| 10/1/2026, 1:00:00 PM | 100% | 1 | 9ms |
| 10/1/2026, 3:00:00 PM | 100% | 1 | 9ms |
| 10/1/2026, 5:00:00 PM | 100% | 1 | 14ms |
| 10/1/2026, 7:00:00 PM | 100% | 1 | 20ms |
| 10/1/2026, 9:00:00 PM | 100% | 1 | 9ms |
| 10/1/2026, 11:00:00 PM | 100% | 1 | 9ms |
| 10/2/2026, 1:00:00 AM | 100% | 1 | 8ms |
| 10/2/2026, 3:00:00 AM | 100% | 1 | 9ms |
| 10/2/2026, 5:00:00 AM | 100% | 1 | 8ms |
| 10/2/2026, 6:00:00 AM | 100% | 1 | 7ms |
| 10/2/2026, 8:00:00 AM | 100% | 1 | 8ms |
| 10/2/2026, 10:00:00 AM | 100% | 1 | 8ms |
| 10/2/2026, 12:00:00 PM | 100% | 1 | 9ms |
| 10/2/2026, 2:00:00 PM | 100% | 1 | 31ms |
| 10/2/2026, 4:00:00 PM | 100% | 1 | 23ms |
| 10/2/2026, 6:00:00 PM | 100% | 1 | 61ms |
| 10/2/2026, 8:00:00 PM | 100% | 1 | 18ms |
| 10/2/2026, 11:00:00 PM | 100% | 1 | 8ms |
| 10/3/2026, 12:00:00 AM | 100% | 1 | 9ms |
| 10/3/2026, 1:00:00 AM | 100% | 1 | 8ms |
| 10/3/2026, 3:00:00 AM | 100% | 1 | 9ms |
| 10/3/2026, 5:00:00 AM | 100% | 1 | 9ms |
| 10/3/2026, 7:00:00 AM | 100% | 1 | 7ms |
| 10/3/2026, 9:00:00 AM | 100% | 1 | 8ms |
| 10/3/2026, 11:00:00 AM | 100% | 1 | 8ms |
| 10/3/2026, 1:00:00 PM | 100% | 1 | 7ms |
| 10/3/2026, 3:00:00 PM | 100% | 1 | 8ms |
| 10/3/2026, 5:00:00 PM | 100% | 1 | 8ms |
| 10/3/2026, 7:00:00 PM | 100% | 1 | 8ms |
| 10/3/2026, 9:00:00 PM | 100% | 1 | 9ms |
| 10/3/2026, 11:00:00 PM | 100% | 1 | 8ms |
| 10/4/2026, 1:00:00 AM | 100% | 1 | 7ms |
| 10/4/2026, 2:00:00 AM | 100% | 1 | 9ms |
| 10/4/2026, 4:00:00 AM | 100% | 1 | 9ms |
| 10/4/2026, 6:00:00 AM | 100% | 1 | 7ms |
| 10/4/2026, 8:00:00 AM | 100% | 1 | 8ms |
| 10/4/2026, 1:00:00 PM | 100% | 1 | 8ms |
| 10/4/2026, 3:00:00 PM | 100% | 1 | 9ms |
| 10/4/2026, 5:00:00 PM | 100% | 1 | 7ms |
| 10/4/2026, 7:00:00 PM | 100% | 1 | 7ms |
| 10/4/2026, 9:00:00 PM | 100% | 1 | 8ms |
| 10/5/2026, 2:00:00 AM | 100% | 1 | 8ms |
| 10/5/2026, 7:00:00 AM | 100% | 1 | 8ms |
| 10/5/2026, 9:00:00 AM | 100% | 1 | 8ms |
| 10/5/2026, 11:00:00 AM | 100% | 1 | 8ms |
| 10/5/2026, 1:00:00 PM | 100% | 1 | 8ms |
| 10/5/2026, 2:00:00 PM | 100% | 1 | 9ms |
- Availability
- 100
- Latency
- 100
- Security
- 100
- Transparency
- 61
- Activity
- 1
How often it was reachable when we probed it (weight 35%).
How quickly it answers when it is up — fast scores high (weight 20%).
Whether it serves over working TLS / https (weight 15%).
Whether the operator disclosed what it does — description, schema, identity (weight 15%).
Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).
Confidence 100% — how much probe evidence backs this score. A thin history is flagged, not hidden.
See the scoring methodology for exactly how each number is computed.
Payment
- Currencies
- USDC
- Networks
- base
- Facilitator
- unknown
- SDK
- unknown
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- Key-Systems GmbH
- Domain registered
- 2020-10-29
- Hosting network
- CLOUDFLARENET
- Hosting country
- —
Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.
On-chain activity (base)
Payments per day
last payment 10/2/2026Data table
| Day | Payments | Volume (USD) | Paying wallets |
|---|---|---|---|
| 9/28/2026 | 49 | 2.45 | 1 |
| 9/29/2026 | 55 | 2.75 | 1 |
| 10/1/2026 | 33 | 1.65 | 1 |
| 10/2/2026 | 1 | 0.05 | 1 |
This payout wallet is shared: figures cover all 33 endpoints paid at it, since payments cannot be attributed to one of them. Only payments settled on chains and facilitators we index.
Linked by wallet — likely same operator
On-chain agent identity and the x402 endpoint that shares its settlement wallet.
Response schema
{
"properties": {
"data": {
"description": "convert: gregorian, calendars {<id>: {year, month, month_name, day, era, formatted, algorithm}}, and unavailable {<id>: reason} when no to was given and a calendar is undefined for the date. Gregorian input covers years 1-9999 (proleptic Gregorian, so month and month_name always agree with the date given); every field is computed for the whole range, never clamped. A calendar that is undefined for the date is rejected with 400 INVALID_PARAM on date when named in to, and listed in unavailable when to is omitted: japanese before Meiji 1 (1868-10-23) and islamic-umalqura outside its published table (1300-1600 AH, 1882-11-12 to 2174-11-25). islamic and persian are proleptic before their epoch (year 0 and negative years, as ICU computes them). easter: year, rite, date (always the Gregorian date), gregorian_date, julian_date (eastern rite only: the date in the Julian calendar), algorithm (anonymous-gregorian|meeus-julian). islamic is the tabular civil calendar; Hebrew months are numbered from Tishri = 1.",
"properties": {
"algorithm": {
"type": "string"
},
"calendars": {
"additionalProperties": {
"properties": {
"algorithm": {
"type": "string"
},
"day": {
"type": "integer"
},
"era": {
"type": "string"
},
"formatted": {
"type": "string"
},
"month": {
"type": "integer"
},
"month_name": {
"type": "string"
},
"year": {
"type": "integer"
}
},
"required": [
"year",
"month",
"month_name",
"day",
"era",
"formatted",
"algorithm"
],
"type": "object"
},
"description": "keyed by caller-chosen names",
"type": "object"
},
"date": {
"type": "string"
},
"gregorian": {
"type": "string"
},
"gregorian_date": {
"type": "string"
},
"julian_date": {
"type": "string"
},
"rite": {
"type": "string"
},
"unavailable": {
"additionalProperties": {
"type": "string"
},
"description": "keyed by caller-chosen names",
"type": "object"
},
"year": {
"type": "integer"
}
},
"type": "object"
},
"meta": {
"$ref": "#/components/schemas/Meta"
},
"ok": {
"const": true
},
"route": {
"const": "/v1/time/calendar"
},
"version": {
"const": "1.0.0"
}
},
"required": [
"ok",
"route",
"version",
"data",
"meta"
],
"type": "object"
}