> For the complete documentation index, see [llms.txt](https://docs.v2.like.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.v2.like.co/developer/iscn/iscn-badge.md).

# ISCN Badge

This page is showing how to use query string to change ISCN badge Looks in color and size.

{% hint style="warning" %}
The documentation is designed for Liker Land and LikeCoin v2. For information on [3ook.com](https://3ook.com/) and LikeCoin v3, please visit [docs.3ook.com](https://docs.3ook.com) and [dao.like.co](https://dao.like.co/).
{% endhint %}

**You can add one of the following query string after the "`?`" of the Base URL below. Base URL:** \
`https://static.like.co/badge/iscn/<iscn_tx_hash>.svg?`

Success Example: <https://static.like.co/badge/iscn/3513633D18BA70EB9DA38CD1AC779D6D4372326B3D65B7A14EC75DB8C86C0E6D.svg?dark=1&responsive=0&width=82>

| Query String | Accepted Value                                                                                                |
| ------------ | ------------------------------------------------------------------------------------------------------------- |
| dark         | <p>boolean. e.g. 0 (light) or 1 (dark)</p><p>When not provided, default to 0.</p>                             |
| responsive   | <p>boolean. e.g. 0 (size is not responsive) or 1 (responsive size)</p><p>When not provided, default to 0.</p> |
| width        | <p>number. e.g. 164 (164px)</p><p>When not provided, default to 164.</p>                                      |
| height       | <p>number. e.g. 64 (64px)</p><p>When not provided, default to 64.</p>                                         |

**Some errors may happened when providing multiple conflicting query string values between responsive, width, and height.**

| Error Scenario          | Error Code & Explanation                                                            |
| ----------------------- | ----------------------------------------------------------------------------------- |
| responsive=1\&width=30  | <p>400 <br>Does not know whether the user want a fixed size or responsive size.</p> |
| responsive=1\&height=20 | <p>400 <br>Does not know whether the user want a fixed size or responsive size.</p> |
| responsive=0\&height=sf | <p>400</p><p>Height in wrong format (NaN).</p>                                      |
| responsive=0\&wodth=sf  | <p>400</p><p>Height in wrong format (NaN).</p>                                      |

**Note:**&#x20;

When providing both height & width, but the ratio does not fit to 164 (width) \* 64 (height), we will anchor the size of the badge on **width**.\
For example, user provides `width=200&height=400`, the overall size for the badge would be: `width=200&height=200*64/164`.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.v2.like.co/developer/iscn/iscn-badge.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
