> For the complete documentation index, see [llms.txt](https://token-playground.gitbook.io/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://token-playground.gitbook.io/guide/index/12_identify_classic_using_stellar_sdk.md).

# 12 : Identify a Stellar Classic Asset using stellar-sdk.

How can we know if a specific asset is a Stellar Classic Asset?

Create an asset:

```
bash quickstart.sh standalone
bash run.sh
node src/friendbot.js
node src/issueAsset.js AAA
```

This will return:

```
ASSET ISSUED:  Asset {
  code: 'ABCD',
  issuer: 'GAM5XOXRUWPMKENBGOEAKMLRQ4ENHLHDSU2L2J7TVJ34ZI7S6PHMYIGI'
}
```

## From a SYMBOL:ISSUER address

1.- See if the combination have a correct format:

```javascript
var asset = new StellarSdk.Asset(asset_code, asset_issuer );
```

This will create an asset object. If either the asset\_code or the asset\_issuer are not in a good format, this will fail.

Test with:

```
node src/chapter12/checkFormat.js ABC GAM5XOXRUWPMKENBGOEAKMLRQ4ENHLHDSU2L2J7TVJ34ZI7S6PHMYIGI
```

## See if the asset exist?

Can we know if for an asset we have totalSupply or something?

Can we use this in stellar-sdk?

```
https://horizon-testnet.stellar.org/assets?asset_code=ASSET_CODE&asset_issuer=ISSUER_ADDRESS
```

## From a wrapped asset contract address


---

# 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://token-playground.gitbook.io/guide/index/12_identify_classic_using_stellar_sdk.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.