> For the complete documentation index, see [llms.txt](https://multiplechain.gitbook.io/multiplechain-docs-v0.4/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://multiplechain.gitbook.io/multiplechain-docs-v0.4/structure/assets/common.md).

# Common

Below you can find out which methods mean what

### General

**getName**: Name of the relevant asset

**getSymbol**: Symbol of the relevant asset

**getBalance**: Asset balance at the wallet address sent as a parameter

**getDecimals**: The decimal value of the respective asset applies to this Coin and Token. For NFT it is always 0 and does not have to be in every contract.

**transfer**: Initiates a transfer transaction that can be signed by the owner of the relevant asset

### Contracts

The methods here do not have to be in every contract. Only standard asset contracts on blockchain networks have them.

**approve**: Executes a transaction that allows the asset to be managed and spent by another wallet

**transferFrom**: Executes the transaction by which the asset can be transferred to any other wallet by the wallet address authorized by "approve"

### NFT

**getApproved**: Checks whether the relevant NFT is authorized to spend to any other wallet

**getTokenURI**: Returns the URL address where the metadata of the relevant NFT is located

**getOwner**: Returns the wallet address of the owner of the relevant NFT

### Token

**getAllowance**: It is basically the same as getApproved in NFT. However, since tokens are not just one, the total amount authorized to spend is returned.

**getTotalSupply**: Returns the total supply of the respective token


---

# 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://multiplechain.gitbook.io/multiplechain-docs-v0.4/structure/assets/common.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.