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

# Getting access

How to request access, what to send us and how credentials are issued.

Access to TRON Energy is set up by our team for each organisation. Contact <business@luganodes.com> for API keys, RPC endpoint access or a direct delegation.

## How access works

{% stepper %}
{% step %}

### Share your requirements

Send us the details listed under [What to send us](#what-to-send-us).
{% endstep %}

{% step %}

### Agree the delivery model

Our team recommends a delivery model for your volume and transaction mix.
{% endstep %}

{% step %}

### Receive your credentials

For the API, we share an API key, a secret and your [base URL](https://docs.luganodes.com/tron-energy/energy-rental-api/conventions-and-limits.md#base-url). For the RPC endpoint, we share an API key and your base URL: your node URL is `$BASE_URL/rpc`. For direct delegation, energy is delegated to your addresses by our team, typically within one business day.
{% endstep %}
{% endstepper %}

## What to send us

| Item                                                             | Why we ask                                          |
| ---------------------------------------------------------------- | --------------------------------------------------- |
| Organisation and a technical contact                             | Credentials and support are issued per organisation |
| Expected daily volume                                            | Capacity is sized to your volume                    |
| Transaction types (token transfers, swaps, other contract calls) | Energy needs vary by transaction                    |
| Delivery model: API, RPC endpoint or direct delegation           | Each model is provisioned differently               |
| Sending addresses (direct delegation only)                       | Energy is delegated to a fixed set of addresses     |

## API credentials

| Credential | Used for                                               |
| ---------- | ------------------------------------------------------ |
| API key    | Identifies your organisation on every request          |
| Secret     | Signs every request. It is never sent with the request |

[Authentication and signing](https://docs.luganodes.com/tron-energy/energy-rental-api/making-requests.md) shows how to sign requests and how to store and rotate your credentials.
