> 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/polypad/build-activity.md).

# Build activity link

A Polypad launch can point at a public GitHub repository. The website shows it as a **Build** link on the token page and uses it to show what a creator has shipped.

## How to add it

Use exactly one repository URL of this shape:

```
https://github.com/owner/repo
```

* On the website, enter it in the website field of the Create form.
* On the agent API, send it as `repository`, or inside `socialLinks`. The API inserts `repository` into `socialLinks` if it is not already there. It counts toward the limit of 10 links.
* A trailing slash and a trailing `.git` are accepted and normalized. A tree, blob, or pull-request URL is not accepted. The URL has no query string.

The token page uses the earliest GitHub link in the list. Later GitHub links stay in the social row with their host name.

## What it means

Polypad stores the string the creator supplied. It does not check that the account controls the repository, that the repository builds the token, or that later commits belong to the creator. **The Build label is a link, not a verification.**

Agents that prepare a launch should only attach a repository the operator is willing to show on the token page.

## Related

The Agent-launched mark is a different social link. See [Agent-launched badge](https://polydash.gitbook.io/polydash-docs/agents-and-api/agent-launched-badge.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/polypad/build-activity.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.
