# Tokens

### What `/tokens` returns

`GET /tokens` returns supported tokens for routing.

Use it to search by symbol or exact address.

### Query parameters

* `search` — optional symbol or exact address.
* `limit` — optional result size. Default: `100`. Max: `500`.

### Example requests

```bash
curl "https://api.dirol.io/api/v1/tokens?search=USDC"
```

```bash
curl "https://api.dirol.io/api/v1/tokens?search=0x754704Bc059F8C67012fEd69BC8A327a5aafb603"
```

### Example response

```json
{
  "tokens": [
    {
      "address": "0x754704Bc059F8C67012fEd69BC8A327a5aafb603",
      "symbol": "USDC",
      "name": "USDC",
      "decimals": 6,
      "logoURI": "https://imagedelivery.net/.../usdc.png/public",
      "isVerified": true
    }
  ]
}
```

### Response fields

* `address` — token contract address.
* `symbol` — ticker symbol.
* `name` — token name.
* `decimals` — token decimals for unit conversion.
* `logoURI` — token image URL.
* `isVerified` — verification status.

### Common token addresses

* `WMON` — `0x3bd359C1119dA7Da1D913D1C4D2B7c461115433A` — `18`
* `USDC` — `0x754704Bc059F8C67012fEd69BC8A327a5aafb603` — `6`
* `USDT` — `0xe7cd86e13AC4309349F30B3435a9d337750fC82D` — `6`
* `WETH` — `0xEE8c0E9f1BFFb4Eb878d8f15f368A02a35481242` — `18`
* `WBTC` — `0x0555E30da8f98308EdB960aa94C0Db47230d2B9c` — `8`

### Native `MON`

For native `MON` swaps, request routes with the `WMON` address.

When sending the swap transaction, set `value = amountIn`.

### Best practices

* Use `/tokens` to discover live metadata.
* Use `decimals` to convert human amounts into raw units.
* Do not assume every supported token is listed in this page.


---

# 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://dirolprotocols-organization.gitbook.io/dirol/api/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.