# Page Not Found

The URL `how-to-add-import-your-own-token-with-a-contract-address` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [How to import (find) your own token with a contract address](https://guide.ston.fi/en/swapping-on-ston.fi/how-to-import-find-your-own-token-with-a-contract-address.md)
- [Where to find your wallet address](https://guide.ston.fi/en/start-here/where-to-find-your-wallet-address.md)
- [How to create a TON wallet](https://guide.ston.fi/en/start-here/how-to-create-a-ton-wallet.md)
- [How to buy TON (Toncoin) in Telegram](https://guide.ston.fi/en/start-here/how-to-buy-ton-toncoin-in-telegram.md)
- [How to add a new token on STON.fi](https://guide.ston.fi/en/providing-liquidity/how-to-add-a-new-token-on-ston.fi.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://guide.ston.fi/en/swapping-on-ston.fi/how-to-import-find-your-own-token-with-a-contract-address.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.

### Option 2 — Browse the documentation index

Full index: https://guide.ston.fi/en/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://guide.ston.fi/en/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/en/swapping-on-ston.fi/how-to-import-find-your-own-token-with-a-contract-address.md`).

You may also use `Accept: text/markdown` header for content negotiation.