Documentation Index
Fetch the complete documentation index at: https://docs.near-intents.org/llms.txt
Use this file to discover all available pages before exploring further.
Multi Token Standard (NEP-245)
After a successful deposit, the Verifier contract manages tokens using the Multi Token Standard (NEP-245). This enables uniform handling of all supported token types.Token ID format
Each token is identified by a string-based token ID, prefixed with its standard type.| Token Type | Prefix | Example |
|---|---|---|
| Fungible (NEP-141) | nep141: | nep141:wrap.near |
| Non-fungible (NEP-171) | nep171: | nep171:coolnfts.near:rock.near |
| Multi Token (NEP-245) | nep245: | nep245:mygame.near:shield.near |
Checking your balance
After a successful deposit, query your balance using mt_balance_of, which adheres to the NEP-245 standard.- NEAR CLI
- NEAR API JS
| Parameter | Description |
|---|---|
account_id | The NEAR account to check the balance of. |
token_id | The token ID with its standard prefix (e.g., nep141:wrap.near). See Token ID format. |
Batch balance query
To check multiple token balances at once, use mt_batch_balance_of:- NEAR CLI
- NEAR API JS
Balances are returned in the smallest unit of each token (e.g., yoctoNEAR for wrapped NEAR).