> 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/why-sna.md).

# Why SNA?

Sahamati evaluated two options for how AAs should report SLA metrics. The following comparison, agreed upon with the AA community, guided the decision to build and distribute SNA:

| Option 1: AA Gathers & Reports Independently          | Option 2: AA Uses SNA (Recommended)              |
| ----------------------------------------------------- | ------------------------------------------------ |
| ✔ AA-controlled changes                               | ✔ Uniform interpretation across all AAs          |
| ✘ Interpretations may vary across AAs                 | ✔ Minimal integration effort for AAs             |
| ✘ Each AA must implement all reporting logic          | ✔ Future changes: redeploy SNA, no code changes  |
| ✘ Future schema changes require AA engineering effort | \~ AAs maintain one additional cluster component |

The SNA approach ensures that Sahamati can centrally update calculation logic, definitions, schema, and all AAs benefit immediately by simply deploying the new version of SNA.

This leads to:

* Faster ecosystem-level consistency
* Lower engineering burden on individual AAs.

#### Extending SNA to Billing

The same approach now applies to billing. Rather than each AA building separate reporting logic for billing, AAs capture transaction metadata at the AA-FIU interface through the same `sna.dispatch()` method already used at the AA-FIP interface. SNA provides a single, uniform source of data for billing across all AAs.

For data fetches, the AA passes the consent types of the approved consent to SNA. This lets SNA identify whether a fetch is for transactions or for profile and summary only, since these may be billed differently.

#### Accurate Latency Measurement

The AA passes its own timestamp for every request and response it sends or receives. Latency calculations therefore do not depend on the clock of the peer FIP or FIU being in sync.

#### Minimal Data Sharing

AAs that prefer not to share the encrypted FI payload with SNA can redact the `encryptedFI` field in FI/fetch responses and send only its length. SNA uses this length to calculate data volumes


---

# 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/why-sna.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.