> 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/api-reference/deployment-truth-and-provider-security.md).

# Deployment truth & provider security

Shared deployment statuses, null-value policy, server-only provider credentials and mutation security requirements.

API routes can exist before SONIC-specific chain infrastructure exists. Application capability and on-chain deployment are separate states.

## Deployment truth

Never invent a SONIC mint, program ID, treasury, fee authority or update authority. If a deployment value does not exist:

```json
{
  "address": null,
  "status": "planned",
  "verified": false
}
```

A configured mainnet address that has not completed verification is `mainnet_unverified`, not verified.

## Provider secrets

Private Helius, Pyth, Birdeye, AI-provider, RPC, reconciliation and treasury credentials remain in protected server configuration.

```
Browser → SONIC API → normalized provider adapter → provider
```

Never expose private keys through `NEXT_PUBLIC_*`, browser fetches, logs, API envelopes or provider error payloads.

## State-changing request controls

Sensitive mutations must apply the applicable combination of:

* authentication;
* tenant/account authorization;
* RBAC;
* request/wallet/public-URL validation;
* rate limiting;
* tenant-scoped idempotency;
* audit logging;
* replay protection;
* protected reconciliation.

Current process-local rate limiting protects a single backend process. Multi-instance production should use a shared rate-limit store.

## Business identity

External provider task IDs, transaction signatures and mint addresses are never the only business identity. SONIC-owned record IDs survive retries, reordered callbacks and provider replacement.


---

# 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/api-reference/deployment-truth-and-provider-security.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.