> For the complete documentation index, see [llms.txt](https://legacy-docs.usesmileid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://legacy-docs.usesmileid.com/getting-started/go-live.md).
# Go Live!
Once you have tested your integration in the sandbox environment, completed your Partner KYC, and funded your wallet, you are ready to run jobs with real IDs.
To perform a job in production, you are only required to calculate your **production signature** and change the endpoints from test to production in your integration code.
### Calculating your Production Signature
Calculating your production signature is the exact same process as you used in the Sandbox environment except you need to use your Production API keys. You can use any of our [server-side libraries](/integration-options/server-to-server.md) or follow the guide in the [Signing your API Request](/integration-options/rest-api/signing-your-api-request.md) page of Rest API in the documentation. You will need your production API key, to obtain your production API key, visit the [security settings page](https://portal.usesmileid.com/security-settings) under the Developers menu, switch the environment to Production using the toggle at the top of the Portal and then copy your API key.
API key management
---
# 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://legacy-docs.usesmileid.com/getting-started/go-live.md?ask=&goal=
```
`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.