> For the complete documentation index, see [llms.txt](https://docs.swapkit.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.swapkit.dev/guides/chain-specific-guides/near-chain-and-its-assets.md).

# Near Chain and its assets

SwapKit provides comprehensive support for NEAR Chain, enabling seamless swaps for both native NEAR tokens and NEP-141 tokens.

### Supported Token Types

SwapKit's NEAR integration supports two primary token types:

#### Native NEAR Token

The native NEAR protocol token used for transaction fees, staking, and governance. In SwapKit, this is represented as `NEAR.NEAR`.

#### NEP-141 Tokens

NEAR's fungible token standard, equivalent to Ethereum's ERC-20. This includes:

* Wrapped NEAR (wNEAR) for DeFi interactions
* Bridged assets from other chains (ETH, wBTC, USDC, USDT)
* Native NEAR ecosystem tokens (DeFi, meme tokens, and project tokens)
* Tokens created through platforms like Meme Cooking

### Fetching Available NEAR Assets

#### Using the Provider Endpoint

To retrieve the complete list of tradeable NEAR assets, use the `/tokens` endpoint with a `GET` request to `https://api.swapkit.dev/tokens?provider=NEAR` You can see the `/tokens` endpoint [explained in detail here](https://docs.swapkit.dev/api-reference/tokens-list-and-search-supported-tokens.md).

Each token in the response includes:

* **identifier**: The SwapKit asset identifier (e.g., `NEAR.NEAR`, `NEAR.wNEAR-wrap.near`)
* **address**: The NEAR contract address (empty string for native NEAR)
* **decimals**: Token precision
* **symbol/ticker**: Token symbols
* **logoURI**: Token logo for UI display
* **extensions**: Additional metadata including the NEP-141 provider ID

#### Token Identification

NEAR tokens follow SwapKit's standard identifier format:

* **Native NEAR**: `NEAR.NEAR`
* **NEP-141 Tokens**: `NEAR.[TICKER]-[CONTRACT_ADDRESS]`
  * Example: `NEAR.wNEAR-wrap.near`
  * Example: `NEAR.USDC-17208628f84f5d6ad33f0da3bbbeb27ffcb398eac501a31bd6ad2011e36133a1`

### Executing Swaps

#### Understanding NEAR wallet addresses

NEAR supports two address formats, and SwapKit accepts both:

* **Implicit accounts** — 64 hexadecimal characters.
* **Named accounts** — human-readable, ending in `.near`, `.tg` or another registered TLD (e.g. `alice.near`).

#### Getting a Quote

Use the `/quote` [endpoint](https://docs.swapkit.dev/api-reference/v3-quote-request-a-swap-quote.md) to retrieve swap rates and routing information like you would for any other token. It can be a cross-chain swap or a single-chain Near Chain swap.

Example request payload - NEAR to AVAX:

```json
{
  "sellAsset": "NEAR.NEAR",
  "buyAsset": "AVAX.AVAX",
  "sellAmount": "10",
  "sourceAddress": "5c33c6218d47e00ef229f60da78d0897e1ee9665312550b8afd5f9c7bc6957d2",
  "destinationAddress": "0x0a4c79cE84202b03e95B7a692E5D728d83C44c76",
  "slippage": 3
}
```

#### Quote Response

The [quote response](https://docs.swapkit.dev/api-reference/v3-quote-request-a-swap-quote.md) includes all the data you find in any other SwapKit quote. It does not carry a transaction — in v3 that is a second call: post the route's `routeId` to [`/v3/swap`](https://docs.swapkit.dev/api-reference/v3-swap-obtain-swap-transaction-details.md) to get a payload ready to sign.

#### Executing the Swap

Swaps originating on Near Chain are funded by a deposit, and no prior approval step is ever needed — NEP-141 has no allowance model.

How the deposit is sent depends on what you're selling, and the route's `txHint` tells you which it is. Native `NEAR.NEAR` is a plain transfer to the deposit address (`simpleTransfer`). A NEP-141 token moves by calling its own contract (`contractCall`), so that transaction carries data and is addressed to the token contract rather than to the deposit address.

Either way the account needs **native NEAR** on top of what it is selling, because NEAR gas is paid in NEAR and a NEP-141 transfer additionally attaches 1 yoctoNEAR. A wallet holding only the token cannot swap it. Pass `gasCheck: true` on the quote to have SwapKit check this and return an `insufficientGas` warning rather than letting the send fail at broadcast.

### Amounts and decimals

Write `sellAmount` as a human-readable decimal — 10 NEAR is `"10"`, not `"10000000000000000000000000"` — and SwapKit converts using the token's metadata.

Decimals still matter when you read a balance or render an amount yourself: native NEAR uses 24, and NEP-141 tokens vary. Take the `decimals` field from `/tokens` rather than assuming.

### Additional Resources

* NEAR Protocol Documentation: <https://docs.near.org>
* NEP-141 Token Standard: <https://nomicon.io/Standards/Tokens/FungibleToken>
* NEAR Wallets: <https://wallet.near.org/>
* NEAR Explorer: <https://nearblocks.io>

***

For support or questions about NEAR integration don't hesitate to contact us directly.
