# Tokens

Tokens are the heart of what the key services works with. There are 3 main modules that the API works with to be able to make you do anything with and for your tokens:

* [Contracts](/w3block-eng/dev-docs/api/key-api-services/tokens/contracts.md) 
* [Categories](/w3block-eng/dev-docs/api/key-api-services/tokens/categories.md)
* [Token Collections](/w3block-eng/dev-docs/api/key-api-services/tokens/token-collections.md)

The following diagram explains the relationship between those modules:

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

A Token Collection is going to be your template for minting tokens and to create it you will need to specify a contract and a base template(this one is linked to a more general category). So we can start talking about Contracts and Categories.

{% content-ref url="/pages/74dUnOihIi51JqWsf5wB" %}
[Contracts](/w3block-eng/dev-docs/api/key-api-services/tokens/contracts.md)
{% endcontent-ref %}

{% content-ref url="/pages/IakqMtoEs8G4eCXwFbYw" %}
[Categories](/w3block-eng/dev-docs/api/key-api-services/tokens/categories.md)
{% endcontent-ref %}


---

# Agent Instructions: 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:

```
GET https://w3block.gitbook.io/w3block-eng/dev-docs/api/key-api-services/tokens.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.