> For the complete documentation index, see [llms.txt](https://docs.premia.blue/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.premia.blue/developer-center/sdk/sdk-technical-docs.md).

# SDK Technical Docs

The documentation at [docs-sdk.premia.finance](https://docs-sdk.premia.finance/) provides detailed information about the Premia V3 SDK, an Alpha software used in the Premia Interface. Here's a summary of the key sections:

1. **Alpha Software Warning**: The SDK is considered Alpha software and may contain bugs or significant changes between patch versions.
2. **Development Setup**: Instructions for setting up the development environment, including setting NPM auth tokens, API keys, and running necessary commands.
3. **Anvil Setup**: Guidelines for using Anvil as a local blockchain for development purposes, including installation instructions.
4. **Forking Arbitrum Goerli**: Steps to fork Georli for development, including specific terminal commands.
5. **Contract Deployments**: A list of contract deployment dates on Goerli and Arbitrum Goerli networks.
6. **SDK Documentation**: In-depth documentation on the SDK, including details about various factory functions, structures, queries, and more related to ERC20, IERC1155, IPool, IVault, and other blockchain components.
7. **Utilities and Helpers**: Information about various utilities, formatting functions, and helpers used within the SDK.


---

# 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://docs.premia.blue/developer-center/sdk/sdk-technical-docs.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.