Install Jentic One Beta

Connect the Amanah Sunnah API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Amanah Sunnah 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Famanahagent.cloud%2Famanahagent" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Famanahagent.cloud%2Famanahagent" | 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 Amanah Sunnah API.

Look up a Quran ayah or a hadith by its reference key

Run hybrid semantic and keyword search across the verse and hadith corpus

Ask a question and get an answer with supporting dalil from verified references

Retrieve Tafsir Ibn Kathir for a given ayah

Search hadith narrators and read Aqidah and Tawhid explanations

GET STARTED

Start building with Amanah Sunnah API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Amanah Sunnah API for, with concrete tasks.

★ AI agent answering Islamic questions with sources

An assistant needs to answer questions about Islamic practice while citing where each answer comes from. Through Jentic the agent searches for asking a question with supporting dalil, loads the question-answering operation with the API key already injected, and returns an answer grounded in the verified corpus rather than the model's own recollection. The citations let a reader verify each point.

Call POST /ask with a question about fasting and return the answer together with the dalil references it cites

Quran and hadith lookup bot

A study bot resolves a reference the user gives, such as a surah and ayah or a hadith key, and returns the text plus its tafsir. The Amanah Sunnah API fetches a single ayah or hadith by key and serves Tafsir Ibn Kathir for an ayah, so the bot can show the verse, its explanation, and the hadith it mentions. This turns a reference into a complete reading in one exchange.

Call GET /quran/{key} for the ayah, then GET /tafsir/{key} to attach its Tafsir Ibn Kathir

Semantic study assistant

A learner asks about a theme rather than a specific reference, such as patience or gratitude. The API's hybrid search combines semantic matching with keyword matching across verses and hadith, so an agent can surface the most relevant passages even when the user's wording does not match the text exactly. Results come back ranked for the agent to summarize.

Call POST /search with the query 'patience in hardship' and return the top matching verses and hadith

Daily sunnah reminders

A reminder agent pulls the recommended practices, duas, and calendar events for the day to prompt a user. The Amanah Sunnah API lists daily sunnah practices, authentic duas, and sunnah calendar events, so the agent can assemble a short daily message grounded in the corpus. This keeps the content consistent and sourced rather than freely generated.

Call GET /amalan for today's practices and GET /doa for a matching dua, then compose a reminder

Key Endpoints

20 endpoints — the amanah sunnah api provides programmatic access to a verified islamic knowledge base covering quran verses, tafsir ibn kathir, hadith from seven major collections, narrator records, aqidah and tawhid texts, duas, and daily sunnah practices.

METHOD

PATH

DESCRIPTION

POST

/search

Run hybrid semantic and keyword search over the corpus

POST

/ask

Ask a question and get an answer with dalil

GET

/quran/{key}

Get a Quran ayah by reference key

GET

/hadith/{key}

Get a hadith by reference key

GET

/tafsir/{key}

Get Tafsir Ibn Kathir for an ayah

GET

/rijal

Search hadith narrators

GET

/amalan

Get daily sunnah practices

POST

/search

Run hybrid semantic and keyword search over the corpus

POST

/ask

Ask a question and get an answer with dalil

GET

/quran/{key}

Get a Quran ayah by reference key

GET

/hadith/{key}

Get a hadith by reference key

GET

/tafsir/{key}

Get Tafsir Ibn Kathir for an ayah

GET

/rijal

Search hadith narrators

GET

/amalan

Get daily sunnah practices

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Amanah Sunnah API by hand means obtaining an API key, sending it in the X-API-Key header on every call, and handling the request shapes for its hybrid search and question-answering endpoints yourself. Through Jentic you install once, import Amanah Sunnah from the API Directory, store the key once, and your agent calls it.

Permission scoping

The Amanah Sunnah API is mostly read lookups and search, with a lecture submission webhook as its one write path. You choose the operations your agent may call, so you can allow the verse, hadith, and search reads and leave the lecture submission out of the allowed set unless you add it.

Credential isolation

Your Amanah Sunnah key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'search Islamic texts' or 'get a Quran ayah', and Jentic returns the matching Amanah Sunnah operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using Amanah Sunnah API through Jentic.

What authentication does the Amanah Sunnah API use?

The Amanah Sunnah API authenticates with an API key sent in the X-API-Key request header, per its OpenAPI spec. Every operation in the spec expects that header. Through Jentic the key is stored once and injected at call time, so the agent never handles the raw key.

Can I get an answer with supporting evidence from the Amanah Sunnah API?

Yes. Call POST /ask with a natural-language question and the API returns an answer together with the dalil it draws from the verified corpus, rather than an unsourced generation. For passage discovery without a full answer, POST /search returns ranked verses and hadith for a query.

What are the rate limits for the Amanah Sunnah API?

The OpenAPI spec does not define request-rate ceilings. Limits are tied to the issued API key and the plan it belongs to. Check the Amanah Sunnah developer documentation for the quota on your key before running large search or question-answering batches.

Is there an Amanah Sunnah API MCP server?

You don't need an MCP server to give your agent the Amanah Sunnah API. Jentic connects it directly from the API Directory: import the API, store your key once, and your agent calls operations such as POST /search on demand without loading another server's tool definitions into its context.

Can I limit what my agent is allowed to do with the Amanah Sunnah API?

Yes. Write a rule that allows only the lookup and search operations, so the agent can read verses, hadith, and tafsir and run searches but cannot submit a lecture to the processing webhook, and every call it makes is logged. The one write path stays out of the allowed set until you add it.

How do I search the hadith corpus through Jentic?

Search Jentic for 'search Islamic texts', load the POST /search operation, and run it after your API key is stored. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Which collections does the Amanah Sunnah API cover?

The corpus spans Quran verses with Tafsir Ibn Kathir, hadith from seven major collections, narrator records, Kitab At-Tawhid chapters, Aqidah texts, duas, daily sunnah practices, the 99 Names of Allah, and lists of known fabricated hadith. An agent can call GET /rijal for narrators or GET /tawhid for Tawhid chapters to work with a specific collection.

Amanahagent Amanah Sunnah API

AI ReadinessFoundational (D)45/100

See full scorecard

Official vendor OpenAPI document · agent-readyAI/MLEmbeddings SearchapiKey20 EndpointsREST

For Agents

Search a verified Islamic knowledge base of Quran, hadith, and tafsir, fetch entries by key, and get natural-language answers with supporting dalil.

Use for: Get the text of a specific Quran ayah, Search the hadith collections for a topic, Ask a question and get an answer backed by dalil, Retrieve Tafsir Ibn Kathir for an ayah

Not supported: Does not issue personal religious rulings, process payments, or host open-ended chat. Use for searching and retrieving verified Islamic texts and sourced answers only.

The Amanah Sunnah API provides programmatic access to a verified Islamic knowledge base covering Quran verses, Tafsir Ibn Kathir, hadith from seven major collections, narrator records, Aqidah and Tawhid texts, duas, and daily sunnah practices. It runs hybrid semantic and keyword search over that corpus and answers natural-language questions with supporting dalil through a retrieval-augmented endpoint. Individual verses, hadith, and tafsir entries can also be fetched directly by reference key.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: C+Signals: 4

11%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

26%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

31%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

49%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: ASignals: 1

81%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Amanah Sunnah API to your agent

Capabilities

Start building with Amanah Sunnah API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Amanahagent Amanah Sunnah API

Jentic AI Readiness Score

Amanah Sunnah API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness