> For the complete documentation index, see [llms.txt](https://docs.ur.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ur.app/getting-started/quickstart.md).

# Quickstart

## Get access

The fastest way to start is the [API sandbox](https://partner.ur.app/api-sandbox). On your first sign-in it creates your `partnerId` and signing key, so you can begin calling UR APIs without waiting on UR. Store your private key; UR does not keep it. See [API signing key](/getting-started/integration-guide.md#api-signing-key) for this path and for bringing your own EVM address instead.

You also get a dedicated integration channel with the UR team for anything the sandbox does not cover, such as production configuration. Email **<support@ur.app>** to set it up.

{% hint style="info" %}
Creating your sandbox credentials is self-serve. Moving a test account to `Live` status still runs through the UR team, because testnet KYC results are mocked.
{% endhint %}

## Access the sandbox environment

UR provides a sandbox environment for integration development and testing. You generate your own credentials in the [API sandbox](https://partner.ur.app/api-sandbox); the UR team promotes test accounts to `Live` status, because testnet KYC results are mocked.

See [Sandbox environment](/getting-started/sandbox-environment.md) for the base URL and testnet notes.

## Authenticate your API requests

All API requests are authenticated using EIP-191 signatures. You'll sign requests with your partner wallet, and UR verifies the signature on every call.

See [Signature and Verify](https://docs.ur.app/api-reference/signature-and-verify) for how it works, including code examples.

## Next steps

* [Choose your approach](/getting-started/integration-guide.md): compare Managed Custody Mode and External Wallet Access Mode
* [OpenAPIs](https://docs.ur.app/api-reference): understand the API surfaces


---

# 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://docs.ur.app/getting-started/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.