> For the complete documentation index, see [llms.txt](https://developer.sahamati.org.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.sahamati.org.in/sahamatinet-agent-sna/overview.md).

# Overview

SahamatiNet Agent (SNA) is a lightweight, standalone agent developed by Sahamati and deployed within an Account Aggregator's (AA's) own infrastructure. SNA is responsible for aggregating and sending required metrics to Sahamati's endpoint on behalf of the AA, without requiring the AA's to write or maintain code that implements complex metric-capture logic.

### Key Capabilities

* Runs entirely within the AA's infrastructure; no data leaves unless pushed to Sahamati's endpoint.
* Captures request and notification metrics across all FIP-side and FIU-side AA APIs.
* Aggregates data and pushes structured JSON payloads to Sahamati every 10 minutes.
* Is versioned and upgradeable; AAs simply redeploy a new Helm chart version; no code changes needed.
* Provides uniform, schema-consistent data across all AAs for fair SLA benchmarking and billing.

### Current Phase of Deployment

Sahamati is currently requesting all AAs to:

1. Deploy the latest SNA image to the UAT environment
2. Integrate at the AA-FIP interface.
3. Integrate at the AA-FIU interface.
4. Send the additional attributes (`addlAttr`) applicable to each API, on both interfaces.
5. Validate the integration in UAT, then deploy to Production.

📌 **AAs already integrated at the AA-FIP interface:** your existing A–D integration must also be updated. The `eventTime` attribute is now required on every `sna.dispatch()` call, including AA-FIP calls. Other attributes, such as `consentTypes` and `fiFetchEncDataLen`, apply to specific AA-FIP APIs as well.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.sahamati.org.in/sahamatinet-agent-sna/overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.