* **Please tell us about yourself (include an email address):** <!-- Ejabath Ejabath1@gmail.com Project Lead & Technical Coordinator I am working on digitizing a scholarly Quranic index originally authored by my father, a respected Islamic scholar from Kerala, India. The original work is a comprehensive Malayalam-language concordance that maps Quranic concepts to their precise verse locations (Surah:Ayah) with detailed contextual descriptions. I am now leading the effort to transform this into a multilingual digital platform to serve the global Muslim community. --> * **Your purpose in using this API:** <!-- Our platform is a scholarly-grade Quranic concordance that goes beyond simple translation search. When a user searches for a concept (e.g., "milk", "prayer", "charity"), we display: All Quranic verses (ayahs) where that concept appears, with precise Surah:Ayah references Contextual descriptions explaining how each verse relates to the searched concept Cross-references to semantically related concepts Hadith references from authentic collections to provide complementary Prophetic guidance Specific API use cases: Fetching hadiths related to Quranic concepts to display alongside ayah results Validating concept connections through authenticated narrations Enabling users to explore the Sunnah context of Quranic themes Supporting academic research by linking Quranic concordance with hadith evidence Target audience: Islamic scholars and students of knowledge General Muslims seeking deeper understanding of the Quran Academic researchers in Islamic studies Malayalam-speaking Muslim community (primary) expanding to global audiences Project status: Currently in MVP development phase. We have digitized the original Malayalam index and are building the multilingual web platform. --> * **API rate limits:** <!-- Maximum requests per second: 2 requests/second Maximum requests per day: 5,000 requests/day Rationale: Our platform is read-heavy with scholarly content. Users search concepts and we display cached Quran results with live hadith cross-references. We will implement aggressive caching (Redis) to minimize API calls. Most hadith data will be fetched once per concept and cached indefinitely, as hadith collections are static.** * **Is your use case better served by having an offline dump of hadith data or programmatic API access?** <!-- Offline Dump vs. Programmatic API Access We prefer: Offline dump of hadith data Reasoning: Performance: Our platform targets users in regions with limited internet connectivity (rural India, Africa, etc.). Offline data ensures instant access without latency. Reliability: We want to avoid dependency on live API availability for core content delivery. Cost efficiency: Reduces server costs and API rate limit concerns as we scale. Offline capability: We plan to offer offline/PWA functionality where users can access the full platform without internet. However, we would also value programmatic API access for: Initial data population and validation Occasional updates when new collections or corrections are added Supporting features that require real-time hadith search beyond our curated cross-references Ideal scenario: An offline dump for our primary database + API access for supplemental features and updates. --> * **What are the languages in which would you like hadith data?** <!-- Primary languages requested: English - For global accessibility and our primary international audience Arabic - For original text verification and scholarly users Urdu - For South Asian Muslim community (India, Pakistan, Bangladesh) Secondary languages (if available): 4. Malayalam - For our core Kerala/Malayali user base 5. Indonesian - For Southeast Asian Muslim community (largest Muslim population country) 6. Turkish - For Turkish-speaking Muslim community Note: We understand not all languages may be available for all collections. English and Arabic are our critical requirements; additional languages are highly valued but not blockers. --> * **What programming language will your API client be in?** <!-- Primary language: JavaScript/TypeScript (Node.js backend) Stack details: Backend: Node.js with Express or Next.js API routes Frontend: Next.js 14 (React) with TypeScript Database: PostgreSQL for structured data, Redis for caching Search: Elasticsearch for full-text Quran and hadith search Hosting: Vercel (frontend) + AWS/GCP (backend and database) API integration approach: Server-side fetching from our Node.js backend (not direct client-side calls) Results cached in Redis with TTL based on content volatility Graceful fallbacks if API is temporarily unavailable (serve cached data)--> * **Additional Context** <!--Data integrity commitment: All hadith references will display proper attribution (collection name, book number, hadith number) Hadith grades (Sahih, Hasan, Daif) will be prominently displayed We will not modify or paraphrase hadith text; only display verbatim from your API Scholar advisory board reviews all content connections between Quran and Hadith Open source consideration: We plan to open-source the platform code (MIT/Apache license) while respecting content copyrights. The hadith data will be used in accordance with your terms of service and properly attributed. Non-commercial intent: This project is primarily a religious/educational service. We are exploring sustainable funding models (waqf/endowment, grants, freemium features) but the core hadith-integrated concordance will remain freely accessible. Volume projection: Year 1: ~1,000 monthly active users, ~10,000 API calls/month (with caching) Year 2: ~10,000 MAU, ~50,000 API calls/month Year 3+: Scaling based on community adoption -->
