Research agent · not a lookup table
Bank paperwork, researched live and cited line by line.
Name the transaction, the bank, the applicant, and the state. Kaagaz normalizes the question, checks its research record, searches the live web when needed, and returns one ordered checklist with costs, timelines, regulator attribution, and the sources it actually read.
You ask once. You tick everything off. You keep the receipts.
-
Live research, not a fixed menu
Unknown banks, products, and spellings pass through. Anything outside the cache is researched, then filed.
-
Sources you can open
No anonymous “generally required” list. Every checklist keeps the exact URLs behind its claims.
-
Regulator-aware answers
RBI rules, state stamp acts, registrar procedure, and bank policy are labeled separately—and never mixed.
-
Freshness with a date
Repeat questions answer instantly from cache, show when they were researched, and refresh through live search.
Ask in your own words
-
Describe the transaction
any bank, any state -
We search, read and cite
the primary sources -
Tick off each document
as you collect it
Or start from something common
Architecture
A pipeline built to be audited.
Search and generation are deliberately separate operations. That separation lets Kaagaz control citations, survive one provider outage without losing the other, and store every answer with the evidence used to construct it.
-
Normalize the request
Transaction, bank, state, and residency are canonicalized for matching. Unknown values are preserved because they may be the most important part of the question.
-
Check the research record
Fresh entries answer immediately. A stale entry can be served transparently when live research fails, with its age displayed.
-
Search and read sources
Direct keyless search finds candidate pages; the app fetches and reads the text. A model-backed web-search fallback is used only when direct search is unavailable.
-
Generate through a provider chain
Structure comes from an ordered registry, not one API. Providers without keys are skipped; unavailable providers are temporarily removed from rotation.
-
Enforce honesty in code
Figures must be sourced. Stamp duty is never attributed to the RBI. Rates are published as bands. Missing disclosures are stated explicitly.
-
File one audit record
The checklist, query, sources, timestamps, model, and provider are stored together. The result page can show that exact research record.
Search and generation can fail independently. That is intentional: a search outage does not disable structuring, and a generation outage does not erase retrieved evidence. When both are unavailable, the interface suggests the closest cached research instead of displaying an empty error.
What we already know
Questions judges usually ask
Why are bank, state, and residency all required?
Because each changes the documents. A bank imposes its own proofs, a state controls stamp duty and registration, and residency determines FEMA and attestation requirements. Removing any input would make some correct answers impossible.
What happens when live search is blocked?
Kaagaz first serves a stale answer if one exists. Otherwise it reports the outage and recommends cached cases with overlapping transactions or banks, so the visitor can still make progress.
Why does it show a rate band instead of one rate?
Published loan pricing varies by credit score, amount, tenure, and fees. A single number would imply a guarantee the bank did not make. Kaagaz therefore reports the sourced band—or says the rate is not publicly disclosed.
Is this legal or financial advice?
No. It is an informational research tool. Every material decision should be checked against the cited bank page, registrar notification, RBI direction, or a qualified professional.