> For the complete documentation index, see [llms.txt](https://sonic-ai-works.gitbook.io/sonic-networks-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sonic-ai-works.gitbook.io/sonic-networks-docs/documentation/developers/developer-quickstart.md).

# Developer quickstart

Go from sign-up to your first deploy in under five minutes.

Integrate around a lifecycle rather than a one-shot request.

## Required integration concepts

1. Resolve tenant/user context.
2. Authenticate the request and validate operation input.
3. Apply a tenant-scoped idempotency key to mutating operations.
4. Reserve credits in atomic units with explicit currency and decimals.
5. Dispatch the provider request only after reservation succeeds.
6. Persist provider operation identity.
7. Merge callbacks idempotently, including partial and out-of-order stages.
8. Settle or refund exactly once when the operation reaches a verified terminal outcome.

## Retry rule

A retry with the same tenant + idempotency key must resolve to the same logical mutation rather than creating a second reservation or provider job.


---

# 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://sonic-ai-works.gitbook.io/sonic-networks-docs/documentation/developers/developer-quickstart.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.