Select the analysis
Choose the business question, institution, branches and reporting date.
A vendor-neutral foundation for secure CBS/MIS APIs and optional MCP clients. Each connection must be approved for the institution and verified against the actual source product and version.
The selected analysis defines the required fields, branch scope, date window and financial definitions. The same current policy must apply to the human UI, API, jobs and optional MCP tools.
Choose the business question, institution, branches and reporting date.
Review the immutable analysis manifest: purpose, fields, scope, grain and approved source.
Minimize fields before crossing the boundary. Unsupported upstream filtering blocks the request or requires an approved institutional edge.
Check schemas, totals, currencies, dates, pagination and conflicts before accepting a new snapshot.
Vendor-neutral means adapters share a common contract. It does not mean every installed product is already connected or that source access is automatically approved.
| Connection path | Institutional prerequisites | Current scope |
|---|---|---|
| Authorized exported files | Approved export schema, dates, mappings and reconciliation controls. | Synthetic browser demonstrations; production inputs require the review process. |
| Secure CBS/MIS API | Product/version documentation, approved sandbox, minimum-field projection and read-only source permission. | Shared planning and adapter contracts under implementation; live vendor conformance pending. |
| Institution-side edge | Separately approved edge that filters within the institution when the source cannot safely project data. | Architecture provision; no installed edge or new network grant. |
| Optional MCP facade | Approved client, maintained protocol/SDK, intended-resource authorization and the same current institution policy. | Contracts and implementation work; no live model connection or permissions granted. |
The integration does not approve loans, change customer records, disburse funds or write to the CBS ledger.
Preserve currency, scale, business date, calendar and namespace. Require a compatible country/engine pack; do not relabel INR or USD as NPR.
No arbitrary SQL, URLs or field lists; no token passthrough or model-created permissions. Recheck handles, jobs, caches, results and exports.
The synthetic contract reference is checked. Actual authenticated API/MCP and vendor-version release cases remain pending against the implemented service. A working adapter requires its own conformance evidence.
Bring a vendor/version, an approved schema or sandbox and a clear analysis objective. Do not send production credentials or borrower records by email.
A synthetic design preview with placeholder charts, geographic drill-down and proposed data integrations. No institution account or live data feed is connected.