15-09-2026: Counterparty Token Amounts Include Direction

Affected endpoints: profiler/address/counterparties, profiler/address/counterparties/batch

Each tokens_info entry now includes:

• total_token_amount: incoming plus outgoing units of the token

• token_in_amount: units received from the counterparty

• token_out_amount: units sent to the counterparty

Direction is relative to the requested wallet, or to the selected entity's wallets for entity input. For example, receiving 4 units and sending 10 units of the same token produces total_token_amount: 14, token_in_amount: 4, and token_out_amount: 10. Different tokens remain separate. All three fields are null when transferred token units cannot be determined.

Breaking change: token_amount has been removed from these tokens_info entries and replaced by total_token_amount. Clients reading token_amount must migrate to total_token_amount.

Rollout: The data-source change is deployed before the API change. The internal total remains available throughout the rollout, but cached responses created before the data-source deployment do not contain the two directional fields. Settled historical requests can remain cached for up to 7 days, so identical requests may return null directional amounts until those entries expire. Recent windows use a 5-minute cache. No cache flush is performed as part of this change.

total_volume_usd, volume_in_usd, volume_out_usd, filters, grouping, pagination, and labels are unchanged.