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

Claim accumulated LP fees from the ClankerFeeLocker contract on Base for a specific feeOwner and feeToken pair. Use clanker-get-token-rewards first to discover recipients and fee token addresses. Ideal for: automated fee harvesting, reward claiming workflows, creator earnings collection.

![Clanker Claim Fees logo](https://cdn.b3.fun/b3os-icons/clanker.svg)
Catalog action EVM Onchain wallet Gas receive

Claim accumulated LP fees from the ClankerFeeLocker contract on Base for a specific feeOwner and feeToken pair. Use clanker-get-token-rewards first to discover recipients and fee token addresses. Ideal for: automated fee harvesting, reward claiming workflows, creator earnings collection.

**Review wallet and value movement**

This action can require a wallet connector, gas, token movement, or an external side effect. Test with simulation or a controlled amount before using it in a live workflow.

## At a Glance

| Field | Value |
| --- | --- |
| Action ID | `clanker-claim-fees` |
| Category | EVM Onchain |
| Connector | `wallet` |
| Requires gas | Yes |
| Funds movement | `receive` |
| Tags | `clanker`, `fees`, `claim`, `base`, `onchain`, `write` |

## Payload Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `feeOwnerAddress` | `string` | Yes | Fee owner \(reward recipient\) address to claim 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 |
| --- | --- | --- | --- |
| `status` | `string` | Yes | Claim status |
| `transactionHash` | `string` | No | Transaction hash of the claim |
| `blockNumber` | `number` | No | Block number of the transaction |
| `feeOwnerAddress` | `string` | No | Fee owner address claimed for |
| `feeTokenAddress` | `string` | No | Fee denomination token address |

## Examples

**Workflow node**

```json
{
  "type": "clanker-claim-fees",
  "payload": {
    "feeOwnerAddress": "0x0000000000000000000000000000000000000000",
    "feeTokenAddress": "0x0000000000000000000000000000000000000000"
  },
  "children": [],
  "connector": {
    "type": "wallet",
    "id": "conn_wallet"
  }
}
```
  **Test with API**

```bash
curl -X POST "https://api.b3os.org/v1/actions/clanker-claim-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.