# API

W3block services are architected to use the REST api patterns, which everyone can integrate and use on its own applications. For most of our services we also have a SDK developed for node.js applications that can be used for your application to make the integration easier.

To start using the W3block services, you must first understand our architecture of services and what each one can do. Having this in your mind, you can find what service you must call to execute some specific job. The following sections will give an overview about what is each one of our services and what can be done with each one.

* **ID API services**: ID provides services about identity and permission inside all of W3block ecosystem. It provides, for instance, users registration, users permission, whitelist creation and also authentication.
* **Key API services**: Key provides services that can be used to create collections and tokens using some blockchain. You can also use key to transfer tokens and invite users to register and receive some token of a certain collection after registering with a special link.
* [Commerce API services](/w3block-eng/dev-docs/api/commerce-api-services.md): Commerce provides services that can be used to put your tokens created inside Key to sale. It offers both api and a basic e-commerce front-end that can be used to sell yours tokens. With this service you can integrate with some payment gateways as paypal and stripe and sell yours tokens using some FIAT currencies. In a near future it will be also possible to sell tokens using crypto currencies.

<figure><img src="/files/N4rrNh3vG7n99oWhXE5T" alt=""><figcaption><p>Overview of w3block architecture</p></figcaption></figure>


---

# 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.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.