> For the complete documentation index, see [llms.txt](https://cifer.gitbook.io/cifer-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cifer.gitbook.io/cifer-docs/documentation/cifer-sdk/sdk-reference/namespace-map.md).

# Namespace map

## Core namespaces

| Namespace            | Main responsibility                                                   | Generated reference                                                                      |
| -------------------- | --------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
| `keyManagement`      | Secret state, fees, readiness, transaction intents, and event parsing | [Open](https://sdk.cifer-security.com/docs/api/namespaces/keyManagement)                 |
| `blackbox.payload`   | Text and record encryption/decryption                                 | [Open](https://sdk.cifer-security.com/docs/api/namespaces/blackbox.namespaces/payload)   |
| `blackbox.files`     | File upload and result download                                       | [Open](https://sdk.cifer-security.com/docs/api/namespaces/blackbox.namespaces/files)     |
| `blackbox.jobs`      | Asynchronous job state and polling                                    | [Open](https://sdk.cifer-security.com/docs/api/namespaces/blackbox.namespaces/jobs)      |
| `blackbox.publicKey` | Public-key retrieval                                                  | [Open](https://sdk.cifer-security.com/docs/api/namespaces/blackbox.namespaces/publicKey) |
| `commitments`        | Storage intents, metadata, logs, and integrity                        | [Open](https://sdk.cifer-security.com/docs/api/namespaces/commitments)                   |
| `flows`              | High-level planning and execution                                     | [Open](https://sdk.cifer-security.com/docs/api/namespaces/flows)                         |

## Web2 namespaces

| Namespace           | Responsibility                                                   |
| ------------------- | ---------------------------------------------------------------- |
| `web2.auth`         | Registration, verification, keys, password and account lifecycle |
| `web2.session`      | Session creation and management                                  |
| `web2.secret`       | Principal-based secret operations                                |
| `web2.delegate`     | Delegated access                                                 |
| `web2.permit`       | Permit authorization                                             |
| `web2.principal`    | Principal information                                            |
| `web2.blackbox`     | Session-aware payload, file, job, and public-key wrappers        |
| `web2.createClient` | Stateful recommended Web2 interface                              |

Use the [complete generated API](https://sdk.cifer-security.com/docs/api) for individual signatures and exported types.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cifer.gitbook.io/cifer-docs/documentation/cifer-sdk/sdk-reference/namespace-map.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.