> For the complete documentation index, see [llms.txt](https://docs.allforone.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allforone.app/glossary/disambiguation/coins-vs-tokens.md).

# Coins vs Tokens

Coins and tokens are both digital assets that can be traded on a [blockchain](/glossary/definitions/decentralization/blockchains.md). However, there are some key differences between the two.

Coins are cryptocurrencies that have their own independent blockchain. This means that they are not built on top of another blockchain, but rather have their own underlying network and infrastructure. Examples of coins include Bitcoin, Litecoin, and Ethereum.

[Tokens](/glossary/definitions/smart-contracts/tokens.md), on the other hand, are digital assets that are built on top of an existing blockchain. This means that they do not have their own independent blockchain, but rather rely on the infrastructure of the blockchain they are built on. Tokens are typically created through a process called "tokenization," which involves creating a [smart contract](/glossary/definitions/smart-contracts.md) on the blockchain that represents the token. Examples of tokens include ERC-20 tokens on the Ethereum network and BEP-20 tokens on the BNB Smart Chain network.


---

# 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.allforone.app/glossary/disambiguation/coins-vs-tokens.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.