Quran API
✓ Official Vendor SpecData EnrichmentData Transformationnone18 EndpointsREST
For Agents
Programmatically list all chapters (surahs), get a specific chapter. Covers 18 operations.
Use for: I need to all chapters (surahs), I want to a specific chapter, Search for chapter info/metadata, Find all verses by chapter number
Not supported: Does not handle payments, communications, or crm — use for data enrichment only.
RESTful API for accessing Quran text, translations, audio recitations, and related data. The API exposes 18 endpoints.
Install Jentic One Beta
Connect the Quran API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Quran 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.
1
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 | sh2
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 instanceJentic 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 Quran API.
List all chapters (surahs)
Get a specific chapter
Access Quran API data enrichment resources via REST API
Use Cases
Patterns agents use Quran API for, with concrete tasks.
★ Data Enrichment Operations
Use the Quran API to perform data enrichment operations programmatically. The API provides 18 endpoints covering core functionality including list all chapters (surahs), get a specific chapter, get chapter info/metadata.
Call GET /chapters to list all chapters (surahs)
Automated Audio Management
Automate audio operations by combining multiple Quran API endpoints. Agents can get a specific chapter and then get chapter info/metadata in a single workflow.
Call GET /chapters/{id} to get a specific chapter, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Quran API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.
Search Jentic for 'list all chapters (surahs)', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
18 endpoints — restful api for accessing quran text, translations, audio recitations, and related data.
METHOD
PATH
DESCRIPTION
GET
/chapters
List all chapters (surahs)
GET
/chapters/{id}
Get a specific chapter
GET
/chapters/{chapter_id}/info
Get chapter info/metadata
GET
/verses/by_chapter/{chapter_number}
Get verses by chapter number
GET
/verses/by_page/{page_number}
Get verses by Mushaf page
GET
/verses/by_juz/{juz_number}
Get verses by juz number
GET
/verses/by_hizb/{hizb_number}
Get verses by hizb number
GET
/verses/by_key/{verse_key}
Get a specific verse by key (e.g. 1:1)
GET
/chapters
List all chapters (surahs)
GET
/chapters/{id}
Get a specific chapter
GET
/chapters/{chapter_id}/info
Get chapter info/metadata
GET
/verses/by_chapter/{chapter_number}
Get verses by chapter number
GET
/verses/by_page/{page_number}
Get verses by Mushaf page
GET
/verses/by_juz/{juz_number}
Get verses by juz number
GET
/verses/by_hizb/{hizb_number}
Get verses by hizb number
GET
/verses/by_key/{verse_key}
Get a specific verse by key (e.g. 1:1)
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Quran API none credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'list all chapters (surahs)') and Jentic returns the matching Quran API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Quran API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Quran API through Jentic.
What authentication does the Quran API use?
The Quran API uses no authentication. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I list all chapters (surahs) with the Quran API?
Yes. Use the GET /chapters endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Quran API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I list all chapters (surahs) through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'list all chapters (surahs)'. Jentic returns the matching Quran API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Quran API have?
The Quran API exposes 18 endpoints covering audio, chapters, juzs operations.
GET STARTED