> For the complete documentation index, see [llms.txt](https://docs.blynk.io/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blynk.io/en/getting-started/activating-devices/blynk-edgent-static-authtoken.md).

# Static Token

This type of device activation is designed for commercial deployments of non-WiFi IoT devices, such as cellular (3G, 4G, LTE, etc.), Ethernet, and others. Typically these devices don't require any additional parameters from the end customers to connect to the Internet.

<figure><img src="/files/RpOCsdkyYeTU9CBf8Bug" alt=""><figcaption></figcaption></figure>

The process of working with Statiс Tokens is the following:

1. Go to Blynk.Console -> Developer Zone -> Static Tokens
2. Generate the number of Tokens you need based on the number of devices you plan to deploy
3. Each token comes with a corresponding downloadable QR-code image
4. You download the list of Tokens and all QR code images
5. You flash AuthToken (Device Token in the table) to every device and print the corresponding QR code
6. Your customers receive the device + printed (or emailed) QR code
7. Your customers download the Blynk app and scan the QR code
8. After scanning the QR code, a device will be claimed by the customer and is now ready to use

{% hint style="info" %}
The claiming screen now shows the same template-driven preparation instructions used for Wi-Fi provisioning (see [User Guides](/en/blynk.console/templates/user-guides.md)), so customers get the same guidance regardless of activation method. Manual code entry validates the code as it's typed and flags it if it's incomplete.
{% endhint %}

Read more about this process here:

{% content-ref url="/pages/-McPKZ6I0a3CaL6-iQpd" %}
[Deploying Products With Static Tokens](/en/commercial-use/deploying-products-with-static-authtokens.md)
{% endcontent-ref %}


---

# 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.blynk.io/en/getting-started/activating-devices/blynk-edgent-static-authtoken.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.