> For the complete documentation index, see [llms.txt](https://crypto-outlaws.gitbook.io/crypto-outlaws-roadmap/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://crypto-outlaws.gitbook.io/crypto-outlaws-roadmap/crypto-outlaws.md).

# Crypto Outlaws

### Introduction

Welcome to the roadmap documentation for the Crypto Outlaw NFT collection! We hope if you find yourself here you like cool hand-drawn art, decentralized technology and Texas Hold Em.

If so, you've found yourself at the right place on the internet partner!

We at the Crypto Outlaws are the crew behind the world's first Ethereum-native poker playing technology! We plan to build a permissionless, decentralized poker-playing experience that doesn't care where you're from or make you use fictitious tokens to play. Use your native Eth with super low transaction costs. We also won't just stop at your old fashioned playing experience, we have plans on making it much more fun to play than that - in our own Wild Western themed metaverse!

Mount your horse and follow us through the roadmap documentation if you'd like to understand the fantastic places this dusty 'ole trail is going to be taking us together...

![](/files/3M9XjFTzmsZM2rMkHt0v)


---

# 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://crypto-outlaws.gitbook.io/crypto-outlaws-roadmap/crypto-outlaws.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.
