Convert Gregorian dates to Hijri (Umm al-Qura calendar) and back
Convert Gregorian dates to Hijri (Umm al-Qura calendar) and back. Returns day/month/year, Arabic and English month names, and a formatted Arabic date string. Essential for agents handling Islamic events, Ramadan, Hajj seasons, or Arabic documents.
by api.qist.info · discovered, not yet claimed by its owner · updated 2026-10-13
Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.
What it does
Convert Gregorian dates to Hijri (Umm al-Qura calendar) and back. Returns day/month/year, Arabic and English month names, and a formatted Arabic date string. Essential for agents handling Islamic events, Ramadan, Hajj seasons, or Arabic documents.
Tags: islamic · hijri · calendar · date-conversion · umm-al-qura · bazaar
Call contract
- Method
- GET
- Input
- query parameters
- Output
- json
- Last paid call
- 2026-10-13
{
"date": "2026-08-03"
}{
"calendar": "Umm al-Qura",
"gregorian": "2026-08-03",
"hijri": {
"date": "1448-02-19",
"day": 19,
"formattedAr": "19 صفر 1448هـ",
"month": 2,
"monthNameAr": "صفر",
"monthNameEn": "Safar",
"year": 1448
},
"weekdayEn": "Monday"
}Use with an agent
- Discover. Agents find this listing with
GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP toolsearch_resources, or/discovery/resources. - Inspect. Fetch
/resources/26935.jsonfor the price and payment options. - Pay. Call
GET https://api.qist.info/api/hijri. The provider answers402with its payment requirements. An x402 client signs one of the options below and retries withPAYMENT-SIGNATURE. - Execute. The provider returns
200with the data. Agent Bazaar is not in the request path and never sees your payment.
For humans
You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.
Pricing & payment
- Price
- $0.01 / request
- Protocol
- x402 v2
- Auth
- No account or API key. Pay per request.
- Networks
- Base
- Demand
- 8 calls · 8 unique payers in 30d (public x402 Bazaar data)
x402 payment requirements
| Scheme | Network | Asset | Amount | Pay to | Timeout |
|---|---|---|---|---|---|
| exact | Base eip155:8453 | USDC | $0.01 | 0x21353452E547B306a6007d834C433a118638D3b3 | 300s |
accepts[] (raw JSON)
[
{
"scheme": "exact",
"network": "eip155:8453",
"payTo": "0x21353452E547B306a6007d834C433a118638D3b3",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "10000",
"amountUsd": 0.01,
"maxTimeoutSeconds": 300
}
]Schemas
Output schema (JSON Schema)
{
"properties": {
"example": {
"type": "object"
},
"type": {
"type": "string"
}
},
"required": [
"type"
],
"type": "object"
}Example shape — generated from the schema, not a captured live response
{
"example": {},
"type": "string"
}Examples
curl -X GET 'https://api.qist.info/api/hijri'
# -> 402 Payment Required; read PAYMENT-REQUIRED
# retry the identical request with PAYMENT-SIGNATUREconst res = await fetch("https://api.qist.info/api/hijri", {
"method": "GET"
});
if (res.status === 402) {
const { accepts } = await res.json();
// pay one of accepts[] via an x402 client, then retry with the payment header
}import httpx
res = httpx.request("GET", "https://api.qist.info/api/hijri")
if res.status_code == 402:
accepts = res.json()["accepts"]
# pay one of accepts[] via an x402 client, then retry with the payment headerDetails
- Provider
- api.qist.info
- Endpoint
- https://api.qist.info/api/hijri
- Machine-readable
/resources/26935.json