> For the complete documentation index, see [llms.txt](https://whitepaper.web3games.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.web3games.com/web3games.com-platform/web3games-login.md).

# Web3Games Login

The Web3Games.com Player Login SDK empowers game developers to seamlessly integrate email login into their games, providing an effortless onboarding experience for traditional players. By leveraging the SDK's flexible architecture, developers can seamlessly integrate crypto wallet connection options later on, allowing players to explore the full potential of crypto gaming at their own pace.

The Web3Games.com Player Login SDK is the key to bridging the gap between traditional gaming and the emerging world of crypto gaming. By providing a seamless and flexible login solution, game developers can attract a wider audience, foster deeper player engagement, and shape the future of gaming.

<figure><img src="/files/7WbXbNSqFbpPVwcqKwxo" alt=""><figcaption><p>Work Flow of Web3Games Login</p></figcaption></figure>


---

# 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://whitepaper.web3games.com/web3games.com-platform/web3games-login.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.