> ## 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 Available Fees

Check unclaimed LP fees for a specific feeOwner and feeToken pair on the ClankerFeeLocker contract on Base. Use clanker-get-token-rewards first to discover recipients and fee token addresses. Returns raw wei amounts. Ideal for: reward tracking, fee monitoring, claim-readiness checks, creator earnings dashboards.

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

Check unclaimed LP fees for a specific feeOwner and feeToken pair on the ClankerFeeLocker contract on Base. Use clanker-get-token-rewards first to discover recipients and fee token addresses. Returns raw wei amounts. Ideal for: reward tracking, fee monitoring, claim-readiness checks, creator earnings dashboards.


## At a Glance

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

## Payload Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `feeOwnerAddress` | `string` | Yes | Fee owner \(reward recipient\) address to query fees for. Use clanker-get-token-rewards to discover recipients for a token. |
| `feeTokenAddress` | `string` | Yes | Fee denomination token address \(e.g. WETH 0x4200000000000000000000000000000000000006\). Use clanker-get-token-rewards to discover fee token addresses per recipient. |

## Result Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `availableFees` | `string` | Yes | Available fees in wei |
| `feeOwnerAddress` | `string` | Yes | Fee owner address queried |
| `feeTokenAddress` | `string` | Yes | Fee denomination token address queried |
| `contractAddress` | `string` | Yes | ClankerFeeLocker contract address |
| `blockNumber` | `number` | Yes | Block number at time of query |

## Examples

**Workflow node**

```json
{
  "type": "clanker-get-available-fees",
  "payload": {
    "feeOwnerAddress": "0x0000000000000000000000000000000000000000",
    "feeTokenAddress": "0x0000000000000000000000000000000000000000"
  },
  "children": []
}
```
  **Test with API**

```bash
curl -X POST "https://api.b3os.org/v1/actions/clanker-get-available-fees/test" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "inputs": {
    "feeOwnerAddress": "0x0000000000000000000000000000000000000000",
    "feeTokenAddress": "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.