> ## Documentation Index
> Fetch the complete documentation index at: https://docs.b3os.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Clanker Get Token Rewards

Resolve reward recipients and fee denominations for a Clanker token on Base. Returns each recipient's address, BPS share, fee preference, and fee token addresses (WETH, clanker token, or both). Ideal for: discovering fee recipients before claiming, reward tracking, fee preference analysis, composable claim workflows.

![Clanker Get Token Rewards logo](https://cdn.b3.fun/b3os-icons/clanker.svg)
Catalog action Blockchain Data

Resolve reward recipients and fee denominations for a Clanker token on Base. Returns each recipient's address, BPS share, fee preference, and fee token addresses (WETH, clanker token, or both). Ideal for: discovering fee recipients before claiming, reward tracking, fee preference analysis, composable claim workflows.


## At a Glance

| Field | Value |
| --- | --- |
| Action ID | `clanker-get-token-rewards` |
| Category | Blockchain Data |
| Connector | Not required |
| Requires gas | No |
| Funds movement | None declared |
| Tags | `clanker`, `rewards`, `fees`, `base`, `onchain`, `read` |

## Payload Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `tokenAddress` | `string` | Yes | Clanker token contract address to resolve reward recipients for. |

## Result Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `clankerTokenAddress` | `string` | Yes | Checksummed clanker token address |
| `recipients` | `array` | Yes | Reward recipients with their fee preferences and token addresses |
| `allFeeTokens` | `array` | Yes | Deduplicated list of all fee token addresses across all recipients |
| `totalRecipients` | `number` | Yes | Total number of reward recipients |
| `claims` | `array` | Yes | Flat list of \(feeOwner, feeToken\) pairs for easy iteration in workflows. Each recipient × feeToken combination is one entry. |
| `totalClaims` | `number` | Yes | Total number of claim pairs \(recipients × fee tokens\) |

## Examples

**Workflow node**

```json
{
  "type": "clanker-get-token-rewards",
  "payload": {
    "tokenAddress": "0x0000000000000000000000000000000000000000"
  },
  "children": []
}
```
  **Test with API**

```bash
curl -X POST "https://api.b3os.org/v1/actions/clanker-get-token-rewards/test" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "inputs": {
    "tokenAddress": "0x0000000000000000000000000000000000000000"
  }
}'
```

**Use expressions for dynamic values**

Payload fields can use workflow expressions such as `{{$trigger.body.amount}}`, `{{$nodes.fetch.result.price}}`, and `{{$props.asset}}` when the value should come from a trigger, prior node, or reusable workflow prop.