> For the complete documentation index, see [llms.txt](https://polydash.gitbook.io/polydash-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://polydash.gitbook.io/polydash-docs/agents-and-api/agent-launched-badge.md).

# Agent-launched badge

The **Agent-launched** badge shows on a token card and token page when the token's social links include the documented agent mark.

```
https://polypad.family/docs#agent-launched
```

## How the mark works

* With `agentMark: true` (the default), the API appends this exact URL to `socialLinks` if it is not already there.
* The factory stores the list on the token. The website reads it and shows the badge.
* The deployed factory is unchanged. There is no new on-chain event.
* Set `agentMark` to `false` to leave the URL out.
* The mark uses one of the 10 social-link slots. If the list is already full, validation fails and names `socialLinks`, so the caller can drop a link or include the mark.
* The mark is hidden from the social link row. It is not a build-activity link.

A person using the website can get the same mark by opening `/create?agent=1`. That query parameter is not stored by itself. The wizard writes the mark into `socialLinks` before the wallet signs.

## Where it shows up

* Token cards and pages on Polypad.
* The Explore filter for agent-launched tokens.
* `GET /api/agents/v1/tokens?agent=1`, and the `agentLaunched` field on token responses.
* `GET /api/agents/v1/launched`, which lists launches registered as agent-launched.

## What the badge means

The badge records **how a launch was prepared**. It says nothing about the token's quality or risk. It does not mean the agent, the operator, or the token was reviewed.

## Related

* [Launch endpoints](https://polydash.gitbook.io/polydash-docs/agents-and-api/launch-endpoints.md)
* [Holder Protections](https://polydash.gitbook.io/polydash-docs/polypad/holder-protections.md)
* [Risk disclosure](https://polydash.gitbook.io/polydash-docs/security-and-risk/risk-disclosure.md)


---

# 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://polydash.gitbook.io/polydash-docs/agents-and-api/agent-launched-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.
