Al-Quran Cloud API

Name: Al-Quran Cloud API
Brand: Al-Quran Cloud API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaContent Deliverynone23 EndpointsREST

For Agents

Read Quranic text, translations, transliterations, and audio recitations across multiple editions through 23 unauthenticated endpoints. Useful for agents building study tools, reading apps, or daily-verse delivery.

Install Jentic One Beta

Connect the Al-Quran Cloud API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Al-Quran Cloud API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Al-Quran Cloud API.

Retrieve a full surah by number with the original Arabic and any chosen edition

Get a single ayah by reference (e.g., 2:255) in the original or a translation

Pull divisions of the Quran by juz, manzil, ruku, page, or hizb quarter

GET STARTED

Start building with Al-Quran Cloud API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Al-Quran Cloud API for, with concrete tasks.

★ Daily Verse and Reading Plan Apps

Mobile app developers wire daily-verse and structured reading-plan features off the juz, page, and ayah endpoints. The API serves both Arabic and a chosen translation in one response, so the app can show the original text and its translation side by side without managing the corpus locally.

Call GET /juz/1/quran-uthmani and GET /juz/1/en.sahih in parallel, then assemble each ayah pair into the day's reading plan view.

Quran Study and Search Tools

Study platforms expose keyword search across the original Arabic and translation editions through the /search endpoint, then deep-link results back to the surah/ayah views. Because the API exposes editions for transliteration and translations, the same study session can show meaning, pronunciation, and original text together.

Call GET /search with keyword 'mercy' and edition en.sahih, take the first result's surah and ayah, and call GET /ayah/{reference}/quran-uthmani to retrieve the original Arabic.

Audio Recitation Playback

Listen-along players use the audio editions surfaced by the API to stream recitations by reciter, surah, or ayah. The /edition endpoint lists the available recitation editions, and the surah/ayah endpoints in those editions return URLs to the audio assets, so a player can build a reciter picker without bundling audio metadata locally.

Call GET /edition?format=audio to list available reciters, then GET /surah/36/ar.alafasy to retrieve the audio URL for Surah Yasin.

AI Agent Quran Lookups via Jentic

An AI agent built on Jentic can field questions like 'show me Ayat al-Kursi in English with the Arabic' and resolve them to the right ayah-by-reference call without manual URL construction. Because the API is unauthenticated, no credentials are needed; Jentic still routes the request through its standard execution layer for logging and retries.

Search Jentic for 'get an ayah by reference', load the /ayah/{reference}/{edition} schema, and execute it twice for reference 2:255 with editions quran-uthmani and en.sahih.

Key Endpoints

23 endpoints — jentic publishes the only available openapi specification for al-quran cloud api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/surah

List all surahs

GET

/surah/{number}/{edition}

Get a surah in a specific edition

GET

/ayah/{reference}/{edition}

Get an ayah by reference in a chosen edition

GET

/juz/{number}/{edition}

Get a juz in a chosen edition

GET

/page/{number}

Get a Quran page by number

GET

/search

Search the Quran text and translations

GET

/edition

List available text and audio editions

GET

/meta

Get Quran metadata (counts of surahs, juzs, pages, etc.)

GET

/surah

List all surahs

GET

/surah/{number}/{edition}

Get a surah in a specific edition

GET

/ayah/{reference}/{edition}

Get an ayah by reference in a chosen edition

GET

/juz/{number}/{edition}

Get a juz in a chosen edition

GET

/page/{number}

Get a Quran page by number

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Al-Quran Cloud API requires no credential, so there is nothing for your Jentic One instance to store, and no secret enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'fetch a surah in a given edition' or 'search the Quran text', and Jentic returns the matching Al-Quran Cloud operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Al-Quran Cloud API through Jentic.

Why is there no official OpenAPI spec for Al-Quran Cloud API?

Al-Quran Cloud does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Al-Quran Cloud API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Al-Quran Cloud API use?

None. The API is fully open and does not require an API key, OAuth token, or sign-up. Through Jentic the call is still routed through the standard execution layer for retry handling and logging.

Can I retrieve a single ayah with translation using the Al-Quran Cloud API?

Yes. Call GET /ayah/2:255/en.sahih for a translated ayah by reference, and GET /ayah/2:255/quran-uthmani in parallel for the original Arabic. The reference format is surah:ayah.

What are the rate limits for the Al-Quran Cloud API?

The API does not publish hard per-key rate limits because it is unauthenticated, but it is community-funded - keep request volume reasonable, cache aggressively at edge or app level, and retry with backoff on 429 or 5xx responses.

How do I look up Ayat al-Kursi through Jentic?

Search Jentic for 'get an ayah by reference', load the /ayah/{reference}/{edition} schema, and execute with reference=2:255 and edition=en.sahih. No credentials are needed; Jentic still wraps the call for retries.

Does the Al-Quran Cloud API serve audio recitations?

Yes. Call GET /edition with format=audio to list reciter editions, then GET /surah/{number}/{edition} (e.g., ar.alafasy) to retrieve URLs to the audio assets for that surah.

Can I limit what my agent is allowed to do with the Al-Quran Cloud API?

Yes. Because you run Jentic One yourself, your own rules decide which Al-Quran Cloud operations the agent may call, and this API is read-only, so you can permit the text and audio reads you want and block the rest. Since the surah number, ayah reference, and edition all sit in the URL path (/surah/{number}/{edition}, /ayah/{reference}/{edition}, /juz/{number}/{edition}), a rule can pin the agent to a single edition or division. The API needs no credential, so there is no secret for the agent to hold, and you control access purely by which endpoints you allow.