> For the complete documentation index, see [llms.txt](https://docs.taligate.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taligate.com/tracking-wallets.md).

# Tracking wallets

You give Taligate a public Polymarket wallet address (the 0x proxy address), and it checks that wallet every 30 seconds. When a position changes - the trader enters a market, adds to one, trims it, or closes it entirely - you get an alert. Price movements alone don't trigger anything. Only actual trades do.

## Adding a wallet

### Single address

Use `/track` and paste one 0x address. The bot looks up the trader's Polymarket public name and offers it as the default nickname for that wallet. Type `/skip` to accept the name as-is, or type your own nickname to use that instead.

### Bulk add (up to 25 at once)

Paste multiple addresses in a single message - one per line is fine, or space-separated. The bot adds all of them without asking for a nickname on each one. Each wallet gets added with its Polymarket name if one is found.

When it finishes, you get a summary that tells you:

* how many were added
* how many you were already tracking
* how many were skipped because you hit your plan's wallet limit
* how many were invalid (not valid 0x addresses)

You can rename wallets individually afterward from the `/list` view.

## How wallet names work

When Taligate displays a wallet - in alerts, `/list`, `/top`, or `/digest` - it picks the name in this order:

1. Your typed nickname (if you set one)
2. The trader's Polymarket public name
3. The short address

A nickname you type is permanent from your side. The bot never overwrites it automatically. If the Polymarket name is missing when a wallet is first added, the bot fills it in later when it becomes available - but once a name is set, it stays as-is. Your own nicknames are never touched.

## Viewing your wallets

`/list` shows each tracked wallet as its own card. Each card has buttons:

* **Profile** - opens the trader's public Polymarket profile
* **Positions** - shows their current open positions, sorted by size
* **Alerts** - the filter settings for this specific wallet (minimum value, change thresholds, which event types to receive)
* **Rename** - set or change your nickname for this wallet
* **Mute / Unmute** - stop or resume alerts from this wallet without removing it
* **Untrack** - remove the wallet entirely
* **Activate** - shown only on paused wallets (see below)

## Paused wallets

Each plan has a wallet limit: 1 on Free, 5 on Basic, 20 on Pro, unlimited on Whale. If your limit drops - because your trial ends or your subscription expires - the wallets over the new limit are paused, not deleted. The most recently added wallets stay active; older ones pause first.

A paused wallet keeps all its settings and history. To resume it, either upgrade your plan, or mute one of your active wallets and tap **Activate** on the paused one.

## Stopping tracking

`/untrack` removes a wallet. You'll no longer receive alerts for it, and its data is cleared from your account.


---

# 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://docs.taligate.com/tracking-wallets.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.